Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[INFO]: OS X 10.2.3 and saving Word files to Windows SFM Servers via Appleshare

11 views
Skip to first unread message

Matthew Centurión [MS]

unread,
Jan 16, 2003, 6:23:20 PM1/16/03
to
Just a heads up on the issue mentioned several times here in threads such
as:

Word v.X and Network Saves
Word X, OS X, and saving to a server
Disk Full Error in MSWord X (Mac OS X)
Word X can't save to Win2k share-Temp Items permission problem
Still can't disable "read-only"
Saving Word Document on Server

This issue has been found to affect Word v.X and Word 2001 (under Classic)
who have upgraded their OS X to 10.2.3 and who connect via AFP to Windows
servers running Windows Services for Macintosh.

Error messages include "Disk Full" or "Unrecoverable Disk Error" an
attempted saves to network share.

We are currently working with Apple to resolve the issue. Workarounds
include:

1) Using "smb://" instead of "afp://" to connect to share.*
2) Not upgrading to OS X - 10.2.3 until more information is available

No other information is available at this time. I will post when there is,
but I don't have a timeframe for any such updates.

If you have been affected by this issue in ways not mentioned in the
messages above I encourage you to post your experience as this will help us
verify any fix that may result from this issue.

Thank you for your patience and your business,

Matt Centurión
MacWord Testing
Macintosh Business Unit

* It has been mentioned in this newsgroup that the use of the SMB protocol
may corrupt files when accessed by other AFP clients as well. This has not
been our experience but we suggest caution when implementing this solution
if you have not used it before. Any issues with the SMB protocol use should
be reported to Apple.

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this e-mail address. It is for
newsgroup purposes only.

Find out everything about Microsoft Mac Newsgroups at:
http://www.microsoft.com/mac/support/newsgroups.asp
Check out product updates and news & info at:
http://www.microsoft.com/mac


Ken

unread,
Jan 20, 2003, 11:17:20 AM1/20/03
to

Hi Matt,
Any update on this issue?

Thanks,
Ken

>.
>

Matthew Centurión [MS]

unread,
Jan 20, 2003, 11:57:34 AM1/20/03
to
On 1/20/03 8:17 AM, in article 007901c2c09f$68a14e10$d2f82ecf@TK2MSFTNGXA09,
"Ken" <m...@gscap.homeip.net> wrote:

> Hi Matt,
> Any update on this issue?
>
> Thanks,
> Ken
>
>

Yes.. It also seems to affect Saving from Word 98/2001 on OS 9.x and Word X
on OS X when the file is on a OS X 10.2.3 SERVER. So, if you know your
server admins, tell them not to install the Server patch yet either. We are
still working with Apple on the issue.

No other information is available at this time. I will post when there is,
but I don't have a timeframe for any such updates.

Matt


MacWord Testing
Macintosh Business Unit

--

Beth Rosengard

unread,
Jan 20, 2003, 12:25:56 PM1/20/03
to
Hi Ken,

Matt said, "No other information is available at this time. I will post


when there is, but I don't have a timeframe for any such updates."

I think that says it all. I would expect a solution that involves both
Microsoft and Apple to take a while.

--
Beth Rosengard
Mac MVP

Mac Word FAQ: <http://www.mvps.org/word/FAQs/WordMac/index.html>
Entourage Help Page: <http://www.entourage.mvps.org>


On 1/20/03 8:17 AM, in article 007901c2c09f$68a14e10$d2f82ecf@TK2MSFTNGXA09,
"Ken" <m...@gscap.homeip.net> wrote:

John McGhie [MVP - Word]

unread,
Jan 20, 2003, 6:44:01 PM1/20/03
to
Ken:

Not yet. They're still working on it. It requires a fairly major change.

Cheers

This responds to microsoft.public.mac.office.word on Mon, 20 Jan 2003
08:17:20 -0800, "Ken" <m...@gscap.homeip.net>:

