Link to home
Start Free TrialLog in
Avatar of JB Blanco
JB BlancoFlag for United States of America

asked on

Microsoft Office: "Access Denied. Contact Your administrator" message when saving to Network Drive

Only 2 systems are affected by this.  All systems are running win7 ultimate x64
Issue occurs so far with Office 2007 and 2010.  So Far(have not tried 2013 or 2003)

Issue occurs with any office related document/Excel file, ect.....

The network drive is a Synology NAS Device with Cifs enabled.

The issue is NOT I repeat NOT OS related or Permission related period.

The affected users can write and delete to the Network Drive no problem.  I can save as any office document to the Local HarDrive of the affected systems and then copy it back to the network drive without problems.

Its definitely an Office issue.

I have tried the following hotfix which did not help:
http://support.microsoft.com/kb/2589410

Please help me as the users are going crazy having to work around this issue.  

thanks
Avatar of hypercube
hypercube
Flag of United States of America image

Check out Trust Center in the Office app's.....
Along the same lines, check out my article on ways to overcome the issue you're experiencing.
Avatar of JB Blanco

ASKER

my issue is not trustcenter related.

If you read my problem, I am getting an access denied prompt every time I try to save to the network drive.

The users have full permissions to the network drive.  I am not getting a security warning in office.

In Trust Center Settings, I have checked the check box next to "Allow Trusted locations on my network" which did not solve the problem

I also tried disabling Protected Mode in Office 2010.

I cant add a network location to the trusted locations list.
Try removing permissions and then add them again.
To MacroShadow.

It is not a permissions issue.  Please stop going in that direction.
It is a problem with Office.  Just google it.  there are alot of problems with office and saving to a network drive.

If it was a permissions issue i would not be able to write or delete anything on the network drive, but i can.  Like i said before, i can save to my local HD and then copy to the network drive overwriting the original with no problem.
On your Synology box, if you open File Station, select the shared folder you're trying to save in, right-click, and choose Properties, and go to Advanced Privileges, do you by any chance have "Disable modification of existing files" checked?
Check to make sure that you have enough local disk space to cache the file being written to the network drive.

Also, make sure that the systems are not losing network connectivity and reconnecting, the OS is telling Office that the network location is not write-able/accessible.  IF it is not a permissions issue, it is an access/connectivity issue.
to akahan:

Unfortunately no I do not have "Disable modification of existing files" checked

I was so excited to go to my sinology drive and hopefully find out that that was the problem all along.  But no so sorry!

this has been the most difficult issue I have had yet.

Good Look though
To AllenFalcon:

It is not losing connectivity and I have plenty of space available.  Its a 256gb ssd and I am only taking up 45gb.  

Its something that I have to fix within office as it only occurs with office apps

cant save within office period to the network drive.

please keep those suggestions coming I really appreciate it.
Can you save to a different (non Synology) network drive?  Would be nice to narrow it down to this Synology unit if you can.  (Have you tried rebooting the synology?)
Yes I have tried rebooting the sinology drive.  I am in the  process now of creating a share on one of our file servers to test if it is infact the sinology drive.

I will get back to you asap
okay,

When using the new network share on our server, it saves fine.  And I moved some excel documents over to it and they saved fine aswell.

Also, I created a new share on the Synology NAS and Office saves fine on that aswell,

So narrowed it down to a problem with this particular share which has all our important data.

Whish I new exactly where to look.

I was thinking about backing up all the data to a temporary location using Robocopy without copying the security settings and then copying everything back.  

I don't think I should have to do this and I don't really want to as it might cause some other headaces.  Any other suggestions?  There must be a setting on the share in Synology Diskmanger that's causing the problem you think?
it could very well still be a problem with office I believe.
It sure sounds like an issue on the permissions on the particular Synology Share.  Does it have NFS enabled?

Might want to consider copying material off that share, deleting the share, and re-creating the share (with the same name, etc.), then putting everything back on it.... though it would be more satisfying to determine what exactly is causing the problem.
I do have NFS enabled.  Should I turn it off?  is this what you think I causing the problem>?

