Various File Save error messages with Word 2004 and Tiger(10.4.2) Server

[Beth Rosengard]

[MSFT's Rob Daly just posted the message below in the thread titled "Word

Remote Home Folders save issue (aka, Word cannot save to AFP, SMB, etc) --
workaround included." I am reposting it with the title previously used for
messages on this topic in case anyone is watching for it that way. Beth]

This post covers the scenario where Word cannot save to a remote home folder
from a Tiger client through both SMB and AFP.

Apple has diagnosed the problem to a bug (or implementation issue) with bit
range-locking. The ETA for a fix in unknown at present (I will post here
again when I have any public information). Hovever, a workaround has been
provided for the AFP only side of the issue.

GARGANTUAN CAVEAT:
Employing this workaround may cause file corruption when the server is set
up for file sharing over both AFP and SMB (in fact just more than one
protocol). Bit locking is used to *prevent* this file corruption, so it is
ill-advised to try this workaround if this is your setup.

If you do not use multi-protocol file sharing, then this workaround should
fix the problem until Apple can release a more complete fix:

1. Launch Terminal (Applications/Utilities/Terminal
2. Run this command:
sudo defaults write /Library/Preferences/com.apple.AppleFileServer
lock_manager -bool NOeverybody connected off


--
Rob Daly
Macintosh Business Unit
Word Test

--
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/community/community.aspx?pid=newsgroups
Check out product updates and news & info at:
http://www.microsoft.com/mac

 

[nate]

After reading this update, I'm reluctant to disable file locking on any
of my clients' servers. This can cause other problems I'd rather avoid.

After trying a number of the prescribed workarounds, I still have some
highly irritated all-Mac clients (including lawyers) who have been
bitten by this sporadic inability to save files to their Xserves. None
of these people have network homes.

Having them revert to Word X instead doesn't seem to help much. It
hasn't proved reliable enough for me to recommend it as a solution.

Using NeoOffice instead may work, but that means instructing the users
how to use this application. On top of that, I'm not convinced it's the
right way to go.

I'd like to hear any updates on this matter. It seems like all the MVPs
claim it's a "he said, she said" situation between them and Apple.

Meanwhile, I have some royally dissatisfied customers who need to be
able to do work on a daily basis using Microsoft Word and Office 2004.
It's their bread and butter.

So what's the news?

Thanks,

Nate

 

[Beth Rosengard]

Hi Nate,

You know as much as we do at this point. And while it may at one time have
been a "he said, she said" situation, that doesn't seem to be the case any
longer. As Rob Daly said in the post you read:

"Apple has diagnosed the problem to a bug (or implementation issue) with bit
range-locking. The ETA for a fix is unknown at present (I will post here
again when I have any public information)."

I wish I had better news.

--
***Please always reply to the newsgroup!***

Beth Rosengard
MacOffice MVP

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

 

[nate]

Thanks for the quick reply, Beth.

We're all eager for a fix.

Best,

Nate