All Spam blocked with SpamNet: a free download from http://www.cloudmark.com/

Please post all comments to the newsgroup to maintain the thread.

John McGhie, Consultant Technical Writer
McGhie Information Engineering Pty Ltd
Sydney, Australia. GMT + 10 Hrs
+61 4 1209 1410, mailto:jo...@mcghie-information.com.au

Mark Meyer

unread,
Jan 21, 2003, 3:53:31 PM1/21/03
to

Word from Microsoft is that Apple's 10.2.4 will fix the problem. It has been
seeded to developers and should be out to us users soon????

John McGhie [MVP]

unread,
Jan 21, 2003, 5:17:53 PM1/21/03
to
WHO in Microsoft?

I suspect that this rumour is true, but I am talking to the Microsoft
software engineers daily, and no-one has gone on the record to ME to confirm
it :-)

Cheers

This responds to article <BA530F6B.4A12%msm...@blc.edu>, from "Mark Meyer"
<msm...@blc.edu> on 22/1/03 7:53 AM:

> Word from Microsoft is that Apple's 10.2.4 will fix the problem. It has been
> seeded to developers and should be out to us users soon????
>

--
All Spam and attachments blocked by Microsoft Entourage for Mac OS X. Please
post replies to the newsgroup to maintain the thread.

John McGhie, Microsoft MVP: Word for Macintosh and Word for Windows
Consultant Technical Writer <jo...@mcghie-information.com.au>
+61 4 1209 1410; Sydney, Australia: GMT + 10 hrs

Rob Banzai

unread,
Jan 21, 2003, 5:52:27 PM1/21/03
to
I'd like to reiterate that this problem is not just related to 10.2.3
although that was the break-point for some people. I made a fresh flat
panel iMac with 10.2 and had the same problem. I've been working with
a Microsoft engineer and made absolutely no progress other than
proving without a doubt that this is not just related to 10.2.3.

As for SMB/AFP having X and OS 9 users accessing the same files via
both protocols is not a good thing. SMB and AFP are tracking file
information differently so any file saved by an SMB user loses its
resource fork info, just like an AFP user fouls things up for an SMB
person.

This problem is holding up my OS X rollout so I'm eager to see a
solution no matter whose shoulders it falls upon.

Robert

Beth Rosengard <bethro...@earthlink.net> wrote in message news:<BA517123.1C816%bethro...@earthlink.net>...

Mark Meyer

unread,
Jan 22, 2003, 10:53:30 AM1/22/03
to
On 1/21/03 4:17 PM, in article
BA541241.204C6%jo...@mcghie-information.com.au, "John McGhie [MVP]"
<jo...@mcghie-information.com.au> wrote:

> WHO in Microsoft?
>
> I suspect that this rumour is true, but I am talking to the Microsoft
> software engineers daily, and no-one has gone on the record to ME to confirm
> it :-)
>
> Cheers
>
> This responds to article <BA530F6B.4A12%msm...@blc.edu>, from "Mark Meyer"
> <msm...@blc.edu> on 22/1/03 7:53 AM:
>
>> Word from Microsoft is that Apple's 10.2.4 will fix the problem. It has been
>> seeded to developers and should be out to us users soon????
>>

Our college has a connection in the Microsoft Macintosh business Unit. He
told us that 10.2.4 will fix the problem.

Mark Meyer
Dir. Of Academic Computing
Bethany Lutheran College
Mankato, MN

Mickey Stevens

unread,
Jan 22, 2003, 3:58:33 PM1/22/03
to
On 1/22/03 9:53 AM, in article BA541A9A.4A55%msm...@blc.edu, "Mark Meyer"
<msm...@blc.edu> wrote:

If anyone has a new PowerBook G4 model, they'll know. Some users attending
Macworld report that these new computers ship with 10.2.4.

--
Mickey Stevens (Microsoft MVP for Office:mac)
PowerPoint FAQ featuring PowerPoint:mac: <http://www.pptfaq.com/>
The Entourage Help Page: <http://www.entourage.mvps.org/>

