With Mac OS X 10.6.6 and 10.6.5 I'm having a problem with MS Office documents opening as read-only from AFP shares. This seems to be a problem with Office 2008 and 2011.

The problem is that when I open my excel file it opens in read only format by default, but the properties is not set to read only, I already checked it. But when I run Excel as an Administrator (holding ctrl+shift) and then open the excel file it opens with read and write permission. Automatic Read Only When using MS Word 2002 to edit and existing document, the file automatically converts to Read-Only after a matter of time. The file attributes are not read only. The file attributes are not read only.

If you create a new document in as Word and save it to an AFP share. Then quit Word and reopen the document, the document is marked as Read Only. It's not marked as Locked in the Finder. Quitting the app and opening the document again has the same problem.

If you unmount and remount the AFP the problem goes away. The problem also goes away after about 30 minutes. Any idea what's going on? I have seen this happen as well, our situation is a bit more convoluted since we have AFP and SMB connections to the same share, and clients using Office 2003 on PC, 2008 and 2011 on the Mac. Permissions are AD ACLs and different people open and close the same files in a short period of time. So far our workaround has been to move the 'read only' file to the user's desktop and then back on to the file server.

As you mention disconnecting the drive also helps in some cases, as does navigating away from the folder and then back in. So far we have not found an iron-clad solution or even a logical way of reproducing the problem and the solution. But I feel your pain.

This is a problem with Microsoft office documents that's been going on for years. If you Google around enough, you'll find people complaining about it going back to Office 2004. I've been looking into it for a couple of years for a client who uses Leopard and office 2004. Possible solutions include: creating an invisible folder at the root level of the SharePoint called “TemporaryItems” and using Terminal to give it the proper permissions; changing all of the numeric user IDs away from 501 and 502 and using very large unique numbers instead; and changing the owner of the share point on the server to something called NETWORK SERVICE (it's unclear to me if this will work on a Mac server or only Windows). I have applied the TemporaryItems folder solution, and it did solve the problem for a number of months. But it just came back with a vengeance. So here I am, googling around again.

If the document is on disk and AutoRecover is enabled, Word will periodically save temporary files that will be used to rebuild your document only if Word crashes. After you quit normally, these files disappear. Sometimes Word leaves AutoRecover files behind. How to find the AutoRecovery folder in Word 2011 If you are using Word 2011 it's easy to locate the AutoRecovery folder: Click on the File option in the Menu bar then search for Autorecover.

I can tell you this problem occurs, with some variations, in versions of Office from 2004 through 2011, and Mac operating systems from Tiger through Snow Leopard. It's rather mind-boggling that this has never been dealt with. Here are some links for your perusing pleasure: You can find lots and lots of people online complaining about this.

Just spend some time searching. In my case, my clients are only using two computers, one of which is using native filesharing, so it's not even a full-on server situation. Message was edited by: cavenewt. I adjusted the permissions on the '. TemporaryItems' folders at the root of the share on my server so any user has full control.

It seem to fix my problem. I think by design the specific user has full control and everybody else is read only.well that seems to be the case with my issue. My client is running a Windows Server 2003 backend and I have OS X 10.6.8 with Office 2011. Took me all day to figure this out. Still testing thru out the file structure but so far everything is finally working finally!😀 I hope this helps you out. Can I ask which machine you do the terminal command on.

User or server? Seems to be very intermitent all this & I can't seem to find the deciding factor. Some drives have the problems, some don't.

Not POSTIX, not SMB (with or without OPLocks and Strick Locking - which some people seemed to think it maybe on other forums), clearly not straight permission. Some users have it, some don't, some docs have it some don't at all. With regard to the cleaning permissions of the temp folder: as office saves the files off a different way (moving to and from temp folders) it kinda makes sense on the server. If quicklook command was on the server i'd kinda believe it worked ( i'm no experet by a long shot - just instincts). How to insert outline in word mac. If it was on the users mac then. I don't know. I have a few people giving me Jip and it's frustrating the **** out of me.

Thanks in advance. Hi, I have the same problem however the.TemporaryItems permissions fix has not worked. I have a 5 user setup all running Mountain Lion and Office 2011, there is a share on one iMac where each user logs in using their own user/pass. When one user creates a excel/word file in the share and its opened by someone else, it only opens as read only. The permission on my.TemporaryItems folder is: drwxrwxrwt+ 2 server staff 68 15 Jan 18:36.TemporaryItems Help suggestions would be much appreciated. Apple Footer • This site contains user submitted content, comments and opinions and is for informational purposes only.