If I disable it It will have to reboot the network.
I do not use NFS on the Synology, and am able to use shared drives, etc.  I was asking about NFS because enabling it likely introduces a bunch of items to configure, which might have been configured incorrectly.... an additional layer of complication!  I can't provide a LOT of advice because, as mentioned, I don't use NFS... when i'm in front of a real computer and not typing with my thumbs, i'll take a look, but in the meantime, you could either check all your NFS settings, or trying disabling NFS and see if everything you want to use still works.

Are you accessing the Synology from Linux machines?  If not, I'm not sure why you'd need NFS enabled anyway.
I enabled it for future use.  

Did not think it would cause this problem.  But if it was causing a problem than the other test share on this Synology that i created would produce the same problem with Office dont you think?

Also i still strongly think that its an office issue since Like i said in my Thread, that it is only affecting 2 systems in my entire network.  Only 2 computers are experiencing this issue.
But you can save from Word on the problem machines to other shares on the Synology, right?
Yes I can save using any office related app on other shares on the sinology, just not this particular share, and only these 2 computers are experiencing the issue
Avatar of RQCRAIG
RQCRAIG

I believe I am experiencing the same type of problem, only I’m not using Synology. Users are on Windows 7 Enterprise x64 machines with Office 2010. They are pointed to shares on a Windows Server 2008 R2 box.

The users are each pointed to their own user share drive (among many other shares). Only two users are experiencing the problem so far, and only with Office files (Word, Excel, and PowerPoint), to their personal share drives. Other public drives are not an issue and neither are other file types to the personal drives with the Office file saving problem. For example, a .txt file plays nice all day long. The users have been given Full Control (even Ownership). However, they can only get Office files onto the share after saving locally and then copying the files back to the share.

For some reason, this is only affecting their user share, and no other share drives. Other users with same setup and permissions have no issues on their personal share drives.

On the problem shares, the users can create NEW Office files (or folders for that matter). However, as soon as they try to modify the files, they get the following error for Word and Power Point files: “Access denied. Contact your administrator.” When trying to modify and save an existing Excel file the error is slightly different:  “Document not saved.” For some strange reason, Access works just fine.

The work around for the Word, Excel, and PowerPoint files is to save the modified version of the files locally (i.e. to the desktop) and then copy the files back to the user share drive which works like a charm.

I tried having the user log into another machine and the problem persisted. This other machine is used by a user with the same type of setup (personal user share drive with exact same permissions) and that “known good” user has no issues.

I then tried having the “good” user with no problems log into the machine of one of the “problem” users. The “good” user had no issues using the “problem user’s” machine! The users are in all the same AD groups and have all the same permissions on their own respective shares. I even deleted and recreated the shares, but no joy.

Ideas?
No one has responded to me on this thread since my last post.

I have not been able to delete and recreate the share to see if the problem persists because i have to wait for the next maintenance window which hopefully is this weekend.

I'm glad to see that i am not the only one on this thread experiencing the same issue!.

Interesting that the good user has no problems on the machine with the issue.

I wish i new why
Problem solved!

It was the "windows ACL" tab on the Synology Diskstation Shared Folder Control Panel!

I had a checkmark in the allow edditing windows access control list Check Box.

I unchecked it and Lo And behold! problem solved.

If anyone else is experiencing this issue im sure that removing the permissions from the share and then re creating them will solve the issue as well.

give it a try.
I've requested that this question be closed as follows:

Accepted answer: 0 points for jblanc03's comment #a39122366

for the following reason:

it was the correct action to solve the problem
ASKER CERTIFIED SOLUTION
Avatar of akahan
akahan
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
TO Akahan:

I will have to wait to test this for the weekend coming up.  I will post the status of your theory once im done.

I guess for now we can keep this question opened until then.

Thanks!
I don't have Synology so I'm still out of luck. I have tried deleting and recreating the share multiple times, but am still experiencing the issue.