Rob Banzai

unread,
Jan 22, 2003, 6:12:51 PM1/22/03
to
I hope that 10.2.4 is the answer. This problem is kind of making me
look bad at work! :P


Mark Meyer <msm...@blc.edu> wrote in message news:<BA541A9A.4A55%msm...@blc.edu>...

Marco Schrieck

unread,
Jan 27, 2003, 4:14:38 AM1/27/03
to
"Matthew Centuri=?ISO-8859-1?B?8w==?=n [MS]" <ma...@online.microsoft.com> wrote in message news:<BA4C7EE8.14F07%ma...@online.microsoft.com>...

> Just a heads up on the issue mentioned several times here in threads such
> as:
>
> Word v.X and Network Saves
> Word X, OS X, and saving to a server
> Disk Full Error in MSWord X (Mac OS X)
> Word X can't save to Win2k share-Temp Items permission problem
> Still can't disable "read-only"
> Saving Word Document on Server

I had this problem sometimes with large files Freehand, Corel and TIFF
And always a file corruption.


> 1) Using "smb://" instead of "afp://" to connect to share.*

I use the SMB Protocol on a w2k Server with latest updates but AFS enabled too.

> 2) Not upgrading to OS X - 10.2.3 until more information is available

to late :)

best reegards

Marco Schrieck

--
Detailgetreu GmbH - Domplatz 3 - 93047 Regensburg
++49 941 58433 0
http://www.detailgetreu.de
msch...@detailgetreu.de

John McGhie [MVP]

unread,
Jan 27, 2003, 11:28:45 AM1/27/03
to
Marco:

Check back with us daily: I get the feeling there's a fix on the way any day
now. This is a critical issue that is getting very high priority.

Cheers


This responds to article <6f0c20fd.03012...@posting.google.com>,
from "Marco Schrieck" <msch...@detailgetreu.de> on 27/1/03 1:14 AM:

--

Mark D. Wagner, M.Ed.

unread,
Feb 10, 2003, 8:45:04 PM2/10/03
to
I am the Educational Technology Coordinator at a campus where our
network is all W2K with Active Directory for roaming profiles. We also
have 250 Macs running OS X, which authenticate directly to AD; At
login they mount a home directory that resides on one of our W2K
advanced servers. Things were working beautifully with Mac OS 10.1.5.
However, after our recent upgrade to 10.2.3 on our Mac workstations,
the Word Saving problem manifests itself. (Reasons to switch were
compelling in the educational setting, Apple granted us a free upgrade
for all our machines, and we took word for granted during our testing
phase.. if it opened a doc, we were happy and moved on.) We have
worked with Apple on this issue, but while we now have a work around
of sorts, there is no resolution. An Apple SE suggested that this
might be an NTFS ownership issue, which led me to the state of affairs
described below. I have included information that includes our
experiences thus far (and the work around we have passed onto our end
users.) Any help or updates on this issue would be appreciated. I am
more than willing to put time in on this end to be sure this gets
solved. Thanks in advance for anytime you give to my message and our
issue. -Mark

OUR SITUATION SO FAR:

Our My Documents and Documents folders are both redirected into our
Home directory (or H: drive to the PCs) on the AD server.


