[ms office - 2010] MS Access Cannot save to Network Location

[mukz]

Hi Guys,

 

Is anyone having an issue whereby noone except a domain admin can save to a Network Share?

Absolutely doing my nut in!

 

Both Office 2010, 2013 and 2016.

 

Any help whatsoever is much appreciated.

 

Thanks

 

Mukesh

[mukz]

Hi Guys,

 

Is anyone having an issue whereby noone except a domain admin can save to a Network Share?

Absolutely doing my nut in!

 

Both Office 2010, 2013 and 2016.

 

Any help whatsoever is much appreciated.

 

Thanks

 

Mukesh

[TechMonkey]

Is the share new? Are the Share permissions default?

[TechMonkey]

Is the share new? Are the Share permissions default?

[mukz]

Is the share new? Are the Share permissions default?

 

Not a new share.

It is the users home folder basically, we don't have roaming or mand profiles.

 

Everyone with full access to the users folder and then modify access for said student.

If i give myself the domain admin permissions i can then save to the folder but not with the domain admin permission.

[mukz]

Is the share new? Are the Share permissions default?

 

Not a new share.

It is the users home folder basically, we don't have roaming or mand profiles.

 

Everyone with full access to the users folder and then modify access for said student.

If i give myself the domain admin permissions i can then save to the folder but not with the domain admin permission.

[TechMonkey]

I would force user owner on all files and folders and then cascade the permissions. SOunds like something has right royally gone hinky™

[TechMonkey]

I would force user owner on all files and folders and then cascade the permissions. SOunds like something has right royally gone hinky™

[m25man]

Are you using Folder Redirection?

Is this affecting other Office Applications?

Try this,

Start Word or Excel as a user.

Create a test doc.

Using the Word/Excel file manager try creating a new sub folder within the default save path.

Does it hang or error?

 

See this...

https://social.technet.microsoft.com/Forums/windows/en-US/b72c763e-d029-4e65-a2dc-885a5aabf643/problem-creatingrenaming-a-folder-on-a-network-share-with-win10-anniversary-update-error?forum=win10itpronetworking

 

We have seen the above issue affecting Office users since at least January's 1607 update.

A fix was promised in Feb but it was pulled at the last minute.

We applied it to a test machine and it killed it dead.

We are waiting to see if it's addressed in this months updates.

 

I can recreate the error exactly using 1607 clients with Office 2016

Saving a file directly to the users home folder works fine, saving to a sub folder within the home folder will hang and creating a new sub folder causes this error.

Despite the error if you reopen the file manager the new folder appears and all security is correctly applied!

Then if the user retries saving to this location it all works!

 

Bizarre!

 

It seems like a permissions issue but clearly isn't because in our scenario after the error which can take 30 seconds or more "not responding" to appear the task of folder creation completes.

Subsequent saves to the folder are fine.

 

Note, clients are W10 1607 target server is a 2012R2 share.

I'm going to spin up a Win7 client to see how that behaves next.

 

I get a feeling this months patches could be a bumpy ride!

[mukz]

Are you using Folder Redirection?

Is this affecting other Office Applications?

 

Nope to folder redirection and also no to other applications.

It is just the blasted access that is doing this.

 

Saving to desktop and then copying to home drive works but cannot save directly to the network share. Even one with full access permissions where the user owns the folder!

[m25man]

Ran the March Updates for 1607 and the SMB saving issue appears have been resolved!

 

So it clearly appears to have been an issue between a previous update and 2012R2 servers.

 

If you haven't already done so test it out.

[mukz]

Ran the March Updates for 1607 and the SMB saving issue appears have been resolved!

 

So it clearly appears to have been an issue between a previous update and 2012R2 servers.

 

If you haven't already done so test it out.

 

Will do! Thanks.