VMware Communities
derekpapworth
Contributor
Contributor

Shared folders - can't open file(s) as kept open by VMWare? (7.0.1 build-227600)

Wonder if someone can shed any light on an issue I've just started getting ..

In my VM's (XP guest) using Workstation 7.0.1 build-227600 running on Windows 7 host I'm running across a problem whereby certain programs won't open or save files on a shared folder (with host) as it says the file is open by another process (which they aren't) but if I exit Workstation and restart all is ok.

As a specific example I run Outlook in an XP VM that opens it's .PST file from the shared folder. This works fine and has done for a couple of years but now if I open Outlook in the VM, do some work and then exit Outlook, when I then open Outlook again I get a message saying it can't open the .PST file as it's in use by another program. If I suspend the VM and then resume it, and try opening Outlook I get the same error .. however .. if I suspend the VM, exit/quit Workstation itself, start Workstation again and resume the VM then Outlook will start fine!

It appears that the Workstation process itself is holding a handle on the file open in some way maybe? I've also had the same issue when say opening a file from a shared folder in Excel, making some changes and then saving it it won't let me as it says the file is in use by another process.

Has anyone experienced this issue at all or know of the reason/solution?

Thanks,

Derek

Reply
0 Kudos
7 Replies
derekpapworth
Contributor
Contributor

Just an update of the specifics as it appears that by just suspending then resuming the vm fixes the issue .. so in other words using the previous example ...

.. in the running VM I open Outlook which is referencing it's .PST file via shared folder on the host machine and all ok .. I then exit Outlook and then when I restart it again I get the "..in use.." error on the .PST file .. but .. if I suspend the vm then immediately resume the vm and then restart Outlook all is fine.

Hope someone can shed some light on this as it's a real pain and as I mentioned in my previous message this has been fine for a couple years so just wondering if it's a but in latest build?

Derek

Reply
0 Kudos
derekpapworth
Contributor
Contributor

Some more examples coming to light ..

Coming across more examples now as for instance running SQL Manager in the VM, load a SQL script file to edit from the shared folders mapped drive then when I try to save changes it says in use by another process yet if I load the same SQL file copied over to local (VM) disk it can save it fine.

This is seriously impacting my use of VMWorkstation now a lot of my data files for VM's are held on the shared folder mapped drives to the host for backup and common access purposes and yet now I'm not able to edit/save these files from programs.

Please can someone at VMWare respond on this one as it's really a problem, Thanks!

Derek

Reply
0 Kudos
continuum
Immortal
Immortal

can't you use regular file-sharing ?

VMware shared folders are known for issues like this - do not use them if possible




___________________________________

VMX-parameters- Workstation FAQ -[ MOA-liveCD|http://sanbarrow.com/moa241.html] - VM-Sickbay


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
josmer
Contributor
Contributor

I had the same Problem with renaming files on shared folder an VM tools greater 8.1.0, but no one had an idea.

Reply
0 Kudos
vmwaredownload
Enthusiast
Enthusiast

I've been seeing this across many version of VMWare when compiling a file on the host then running it in the VM (both Windows Server 2003). The host compiler can't overwrite the file on a new compile until VMWare is suspended and resumed as the original poster noticed.

Sometimes, I've also found that refreshing an explorer view of the shared folder in the guest releases the file handle and makes it accessible to the host again.

Reply
0 Kudos
louyo
Virtuoso
Virtuoso

Did you try turning OFF lazy write on the guest's hard drive. Maybe a caching anomaly?

Lou

Reply
0 Kudos
derekpapworth
Contributor
Contributor

Another factor, possibly red-herring maybe, is that recently changed from Windows 7 RC build to Windows 7 production build as host .. wonder if that might have something to do with it?

Derek

Reply
0 Kudos