- If a student has NTFS ownership of the Documents folder, it
seems Word v.X can save and auto save without a problem, but strangely
not in all cases. This requires more testing.. or more complete
knowledge of what has changed in 10.2 . (*See below for a discussion
of "not all cases.")
- If students do not have ownership of the Documents folder,
Word v.X cannot save a file – even though students have Full Control
permissions on that folder. Word will unexpectedly quit and all work
will be lost. (This is the error your described in the previous post.)
- Most of our students do not have ownership of Documents,
because under our August 10.1 roll out, it was an easy way to set many
Mac preferences to copy them into the home directories of all of the
students. We took Administrative ownership in the process of doing
this. Again, we gave them Full Control when we were done, and under
10.1.5 (and W2K, of course) this sufficed.
- If a student saves their Word v.X doc into their My
Documents folder (which they all still own), it seems to save alright.
- However, once auto save kicks-in ten minutes later we still
get the error, and the application crashes. All unsaved work is lost.
- If auto-save is turned off in the word preferences, this
problem is solved… though of course the auto-save safety net is now
gone. Students must save frequently as insurance against the
unexpected. (NOTE: A programmer who is adept at VB walked me through
the configurable areas of word, but we could not locate the variable
responsible for WHERE word auto-saves. This info might help reach a
more desirable work around.)

- Auto-save must be turned off by each user, as the
preferences are individually stored in the home directory and are not
machine or application based. (We considered writing a batch file to
deal with this issue all at once, but found our scriptwriting
abilities lacking… a friend suggested a PERL script might be more
useful, but even if we had the in-house programming abilities, this
only amounts to a fancier work around.)

- So, the logistical challenge of this ‘work around' is to
somehow train 1300 students, teachers, and staff not to allow word to
save in its default location… to instead always Save As to My
Documents (which, admittedly is desirable in terms of all docs being
in one place on a cross-platform network),,, and to turn off their own
auto-save function in their own Word preferences. This is, it probably
goes without saying, a less than desirable situation in a high school
setting.
- In the meantime I will get the word out to the frustrated
teachers.


*Not all cases: For whatever its worth.. we found some cases in which
a student is the owner of Documents, but cannot save with Word. These
students do not have ownership over the Home directory in which
Documents resides. It turns out that the students who CAN save, also
have ownership over their home directory, a situation that is very
rare because, due to a desire not to type afp sharepoint paths over a
thousand times, we create most accounts and home directories using an
automated import tool; so Administrators owns their Home directory
folder.)

Mark D. Wagner, M.Ed.
Education Technology Coordinator
Estancia High School
Newport-Mesa Unified School District
mwa...@nmusd.k12.ca.us
949-515-6566

Rob Banzai

unread,
Feb 11, 2003, 10:55:32 AM2/11/03
to
As has been clearly documented this problem is directly related to
saving to a Win2k server and the inability of Word to save it's temp
files due to a permissions problem. It is NOT just 10.2.3 but also
10.2 as I have proved earlier.
Word always saves its temp files to the same location as the file
you're working on. If that files was opened from the network Word will
attempt to save its temp files there, and it will fail and crash the
machine. Although SMB is a workaround it does not properly store the
resource fork and this is particularly bad in a mixed environment
where OS X and OS 9 users will be sharing files.

It's ugly and us usual we are stuck in the middle while we wait for
someone (MS/Apple) to get off their lazy asses and fix it.

mwa...@nmusd.k12.ca.us (Mark D. Wagner, M.Ed.) wrote in message news:<24f321d0.03021...@posting.google.com>...

> Word v.X cannot save a file ? even though students have Full Control


> permissions on that folder. Word will unexpectedly quit and all work
> will be lost. (This is the error your described in the previous post.)
> - Most of our students do not have ownership of Documents,
> because under our August 10.1 roll out, it was an easy way to set many
> Mac preferences to copy them into the home directories of all of the
> students. We took Administrative ownership in the process of doing
> this. Again, we gave them Full Control when we were done, and under
> 10.1.5 (and W2K, of course) this sufficed.
> - If a student saves their Word v.X doc into their My
> Documents folder (which they all still own), it seems to save alright.
> - However, once auto save kicks-in ten minutes later we still
> get the error, and the application crashes. All unsaved work is lost.
> - If auto-save is turned off in the word preferences, this

> problem is solved? though of course the auto-save safety net is now


