Jump to content
Welcome to our new Citrix community!
  • 0

FSLOGIX VHDX share session opened and file locked, this leads to temp profile creation or citrix VDI is not launching


Mohamed Aslan

Question

FSLOGIX VHDX share session opened and file locked, this leads to temp profile creation or citrix VDI is not launching.

 

We have DELL ISILON share drive used for FSLogix profile management. Whenever few user's log off and login back, local profile gets created or unable to launch the Citrix VDI, when I checked the VDI and found below logs from programdata FSLogix log folder : [ERROR:00000020]   Open vhd(x) failed, file is locked.  Retrying 12 time(s) at 5 second intervals (The process cannot access the file because it is being used by another process.).

 

Tried to disconnect the opened file from the ISILON but nothing helped.

 

only solution here we have is to rename the old profile and login back into VDI which will create new FSLogix profile. this is not correct solution I know.

 

Now this issue making our production users big issue and down time.

 

I need Citrix team advise to fix this issue ASAP.

Link to comment

6 answers to this question

Recommended Posts

  • 0

Thanks James for the message.

 

I am not able to find where the VHD file is locked, we have Symantec installed on all machines, whether that's holding some file even after log off I am doubting.

 

On logs, only it's mentioned file is locked and below is the logs:

 

[13:48:39.659][tid:00001510.0000172c][ERROR:00000020]   Open vhd(x) failed, file is locked.  Retrying 12 time(s) at 5 second intervals (The process cannot access the file because it is being used by another process.)
[13:48:44.674][tid:00001510.0000172c][INFO]             Retrying open vhd(x) 1/12
[13:48:50.002][tid:00001510.0000172c][INFO]             Retrying open vhd(x) 2/12
[13:48:55.362][tid:00001510.0000172c][INFO]             Retrying open vhd(x) 3/12
[13:49:00.393][tid:00001510.0000172c][INFO]             Retrying open vhd(x) 4/12
[13:49:05.424][tid:00001510.0000172c][INFO]             Retrying open vhd(x) 5/12
[13:49:10.455][tid:00001510.0000172c][INFO]             Retrying open vhd(x) 6/12
[13:49:15.487][tid:00001510.0000172c][INFO]             Retrying open vhd(x) 7/12
[13:49:20.518][tid:00001510.0000172c][INFO]             Retrying open vhd(x) 8/12
[13:49:25.551][tid:00001510.0000172c][INFO]             Retrying open vhd(x) 9/12
[13:49:30.825][tid:00001510.0000172c][INFO]             Retrying open vhd(x) 10/12
[13:49:35.864][tid:00001510.0000172c][INFO]             Retrying open vhd(x) 11/12
[13:49:40.903][tid:00001510.0000172c][INFO]             Retrying open vhd(x) 12/12
[13:49:40.919][tid:00001510.0000172c][INFO]             Status set to 11: Cannot open virtual disk
[13:49:40.919][tid:00001510.0000172c][INFO]             Error set to 32
[13:49:40.919][tid:00001510.0000172c][ERROR:00000020]   Failed to open virtual disk:  sharedrive\VDI\Profiles\user profile folder\username.vhd (The process cannot access the file because it is being used by another process.)
[13:49:40.919][tid:00001510.0000172c][INFO]             Configuration setting not found: SOFTWARE\FSLogix\Profiles\PreventLoginWithFailure.  Using default: 0
[13:49:40.935][tid:00001510.0000172c][ERROR:0000001f]   LoadProfile failed.  User: username. SID: S-1-5-21-0000. (A device attached to the system is not functioning.)
[13:49:40.935][tid:00001510.0000172c][INFO]             loadProfile time: 61547 milliseconds

Link to comment
  • 0

Are you using tools to shrink the VHD files?  I used to run a PS script via a scheduled task which would sequentially mount all the VHDs, shrink them, and then unmount them again.  This process would run overnight on a weekly basis and would always recover 100-200GB of disk space.   Occasionally, a VHD would fail to dismount after being shrunk though, and would remain mounted and so locked.   The fix was to go to the server and launch Disk Management, and you'd see any stuck VHDs listed as still being mounted.

 

I did resolve this more permanently by running a separate PS script a few hours later to check for and dismount any disks, which largely solved the problem.   The same script would also email me the results of the shrinker script, remaining free space, etc.  Worked quite nicely in the end, but the very latest versions of FSLogix now shrink the files on logout so it's not really a problem any more.   But if you have any sort of shrinker scripts running, then it's worth checking if there are files being held open by it.

Link to comment

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...