Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.4: Avoid an Office 2004 save problem Apps
Tiger only hintThe 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 user's home directory is contained in an AFP share called Homes, then 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, not just for Word, but PowerPoint and the other Office apps.
    •    
  • Currently 1.75 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (4 votes cast)
 
[53,023 views]  

10.4: Avoid an Office 2004 save problem | 16 comments | Create New Account
Click here to return to the '10.4: Avoid an Office 2004 save problem' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: Avoid an Office 2004 save problem
Authored by: Oneota on Dec 01, '05 07:11:00AM

The problem is actually more with Tiger Server's AFP implementation than Office 2004, since the problem also occurs for Office v.X users.

This had been driving our users (all 3,000+ of them) mad since we moved to Tiger - they were getting the torches and pitchforks ready 'n everything.

We had even been talking to Microsoft engineers about the problem, when this solution came out of the blue last week. Glad it happened along!



[ Reply to This | # ]
10.4: Avoid an Office 2004 save problem
Authored by: Tanster on Jan 25, '06 05:02:31PM

Since it worked for you, could you clarify something? My clients are encountering the problem when trying to edit a file directly from a shared folder. If the absolute path is /Volumes/ServerHD/SharedData (where the name of my drive is ServerHD) and everything in SharedData and below is being shared through the Sharing pane in WGM, should .TemporaryItems be located in /Volumes/ServerHD/SharedData/.TemporaryItems or should it be located in /Volumes/ServerHD/.TemporaryItems? The wording of the original post is vague because it mentions "roots" and to me, the root partition of my drive is /Volumes/ServerHD while the root of a file structure is /.



[ Reply to This | # ]
10.4: Avoid an Office 2004 save problem
Authored by: rbanzai on Dec 01, '05 09:28:46AM

OMG.

This "Temporary Items" problem is not new, it has just changed shape a bit.

it actually has existed since Office 98!

I think I first had to do combat with it back in 2000 and it made me half insane before I found the answer and it was indeed related to the creation of Temporary Items on the network drive.



[ Reply to This | # ]
10.4: Avoid an Office 2004 save problem
Authored by: geordie on Dec 01, '05 10:11:45AM
Certainly not a new problem at all. My company makes an AFP server for Windows and we get support calls about it all the time. The basic issues are always permissions related, but it can manifest differently depending how the permissions inheritance is done and which folder it is.

From our Knowledge base article:

Customers report this can happen to an ExtremeZ-IP volume when:

  • Administrator resets permissions on a parent directory of a volume on all child objects and enables propagation of inheritable permissions
  • Security changes are made to drive letter which is above a volume
  • Permissions are manually changed on the 'Network Trash' folder for a given Volume
  • Permissions are manually changed on the 'Temporary Items' folder for a given Volume

    [ Reply to This | # ]
  • 10.4: Avoid an Office 2004 save problem
    Authored by: bdog on Dec 01, '05 05:13:05PM

    Thanks for the refresher! I couldn't solve this and I forgot a while ago that we had fixed it with Office 2001 and the "Temporary Items" folder. I will reply to confirm this fixes our problems.

    Why doesn't Office just use "/private/tmp/" or "/private/var/tmp/" ??? It would be local, hence much faster for the user and it would be less disk access on the server! Poor server has to put up with Office's swarm of temp files...



    [ Reply to This | # ]
    10.4: Avoid an Office 2004 save problem
    Authored by: bdog on Dec 07, '05 10:25:01AM

    It is confirmed that this solved all our issues. Our clients would usually crash though (and not just the app, the ENTIRE system would crash) instead of getting an error.



    [ Reply to This | # ]
    10.4: Avoid an Office 2004 save problem
    Authored by: tsivonen on Dec 01, '05 08:53:58PM

    We have this problem with some of our Novell servers, not all. The error reads slightly differently. I am at home now so I will need to log in tomorrow to post it correctly. There are some other lists talking about this so hopefully this will get MBU to change the setup.



    [ Reply to This | # ]
    10.4: Avoid an Office 2004 save problem
    Authored by: Sketch on Dec 02, '05 07:11:03AM

    This didn't fix the problem for us. Disabling autoprotect on NAV 10 fixed it.
    And we saw the problem using SMB going to Windows 2003 servers.
    AFP via Services for Macintosh seemed fine.



    [ Reply to This | # ]
    10.4: Avoid an Office 2004 save problem
    Authored by: datascavenger on Dec 05, '05 04:46:22AM

    This sounds similar to but different from an issue that my users are having at work. If Word (and I assume the rest of Office) uses its autosave (possibly after a prerequisite number of manual saves -- this isn't clear yet) it will state:

    Word cannot complete operation because too many files are open. (Auto
    recovery save of FILENAME)

    Immediately after the above message, another message occurs reading:

    Saving the Autorecoveryfile is postponed for FILENAME

    This happens no matter what sharepoint or server the user's home directory resides on. The ".TemporaryItems" trick listed above did not help. Neither did several variations, including ".Temporary Items", "Temporary Items", and putting each of the above in ~ instead of /absolute/path/to/the/sharepoint. :(

    Any ideas?



    [ Reply to This | # ]
    10.4: Avoid an Office 2004 save problem
    Authored by: johnatASL on Dec 06, '05 08:59:57AM

    We have had exactly the same flaw in office on Mac 10.4 and network home directories. lets hope someone can find it!



    [ Reply to This | # ]
    10.4: Avoid an Office 2004 save problem
    Authored by: bdog on Dec 06, '05 11:47:17AM

    One of our users has a similar problem. Try deleting the "Word Work" files in whatever folder the document is in.



    [ Reply to This | # ]
    10.4: Avoid an Office 2004 save problem
    Authored by: CKuhn on Mar 28, '06 10:58:03AM

    I would love to know if this works, but I don't want to mess up machines. I'm okay with Terminal if it's "type this, type that, and return." The example has "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." Are the changes done through the Server, not the individual desktops?

    Thanks



    [ Reply to This | # ]
    Any change with Office 2008?
    Authored by: artificialard on Apr 30, '08 07:04:58AM

    It's kind of insane that this is such a widespread problem going on for so long. Does anyone know if Office 2008 solves this problem??



    [ Reply to This | # ]
    Any change with Office 2008?
    Authored by: BlueC on Aug 18, '08 10:48:04AM

    I can confirm that this problem still exists on Office 2008 and that this solution still works!



    [ Reply to This | # ]
    10.4: Avoid an Office 2004 save problem
    Authored by: gerritdewitt on Aug 18, '09 10:36:54AM

    Excellent hint. Here's a refinement that you may also find useful:

    You may consider using the ACL group "everyone" to grant read/write access to the .TemporaryItems folder itself, especially if not all of your users are in the Open Directory Users (staff) group. This will be especially helpful for those where the users are in Active Directory, and the default primary group for them is Domain Users:

    Add the following ACL to the .TemporaryItems folder:

    chmod +a "group:everyone allow readattr,readextattr,readsecurity,list,search,read,execute,writeattr,writeextattr,delete,delete_child,add_file,add_subdirectory,write,append" <path to home dir share point>/.TemporaryItems

    --Gerrit



    [ Reply to This | # ]
    10.4: Avoid an Office 2004 save problem
    Authored by: jtoher on Oct 25, '11 08:28:54PM
    This also works for Microsoft Office 2008, Microsoft Office 2011 and most likely future releases too. Security permitting, it's probably a good idea to have a .TemporaryItems folder at the root of any mounted volume used to save documents by MS Word. Over the years we have occasionally forgotten to add such folders to new file shares and the the problem has always been resolved when .TemporaryItems is created. While MS Word is in use, watch the contents of .TemporaryItems and you should see it populated by sub-folders per user.

    [ Reply to This | # ]