> gone. Students must save frequently as insurance against the
> unexpected. (NOTE: A programmer who is adept at VB walked me through
> the configurable areas of word, but we could not locate the variable
> responsible for WHERE word auto-saves. This info might help reach a
> more desirable work around.)
>
> - Auto-save must be turned off by each user, as the
> preferences are individually stored in the home directory and are not
> machine or application based. (We considered writing a batch file to
> deal with this issue all at once, but found our scriptwriting

> abilities lacking? a friend suggested a PERL script might be more


> useful, but even if we had the in-house programming abilities, this
> only amounts to a fancier work around.)
>

> - So, the logistical challenge of this ?work around' is to


> somehow train 1300 students, teachers, and staff not to allow word to

> save in its default location? to instead always Save As to My

John McGhie [MVP]

unread,
Feb 13, 2003, 4:18:49 PM2/13/03
to
Hi Rob/Mark:

This is an Apple bug. They have already fixed it. They are currently
testing the patch to make sure it doesn't break anything else (which is what
they should have done the first time!) and we will get it as soon as they
have completed their testing.

Cheers


This responds to article <c9a51ef8.03021...@posting.google.com>,
from "Rob Banzai" <rba...@yahoo.com> on 11/2/03 7:55 AM:

--

Rob Banzai

unread,
Feb 13, 2003, 5:43:45 PM2/13/03
to
WOOHOO!

Today's OS X 10.2.4 update solved the problem for Word X not being
able to save back to the network via AFP!

I'm testing now to see if Word 98 is fixed too.

Thank you, Apple!

rba...@yahoo.com (Rob Banzai) wrote in message news:<c9a51ef8.03021...@posting.google.com>...

Matthew Centurión [MS]

unread,
Feb 13, 2003, 8:52:51 PM2/13/03
to
As has already been mentioned, the now-available Mac OS X 10.2.4 update
should resolve issues between 10.2.3 clients saving Word documents on
Windows SFM fileservers as well as AppleshareIP fileservers and MacOS X
fileservers.

Those who have Mac OS X Servers running 10.2.3 should upgrade to 10.2.4
whenever the server update is out as well.

Let us know if you still encounter this issue after upgrading to 10.2.4
(unless you are accessing a Mac OS X 10.2.3 server, in which case you need
to have the server admin update it to 10.2.4)

Thx for your patience,

Matt


MacWord Testing
Macintosh Business Unit

--


This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this e-mail address. It is for
newsgroup purposes only.

Find out everything about Microsoft Mac Newsgroups at:
http://www.microsoft.com/mac/support/newsgroups.asp
Check out product updates and news & info at:
http://www.microsoft.com/mac

On 1/16/03 3:23 PM, in article BA4C7EE8.14F07%ma...@online.microsoft.com,

Hannes Stein

unread,
Feb 14, 2003, 4:58:23 PM2/14/03
to
Hi there,


In <BA718BF3.164BE%ma...@online.microsoft.com> Matthew Centurión [MS]"
wrote:


> As has already been mentioned, the now-available Mac OS X 10.2.4
> update should resolve issues between 10.2.3 clients saving Word
> documents on Windows SFM fileservers as well as AppleshareIP
> fileservers and MacOS X fileservers.

I got a OS10.2.4 Mac PB (Office 10.1.2), trying to save on a AFP Server (
Linux netatalk 1.6.0) still getting crashes...

The only difference seems to be, that the first message is
"Word kann den Vorgang nicht beenden, da zu viele Dateien geoeffnet sind.
" - Too many files opened.

No crashes so far, but no saving, too. My Client log says:
Feb 14 22:21:49 morkvomork mach_kernel: ubc_isinuse: called without a
valid reference: v_tag = 21
ubc_isinuse: type VREG, usecount 1, writecount 0, refcount 0,
Feb 14 22:21:49 morkvomork mach_kernel: tag VT_AFP, dirID 30, on
dev 45, 3

