Jump to content

Recommended Posts

Posted (edited)

We have recently migrated all Users' files to a new File Server (Windows 2008 R2). Since then we have had reports of error messages when saving.

 

The error message is "filepath\filename is currently in use. Try again later". This happens on both 'save' and 'save as' and obviously on existing documents in a User Directory.

 

Can anyone shed any light on why this may be occuring or have a fix?

Edited by ZeroHour
  • 3 weeks later...
Posted

It smells of a permissions problem on the new server tbh, I take it they dont get this error saving to local devices like memory sticks?

Can you stick a screenshot of your advanced permissions for the relevant persons dir?

Posted

A lot of times it's programs like backups/AV locking the files, might be worth running handle on it to check the files (Handle)

 

Also out of curiosity, try opening the file through a fully qualified shortcut rather than short one.

 

Steve

Posted

I take it people can create new documents and save fine but when they edit to save/save as it fails?

Also what AV do you have and are you on SP1 for 2010 yet or not?

Posted
Do the problem machines have offline files turned on, this can by symptomatic of a slightly corrupted offline files database which can be resolved by forcing a full sync on the users machine to clean up the offline files database.
Posted

Problem occurs when saving brand new Files aswell as editing files.

 

We are running Symantec Endpoint on Clients and Server and are not on SP1 yet.

 

Offine files on clients is turned off by Group Policy aswell as on the Server.

 

What is the most frustrating is that it is intermittent.

  • 2 months later...
Posted
Did you ever resolve this one. We have Server 2008 Standard and a mix of XP Pro and Windows 7 Pro 32 bit and 64 bit clients. Clients all have MS Office 2010 SP1 under MAK key. Recently some students have been finding Word will open their documents but won't save or save as. I am changing the permissions on the home folder to allow Creator Owner to read, write, list and read and execute to see if that makes any difference. Otherwise the management want me to roll back to 2003!
Posted

I was too scared to ask as nobody has mentioned it for ages.

 

I just spoke with one of the regular complainers who said it hasn't occured for ages and my gut feeling is SP1 for Office 2010 sorted things along with ensuring File and Share Permissions were correct as per Microsoft's guidlines for Home Directories. I wish I had a definate answer and it was the fact it was intermittant that was most baffling.

 

If I remeber rightly after we did a Robocopy to migrate the data we found there was a padlock symbal on some User Directory folders so we had to ensure ownership was correct and that they inherited the correct permissions.

  • Thanks 1
  • 2 weeks later...
Posted

Reviving this one yet again. I think I can see what the issue is now. Logging on as a student opening MS Office 2010 Word then going to Trust Centre and looking at Trusted Locations I can see that the student is not picking up his home drive as a trusted location. Trying to add it for him brings up a message The remote or network path you have entered is not allowed by your current security settings.

 

We are a Server 2008 Domain with a mix of XP Pro and Windows 7 Pro clients. This particular client is the latter. Oddly it’s not happening on all the clients nor is it the case with the effected user on another client, and it's only Word that it happens in?

Posted
Reviving this one yet again. I think I can see what the issue is now. Logging on as a student opening MS Office 2010 Word then going to Trust Centre and looking at Trusted Locations I can see that the student is not picking up his home drive as a trusted location. Trying to add it for him brings up a message The remote or network path you have entered is not allowed by your current security settings.

 

We are a Server 2008 Domain with a mix of XP Pro and Windows 7 Pro clients. This particular client is the latter. Oddly it’s not happening on all the clients nor is it the case with the effected user on another client, and it's only Word that it happens in?

 

Tried using machine policies to trust the whole server?

  • Thanks 1

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...