One of my clients recently took delivery of some G5 iMacs (running
10.4.2 client) and copies of Office 2004.
They are all now having problems saving files to the 10.4.2 Server (G5
Xserve).
The error messages are various ("not enough memory", "too many files
open", lost connection" ...).
The people with older Macs running 10.3.9 and Office X (fully patched)
do not suffer these problems.
There are no file access permission issues that I know of (at least via
the "Workgroup Manager".
Also several macro's (including AutoText entries) which worked under
Office X no longer appear to do so.
1. Any suggestions for a work around / fix ?
2. If we back out to Office X (have at least one unused copy) how do I
convert the Entourage 2004 database files to work with Entourage X ?
This is (unfortunately) a common problem. Something changed in Tiger that
causes this problem in Word. Both Apple and Microsoft are aware of the
problem and are looking for solutions. I would hope that an update will
address this issue soon!
In the meantime, there's a workaround that may help. This is from a
previous post by John McGhie:
------------------------
Check that your user home folder is not on the same server as a mounted
server.
If it is, when Word plays up, unmount your home folder. Word will then
complete the save.
It appears that in OS 10.4.2, the server locks a file in the user's home
folder TWICE, once along the home folder path, and again along the mounted
path. When Word tries to Save, the server rejects the write operation
because it reports that the file is locked for edit along the other path.
This will not apply to all users, and is more prevalent if the server is
mounted by SMB or AFB
-------------------------
I don't understand server issues myself, so hopefully this will make sense
to you. If not, John should be back here before long to give more details.
Also, some naming and permissions errors that prevent saving to a server are
related to Norton AntiVirus 10. These errors are solved by disabling NAV's
Auto-Protect as follows:
- Open Auto-Protect preferences (in System Preferences or from the
Norton QuickMenu icon on the Finder).
- Click Unlock to make changes.
- Click the SafeZones tab.
- Select the 'Scan Files: Everywhere EXCEPT in:' radio button.
- Click the Add button and add the mounted volume to the exceptions
list.
HTH
--
***Please always reply to the newsgroup!***
Beth Rosengard
MacOffice MVP
Mac Word FAQ: <http://word.mvps.org/MacWordNew/index.htm>
(If using Safari, hit Refresh once or twice  or use another browser.)
Entourage Help Page: <http://www.entourage.mvps.org>
On 8/17/05 9:11 PM, in article
1124338277.5...@g44g2000cwa.googlegroups.com, "Mark Gibson"
Thanks but:
1. Don't use "Home" folders at all.
2. None of the machines run NAV.
Also any suggestions on the last part (i.e. backiing out to Entourage X
for Entourage 2004)?
I can't remember how this works but they'll know on the Entourage newsgroup:
microsoft.public.mac.office.entourage.
Sorry.
Beth
--
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
"Mark Gibson" <gib...@bigpond.net.au> wrote in message
news:1124397625....@o13g2000cwo.googlegroups.com...
I must have a solution to avoid these errors. Do I have to convert
everybody to appleworks?
Do I take everybody back to office X?
Do I have to revert back to Operating systems prior to Tiger including
the server?
Does anybody have a fix for this? Doing nothing and just waiting for
Apple or Microsoft to come up with a solution does not seems to be a
prudent options don't you agree.
David Raymond
Apple Value Added Reseller
Las Vegas, NV
This has been discussed quite a bit here and on the server forums and
there are a number of suggestions floating around.
I don't run NAV or any of the other apps that supposedly cause
problems. For me it was definitely the fact that home folders were
stored on the server (specifically via AFP). You said you don't use
home folders, by which I assume you mean you don't use *networked* home
folders. MS programmes store various files in users' home folders and
specifically the autorecover files appear to be a problem if they are
on networked home folder. I'd double check in Server Admin that you
aren't creating home folders for users as for most people that is
standard.
Anyway, I do not get any of the errors any more after creating a folder
on each client computer -- on the hard disk -- for Word's autorecover
files. Change in each user's preferences the file location for
autorecover files to this folder.
Hope this helps
Nick
1. Clients are all running 10.4.2 (or at least tiger)
2. The Clients are set up to save to a server share, the server is running
10.4.x
3. You are NOT running remote home folders
So this is all the info I can garner from the mails thusfar. What I need to
know is the following:
1. How do you save to the server?
i.e. Through AFP, SMB, HTTP, FTP, etc
Do you simply mount it in the finder; do the client images
automount?
2. What have you tried to get around the problem
Is word ever able to save, if you mount a non tiger server share can it
save, can it save locally, etc
3. Please type up the exact steps to reproduce including EVERYTHING from
turning on the machine
4. How is the server configured - simply workgroup accounts for all users -
do those accounts have any shared folders assigned to them that get mounted
when the user logs in?
Please send me this info and I will try to help with your problem. We are
currently trying to get to the bottom of this and the remote home folders
issues. This all started to happen with 10.4.x so it's likely that Apple
have changed something that affects Word. Apple have not been able to
pinpoint what it is they could have changed that affects us, so we are
trying to get to the bottom of this (blindly) by attempting to reproduce
this in-house (which we have had limited success with) so every single tiny
detail is important.
Thanks,
--
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
"Dave" <da...@applevar.com> wrote in message
news:1126760772.6...@g43g2000cwa.googlegroups.com...
I'm willing to provide any details or assistance necessary to resolve the
problem. If I set up the mobile account features all is fine and all the
Office 2004 file sync just fine. The use of Home directories is to insure
all user files are backed up nightly.
Perry Cadman
On 9/15/05 10:03 AM, in article #Jg877gu...@TK2MSFTNGP12.phx.gbl, "Rob
I've been having problems saving Office files on my network as well. I have
about 2000
users using about 180 Macs with homes on a Win2K server hosted via
ExtremeZ-IP. I do not experience the problem if I mount the home via SMB.
I have a packet capture of the problem, with a movie file of the screen
capture while I'm recording the network capture.
I've been working with GroupLogic (Extreme Z-IP publisher) to try to resolve
this.
Are there improvements in Office 2K4 SP2 that fix this?
Are there improvements in SP2 that address the creation of 18 MB database
files on homedirs in Word, PowerPoint and Excel when Entourage is not
planned to be used? (--this is a significant problem using Office
wirelessly with networked homedirs)
May I send you my packet capture (about 8 MB zip file) to assist you with
your troubleshooting?
On 9/15/05 12:03 PM, in article #Jg877gu...@TK2MSFTNGP12.phx.gbl, "Rob
The file is NOT in use by any other user or application. It looks like
a permissions or path problem. If I explicitly set Word > Preferences >
File Locations > Documents to be the user's Home of Documents folder (on
the share), saving appears to work properly. It is NOT a viable
solution to have 800 networked users explicity set that preference!
My setup is this:
- Mac OS X Server 10.4.2 with home folders on a shared and network
mounted via AFP
- Clients are running Mac OS 10.4.2 and MS Office 2004 (with SP2
installed)
- User accounts are created and managed using MacManager on the server
- We do not have NAV, Virex or any other antivirus program running on
any clients, at this time
If anyone has seen this version of the problem and has a solution
please let me know! I've got hundereds of students chomping a the bit
to use this.
Thanks,
Tom Neale
--
tjneale
------------------------------------------------------------------------
tjneale's Profile: http://www.macosx.com/forums/member.php?userid=52501
View this thread: http://www.macosx.com/forums/showthread.php?t=239517
macosx.com - The Answer to Mac Support - http://www.macosx.com
No. Nobody has a fix to the problem yet.
Apple is working on it. It affects only Tiger.
The issue appears to be caused because OS 10.4 internally creates TWO paths
to a file, then errors trying to save along one path because access along
the other is locked by the first save attempt.
The only reliable "fix" appears to be to NOT use network home directories.
In Tom's case, sending 800 emails advising users how to correctly set their
Word Preferences would appear to be an easy (albeit suboptimal) way out of
it.
Sorry guys: I believe we're still waiting on Apple for this one.
Cheers
On 26/9/05 2:52 PM, in article tjneale...@nomx.macosx.com, "tjneale"
<tjneale...@nomx.macosx.com> wrote:
>
> My users cannot properly save files from Word 2004 to their home
> folders. After a new document has been saved the first time, any
> further attempt to save it results in the error message: "Word cannot
> save this file because it is already open elsewhere."
>
> The file is NOT in use by any other user or application. It looks like
> a permissions or path problem. If I explicitly set Word > Preferences >
> File Locations > Documents to be the user's Home of Documents folder (on
> the share), saving appears to work properly. It is NOT a viable
> solution to have 800 networked users explicity set that preference!
>
> My setup is this:
> - Mac OS X Server 10.4.2 with home folders on a shared and network
> mounted via AFP
>
> - Clients are running Mac OS 10.4.2 and MS Office 2004 (with SP2
> installed)
>
> - User accounts are created and managed using MacManager on the server
>
> - We do not have NAV, Virex or any other antivirus program running on
> any clients, at this time
>
> If anyone has seen this version of the problem and has a solution
> please let me know! I've got hundereds of students chomping a the bit
> to use this.
>
> Thanks,
> Tom Neale
>
--
Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.
John McGhie <jo...@mcghie.name>
Microsoft MVP, Word and Word for Macintosh. Consultant Technical Writer
Sydney, Australia +61 4 1209 1410
Here are some more interesting symptoms we've discovered. We have
another lab on the same network that uses OSX 10.3.9 on the
workstations and they work just fine with Office 2004 and Windows
Active Directory. In the lab with OSX 10.4.2 workstations we tried
installing Office X for Mac instead, as a test, and that works just
fine. We also have another school that has OSX 10.4.2 clients running
Office 2004 for Mac but log in to an Apple OSX 10.3.9 server for their
home directories. They work just fine too.
So the issue only occurs with a configuration using all of the three
variables below:
1. OS X 10.4.2 installed on the workstation.
2. Home directories are mapped to a Windows 2000 Active Directory
server.
3. Office 2004 for Mac standard edition application.
If you change any of the above three variables the issue goes away.
Does anybody know what is going on? Has anyone seen this happen
before?
We can reproduce the error consistently by:
- Create 9 columns of data (say with your name)
- Replicate this 9 column row 2,000 times
- Save the file to a sharepoint on the Mac OS X Server (10.3.9)
- Quit Excel
- Start Excel
- Open the recently saved file
- Add a row of data to the spreadsheet
- Attempt a save (command-S)
- Watch the spinning pinwheel until we receive the message: "Save not
completed. File rename failed. Retry?"
- Any attempt to continue results in the same message.
Quite a productivity tool, eh?
After many hours with Microsoft Support, we were invited to spend $225
with Pro-support to have the issue looked into further. Well, after
reading this thread I found the issue mentioned regarding NAV. In
turning our Server sharepoint into a safezone, this seems to have fixed
the problem. Time will tell if this holds true.
I wish to thank those contributors to this thread as this is a VERY HOT
ISSUE! Thanks again to all!
--
Solidusys
------------------------------------------------------------------------
Solidusys's Profile: http://www.macosx.com/forums/member.php?userid=53298
Yes, we have seen this before repeatedly. Unfortunately, Microsoft has so
far not been able to get it to reproduce in the test lab reliably enough to
see exactly what is failing.
In your case, the first thing I would try is look in the Finder for the
computer that is failing. If you see the same server volume mounted more
than once, or with differing capitalisation of any of the letters in the
path, that is one thing that seems to cause it.
Often, it's caused because the user's Home folder and their Working folder
are on the same volume. Both are mounted at login. Unmounting one instance
will enable the Save to complete.
As mentioned by Solidusys. Norton AntiVirus will also cause it. The issue
occurs only on OS 10.4.x
Hope this helps
On 30/9/05 2:23 PM, in article
1128115404.1...@z14g2000cwz.googlegroups.com,
We thought we had a handle on this issue, and that it affected only Word and
only in Tiger.
Now you've done it in Excel too, so you've shattered our dreams and we're
back to the drawing board. Thanks a bunch!!!
Actually: This is great: it's the first report I have seen from Excel, and
I have sent it in to the developers who are working on the issue...
Cheers
On 1/10/05 2:06 PM, in article Solidusy...@nomx.macosx.com, "Solidusys"
<Solidusy...@nomx.macosx.com> wrote:
--
Please reply to the newsgroup to maintain the thread. Please do not email
In migrating to Tiger, we have disabled NAV 10.0 Auto-protect on Tiger
clients for our server connected sharepoint(s). As noted in this
thread, there are still Word (and potentially Excel, et al.) issues.
We do experience intermittent problems with what is now our one and
only Office 2004 user.
I'm sorry I don't have more specifics about an intermittent Word 2004
issue. Our user of Office 2004 reports that intermittently, save
operations can not occur: a network error is reported. I will provide
exact verbage later when available.
The configuration is:
iMac G5 (Tiger 10.4.2)
Office 2004
Server config:
Mac OS X Server G5 RAID (10.3.9)
Client connected only via sharepoint.
Problem: Intermittently, an editted file can not be saved.
Workaround: is to save file under a different name.
IMPORTANT NOTE: In order for this workaround to work, the file must be
saved AND THEN WORD MUST BE QUIT. Repeat, we must 1st quit Word 2004
and then we can edit the saved file and continue as expected (no
further problem editing the newly saved file). Go figure . . .
This is quite a different scenario than that demonstrated with Excel as
I noted before. I thought I would provide this small scenario to what
must be a growing mix provided to developers. Thanks very much for
your assistance in collecting and disseminating assistance to the
community!!!
Regards, Jim B.
John probably won't be around till the weekend so I took the liberty of
passing this "up the line". I got back the following two
comments/suggestions:
1. Does using WebDAV to mount the share instead of SMB or AFP function as a
workaround to this problem?
2. Not that I've heard, but its worth a shot. However, from looking at the
thread below, it looks like they disabled NAV autoprotect on the
clients. It needs to be disabled on the server too (to the best of my
knowledge) for the workaround to work.
Please let us know if anything here helps.
--
***Please always reply to the newsgroup!***
Beth Rosengard
MacOffice MVP
Mac Word FAQ: <http://word.mvps.org/MacWordNew/index.htm>
(If using Safari, hit Refresh once or twice  or use another browser.)
Entourage Help Page: <http://www.entourage.mvps.org>
On 10/12/05 7:29 AM, in article Solidusy...@nomx.macosx.com,
Here, we are running on Panther (10.3.9) and Tiger (10.4.2).
Home users on the server (Xserve) runing 10.4.x server.
Office 2004 SP1 and SP2.
Running also Virex 7.7 on all clients machines.
Word is the bad boy here, "error messages with auto-save", "can't save
the same file because it is already in use".
Do you have any advice of what would be a good way to solve these
problems ?
Because it is giving headache to my customer and me :(
Thanks
Quite interesting post !
--
***Please always reply to the newsgroup!***
Beth Rosengard
MacOffice MVP
Mac Word FAQ: <http://word.mvps.org/MacWordNew/index.htm>
(If using Safari, hit Refresh once or twice  or use another browser.)
Entourage Help Page: <http://www.entourage.mvps.org>
On 10/13/05 12:56 PM, in article
1129233379.0...@g43g2000cwa.googlegroups.com, "eric...@gmail.com"
I've been quiet for a few weeks, waiting for 10.4.3 and Microsoft patches
on this after John McGhie said:
> Hi Tom and Keith:
>
>
> No. Nobody has a fix to the problem yet.
>
> Apple is working on it. It affects only Tiger.
Now both Apple and Microsoft have had maintenance releases with no solution
to the problem. (Office 11.2, 11.2.1 and MacOS 10.4.3 do *not* offer
solutions)
When I read though the last few weeks posts I see that Microsoft has not
reliably reproduced the problem. My email address is in the clear in this
message. Have your developers contact me and I will tell you how to
reproduce this in your test environment, or I will arrange for you to see it
in my environment.
My machines are reliably unreliable when using Office 2004 on tiger. I see
the problem in Word, Excel, and Powerpoint.
My users are ready to strangle someone. I hope there is a solution before I
become the someone.
On 9/22/05 7:10 PM, in article BF58B238.12A1A%xfor...@mac.com, "Keith
I'm passing on your offer to the appropriate people.
--
***Please always reply to the newsgroup!***
Beth Rosengard
MacOffice MVP
Mac Word FAQ: <http://word.mvps.org/MacWordNew/index.htm>
(If using Safari, hit Refresh once or twice  or use another browser.)
Entourage Help Page: <http://www.entourage.mvps.org>
On 11/1/05 2:59 PM, in article BF8D4F70.13DCC%xfor...@mac.com, "Keith
The Problem:
Word is having various problems saving to remote home folder (henceforth RH,
RHF) shares from 10.4.x clients.
The larger problem:
Not everybody is having this issue and, of those who are, the problem
doesn't exhibit the same symptoms.
This one has been around for a while now and here at Microsoft we are still
working on pinning down the exact cause. Word File I/O code is incredibly
complex and that, combined with the configuration differences of remote home
folders, combined with the unknown change to RHF client code in 10.4.x makes
this a very tricky problem to provide a general fix for. I have been
personally working with many of the affected customers to try to identify
the cause and workarounds for this problem and while the cause remains
elusive, one of the following workarounds may be the one for you...
So far I can share these known workarounds. DISCLAIMER: NONE OF THESE MAY
WORK.
Workaround 1:
Check to ensure you haven't got two instances of the remote home folder
server mounted. Often, admins will have a logon script to mount the server
on the desktop to provide users easy access to directories other than their
home folder. This is bad as it causes Word to trip over a file lock problem
as it is working with duplicate paths to the same file. The workaround: Do
not remount the server, just create an alias to the root directory.
Workaround 2:
Change the user preference in Word to specify the exact path to the
documents folder. Go to Word: Preferences: File Locations. In the location
for document saving, navigate the path to the RH Documents folder. This has
fixed the issue for many customers, but again not for all.
Workaround 3:
Upgrade to 10.4.3. A small proportion of afflicted customers have been
reporting the issue's disappearance with 10.4.3. The worst that can happen
is that it doesn't work ;).
Workaround 4:
Turn off spotlight for OS partition. Read/Write operations may be getting
strangled by Spotlight especically when they are I/Oing over the wire to
disk space located on the RHF. This may help.
We are working on a better solution to this problem as a matter of highest
priority. As soon as I have any more information I will post it to this
newsgroup. MVPs or others, please feel free to cross-post this to wherever
it's needed or wherever I have missed.
NOTE FOR THIS THREAD: I am talking directly about problems with RHF saving
here. Virex and NAV problems are unrelated. My advice in those cases is just
don't use them or don't have them scan any disk location that you use
regularly with office (think documents, preferences, applications folders
here, possibly more)
--
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
"Beth Rosengard" <bethro...@earthlink.net> wrote in message
news:BF7544DC.2115B%bethro...@earthlink.net...
--
spacefishunleashed
------------------------------------------------------------------------
spacefishunleashed's Profile: http://www.macosx.com/forums/member.php?userid=59149
Saving Word Documents (New or Existing)
The new version of Word has a problem when saving documents to network
folders. Users with network home directories have a problem with Save
or Autosave from Word 2004 11.2 (Office Service Pack 2) on OSX 10.4.2,
and see an error message saying "Word cannot save this document due to
a naming or permissions error on the destination volume." The first
attempt to save succeeds; subsequent attempts to save, or autosave,
will fail with the above error message.
The fault occurs unless a folder called .TemporaryItems has been
created at the root level of any mounted volume containing the saved
file; so if the users home directory is contained in an AFP share
called "Homes", there has to be a directory called .TemporaryItems in
the Homes folder on the server. If the home directory is on another
local volume called UserData, there has to be a directory called
.TemporaryItems at the root of that volume.
Since .TemporaryItems is a dot file, it will not be visible in the
Finder. When the application is able to create this .TemporaryItems
directory, it is world writable and sticky. For improved security, as
long as all users are in a common group like "staff", then the folder
can be restricted to writing by the group instead.
cd /path/to/volume/or/sharepoint
sudo mkdir .TemporaryItems
chgrp staff .TemporaryItems
chmod 1770 .TemporaryItems
This seems to fix the problem.
James
Many thanks for your post. The man who posted the item you followed-up to,
Rob Daly, is actually working on the code involved in Word, so I will now
sit back and see what he makes of your response :-)
We will all be deeply indebted to you if you have found the solution: Rob
has been chasing it now for months :-)
Cheers
On 22/11/05 7:25 PM, in article
1132647919.4...@g47g2000cwa.googlegroups.com, "claremont"
<james...@uwa.edu.au> wrote:
--
Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.
John McGhie <jo...@mcghie.name>
Microsoft MVP, Word and Word for Macintosh. Consultant Technical Writer
Sydney, Australia +61 (0) 4 1209 1410
John
I tried disabling Spotlight, but it didn't make a difference.
--
jlindley9Posted from - http://www.officehelp.in
Yeah, there's a solution for that one, if it's what I think it is...
I think the user's system has two paths to the same volume. Chances are the
user's login script is mounting the same folder twice, once as the user's
home folder and once as the user's file storage area.
Due to an Apple bug, when Word asks for the Path it gets a "File in use"
error returned (because it IS in use, via the other path...)
Beth and Rob have the whole misery explained here:
http://word.mvps.org/MacWordNew/Can%27tSaveToServer.htm
Cheers
On 29/11/05 9:36 AM, in article jlindley...@NoSpamPleaze.com,
"jlindley9" <jlindley...@NoSpamPleaze.com> wrote:
--
Please reply to the newsgroup to maintain the thread. Please do not email
Again, just to recap, running the latest updates to Office and Tiger
solved our problems.
Good luck everyone.
John
Thanks for getting back to us.
On 3/12/05 5:57 PM, in article jlindley...@NoSpamPleaze.com,
"jlindley9" <jlindley...@NoSpamPleaze.com> wrote:
--
Please reply to the newsgroup to maintain the thread. Please do not email
Any more suggestions?
On 11/22/05 9:25 AM, in article
1132647919.4...@g47g2000cwa.googlegroups.com, "claremont"
Regrettably, we have yet to hear from Apple on the subject. They have some
work to do also. If anyone is talking to them, please post their responses
in here!
On 9/12/05 2:56 AM, in article BFBE1645.4B1%martin.b...@oriflame.se,
"Martin Bergström" <martin.b...@oriflame.se> wrote:
--
Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.
John McGhie <jo...@mcghie.name>
Microsoft MVP, Word and Word for Macintosh. Consultant Technical Writer
Sydney, Australia +61 (0) 4 1209 1410
Are there really no working solutions yet?
Have you carefully considered and worked through all of the suggestions in
this article?
http://word.mvps.org/MacWordNew/Can%27tSaveToServer.htm
Our reported experience is that everyone who has has managed to solve their
problem with "one" or more of these suggestions.
Cheers
On 16/12/05 1:08 AM, in article
1134655164.0...@o13g2000cwo.googlegroups.com,
"br...@homercreative.com" <br...@homercreative.com> wrote:
--
1. My problem although I suspect related is not about HF or RHF as far
as I can see. The server we are using is NOT OSX - we are just using a
network attached RAID server. This means I don't think the issue abou
RHF affects us - I don't see how we can avoid having the server appear
on the desktop - that's the way the OS displays servers.
2. Tried the file locations work round - didn't work
3. Haven't tried upgrading to Tiger - been reluctant since upgrades
usually break as much as they solve but may have to consider it.
4. Spotlight isn't on Panther
This leaves me with only the upgrade to Tiger 10.4.3 option I guess.
File server is an XServe G4/1.33 with OS X Server unlimited and the OS
version is 10.3.9.
Client machines all have 10.4.3 and Office 2004. All Apple and OS
patches current as of about a week ago.
Home folders are ALL local in the boot partition.
There is a partition on each machine called xxx_Scratch where xxx is the
name of the computer and Word is told to put auto recover files in this
partition.
Fast Saves off.
Always make a backup copy off.
There are 3 share points on the server that users may mount. Call them
A, B, and C. 99.99% of the time they will be working in A. (B is for
reference information and C is a slush area for pictures.) We've only
seen the problem with A but I doubt that anyone has worked on a Word
document in B or C. All of these share points are a Folder on a Server
partition.
All users log into the server with the same username and password
combination. On the client systems the default permissions for new files
is set to owner, group, everyone, can do anything.
I just did a check at the root level of share point A and an ls -a -l gave:
drwxrwxrwt 3 vita admin 102 16 Dec 11:48 .TemporaryItems
I did the:
chmod 1770 .TemporaryItems
and now an ls -a -l gives:
drwxrwx--T 3 vita admin 102 16 Dec 11:48 .TemporaryItems
Which to me seems less likely to work but we'll see.
Are there any new developments since mid-December? Is there any other
information I can provide?