After another few tries the mac says that the connection has been
unexpectatly disconnected ("Getrennt - Die Verbindung zum File-Server
"gonzo" wurde unerwartet getrennt und die Verbindung konnte nicht erneut
aufgebaut werden."). Words talk something about bad floppy-disks (!),
where the "Word Work File_2734" should be and finally crashes...

The Word Work File is places on the server:
Temporary Items/501/Temporary Items/Word Work File_2734


So, that's what my system.log sais while Word crashes...
Feb 14 21:56:51 morkvomork mach_kernel: AFP_VFS afpfs UserCommand:
sosend failed for reply 32
Feb 14 21:56:51 morkvomork mach_kernel: AFP_VFS afpfs_Reconnect started /
Volumes/dokumente
Feb 14 21:56:51 morkvomork mach_kernel: AFP_VFS afpfs_Reconnect: Wrong
version 4 or no more attempts 0
Feb 14 21:56:53 morkvomork mach_kernel: AFP_VFS afpfs_unmount: /Volumes/
dokumente, flags 524288, pid 280
Feb 14 21:56:53 morkvomork mach_kernel: AFP_VFS afpfs_unmount:
succeeded
Feb 14 21:56:57 morkvomork crashdump: Crash report written to: /Users/
hannes/Library/Logs/CrashReporter/Microsoft Word.crash.log

The File Server says:
Feb 14 13:33:56 gonzo afpd[1089]: server_child[1] 1893 killed


I wonder if they will ever be able to make Word become a program one can
use...

Hannes

btw: I had this problem even with 10.2.1 - and I read reports of that
with 10.1.5, too.
--
Hannes Stein
hann...@macnews.de
ICQ#118301645

Jim Gordon

unread,
Feb 15, 2003, 12:56:22 AM2/15/03
to
Hi

Please be sure to send a report to Microsoft about this problem. Use the
Feedback feature on Excel's help menu.

-Jim Gordon
Mac MVP

All responses should be made to this newsgroup within the same thread.
Thanks.

Find Macintosh experts in your hometown. Join a user group:
http://www.microsoft.com/mindshare/default.asp
http://www.apple.com/usergroups/

----------
In article <20030214225...@news.cis.dfn.de>, Hannes Stein

hannsens

unread,
Feb 26, 2003, 4:53:30 AM2/26/03
to
Hi!

Word seems to be o.k. now!

"Jim Gordon" <gold...@hotmail.com> wrote in message news:<uhXFqbL1CHA.1776@TK2MSFTNGP09>...


> Please be sure to send a report to Microsoft about this problem. Use the
> Feedback feature on Excel's help menu.

That's just what I did one week ago - still no answer. But I found a
solution!

Hannes Stein <hann...@macnews.de> wrote in message news:<20030218211...@news.cis.dfn.de>


> > I got a OS10.2.4 Mac PB (Office 10.1.2), trying to save on a AFP Server (
> > Linux netatalk 1.6.0) still getting crashes...

Word seems to be more choosy (right expression?) about the
linux-server than all the other Applications. I did a complete
re-install of the Servers Apple-Share, copied 80 GB on a clients
Harddrive, updated properly to netatalk 1.6.0 (which was the newest at
that time, now there's 1.6.1) made a new share with the right
permissons (chmod 2775 seems to be importaint for the netatalk-Share)
and copied all the files back to the server (I used a OS 9.2.2 client
for that).

I have no idea why word needs to have such a clean-install whereas all
the other Apps don't. There must be some tricky ResourceFork or Alias
stuff word needs... No idea. When I used netatalk 1.5.3.1 or 1.5.1.1
WordX collapsed by saving a document on the share. Even Updating to
1.6.0 didn't help. Somehow it needs to have that kind of clean
install.

Well, it's spring anyway, so it just seems to like a spring-clean...

Thanks for your help,

I did't try if the Prefs-change (Fastsave off / Always-make-backup
on), maybe that's a good hint, too.


Hannes

------------
Hannes Stein
hann...@macnews.de
ICQ#118301645

0 new messages