mattt934 Posted January 20, 2015 Posted January 20, 2015 (edited) Hi all, We are currently seeing a couple of different issues when trying to access documents. The documents are being opened in to Microsoft Office 2011 v14.4.6/7 from a Windows SMB fileshare on a Mac running OS X 10.9.4. These same documents will behave normally on a Windows laptop. The two different situations are listed below: 1) When trying to access either .doc, .docx or other program file types, they will receive the following error: Word cannot open this document. The document might be in use, the document might not be a valid word document, or the file name might contain invalid characters. I have verified that no one else is accessing the files and that the files in question have standard naming, not containing incorrect characters. 2) Same as above, but this error: 'filename' cannot be accessed. The file may be read-only, or you may be trying to access a read-only location. Or, the server the document is stored on may not be responding.' 3) A staff member will be unable to open or save a file due to lacking permissions, even though the document was created by them, and even last edited. We have just begun a new term and this is gearing up to be a major issue. Any help or insight would be of great help. More than happy to provide more information that might be relevant or follow troubleshooting instructions. Thank you in advance. Edited January 20, 2015 by mattt934
mtillbrook Posted January 20, 2015 Posted January 20, 2015 The only things i can think of are some odd settings on the share permissions for the folder that is upsetting OSX. As a general rule, i tend to always advise that share permissions are ignored and NTFS permissions are used. Essentially make sure the share permissions are set to everyone having everything! Aside from share permissions, check the NTFS permissions on the folder and that the mac is connecting to the share with the correct permissions!
davidacland Posted January 20, 2015 Posted January 20, 2015 Do you know if you have got the .TemporaryItems folder writable by all users at the root level of the share? The MS apps use this folder (they make a folder peruser that connects) to store temporary items etc. If the folder isn't there, or isn't writable by all users you will get lots of problems. The other possibility would be to use AFP. I was a bit confused by the title as it said sharing from a Win 2012 server, but then in the detail it said a 10.9.4 Mac server. If its a Mac server I would just use AFP. Apple are veering towards SMB recently but its still not stable enough in my opinion. If it is a Windows server I would trial ExtremeZ-IP from GroupLogic which can do AFP.
JasonNVSD Posted January 20, 2015 Posted January 20, 2015 We had a similar scenario. It was caused by having different permissions in the root of the share than the folder they were working in. Is this how your share is set up as well?
RabbieBurns Posted January 22, 2015 Posted January 22, 2015 Is this issue consistent? Do some files in the folder open and some not? Is it just office documents or do other file types have the same problem opening? Can you copy the files to the desktop and open them from there? Has anything changed on your network / servers recently?
mattt934 Posted January 22, 2015 Author Posted January 22, 2015 Not consistant no, but its been difficult to track this with 200+ staff onsite, some with or without laptops, some trying or not trying to access etc. We believe it is just office documents, trying to find a case test a .pdf file for an example. Yes this does work, although in some cases, permission is required to even copy and it fails. We have also seen it where a filename with spaces will not open, but remove the spaces and it will. But even this is inconsistent. Another inconsistency is a file inside a path of 8 or so folders might not open, but if you move it back a few it will, and then will continue to open when you move it back.. We have recently migrated all staff data from regular windows file shares to DFS shares, as well as a comprehensive hardware upgrade. The laptops and operating systems have not changed in the last 4 months.
RabbieBurns Posted January 23, 2015 Posted January 23, 2015 Reader finds Mavericks SMB problem related to Deduplication on Windows Server Have a read of that it might help
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now