fslogix Locked VHDX after Server Reboot unexpected

Question

Hi

I have read many Docs FAQS and also here on Forum but it seems never resolved this issue here so i try to aks here on the Forum.

We have setup the last FSLogix 2.9.7654.46150 without concurrect Sessions and prevent Login if Profile can't be attached. For testing we have logged in as User Profile & ODFC seems works correct, we have Cloud Cache and Cache Modus attached on the Profile if sucessfully mapped, all works.

But if we simulate a crash (Force Reboot and User are logged in) the VHDX seems remaining in LOCK state and the User can't login to another Machine because they dosen't have access to the VHDX. On the Profile Server where the VHDX are i can't see any process open that still try to access this Files and also if i delete the LOCK Files the user can't still Login to the other Machines.

I have try the Registery Key CleanupInvalidSessions but dosen't helps, i have try to set Timeouts and Waiting Time CloudCache but nothing seems to help.

I don't understand where FSLogix seems to check if the File are Loked because they dosen't! Where are this false informations or cached informations that prevent the Successfull Login on another machine?

--> If the rebooted machine are again available the user can connect to this and works normally, but only on the last machine that they are unexepted crashed. The Machines are non presistent so all the Registery are clear after a restart.

Hope anyone can clarifying me how to check deeper where the Access Denied because open in another Process Problem are coming from.

Procmon on Fileserver also dosen't show me any connection active on this VHDX.

Thanks a lot

Answer

Hello @Antonio Lucifora | itcnet AG

" When you are using cloud cache, the system is trying to perform locking across all the storage locations. What it's doing is creating a file in the location where the VHD gets stored that indicates the VHD is locked by another system. This file is named the same as your VHD file with a .lock extension. There should be some more information in your cloud cache logs related to this.

The lock file contains some information about which machine is holding the lock, and when they last updated that they were doing so. It's not really a human readable format file, but I think you could type it and see what computer names it has in it. It seems likely that during testing maybe users are not logging out successfully so these lock files don't get cleaned up.

If you know the file is not in use, you can safely delete the lock file."

Quote from this thread .

Best Regards
Karlie

----------

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer

Hi KarlieWeng

Thanks for the quick response. I have seen this Lock Files and if i look inside i see also teh FQDN, if i delete the file it dosen't seems to work, the user can't logon to another Worker, i have also try to change the FQDN Name but dosen't work.
Are you sure that this file are causing the System to see the VHDX are locked?

Thank you again

Answer

i have try various tests:

Login with user with Profile & ODFC Sucessfully attached
Force Restart the machine to simulate a crash
The Session are crashed, i can see the open files & session and close all manually, i have deleted the Lock files (2 x SMB Share Cloud Cache Destination)
if i try to connect with the user on another machines i receive again the message that the container are used by another process, if i look at the processmonitor i dosen't see any process that are still attached on this VHDX
if i reboot the affected machine i can connect sucessfully with the user on it, even if the LOCK files are deleted, only on this machine i can Login and all works normally

Answer

Hi,

Can you control whether you have access to these folders?
C:\Users\local_username\AppData\Local\Microsoft\Credentials
C:\Users\local_username\AppData\Roaming\Microsoft\Credentials

If not, a restart will help at the moment.

I've described the problem here.
fslogix-unclean-logoff-causing-locked-files-until.html

Regards
Michael

Answer

hi MuchR-5838

i have access on this folders and have also write and delete permission on it.

i have made varoius test and found:

After a unexcepted shutdown of the machine the user have still a session on the Filserver, after minutes it will change from username to disconnected, if i close all that disconnect sessions and open files and also delete the Lock files i can connect to another machines without problem.
But ! if the machine have a unexcepted shutdown and the user notify that (Citrix Workspace disconnect the session) the user try to reconnect to the Desktop, than it starts the session again on the other machine, now it appaers the Error Message that VHDX can't be attached (that's OK because i have configured to not load the Profile if in error state), if the user close the connection and i close all the sessions and open files an delete the Lock Files the connection on the other Machines dosen't work anymore. I must start the affected machine and the user can connect on it without problems.

i have retry the RegKey CleanupInvalidSessions because on the Documentation it's write that this settings helps to prevent this situation, but if set this key and the user Login normally and logout normally they stucks n logout, if i revert the Key to 0 than it works normal.

Hope anyone have more ideas ?

Thanks

Antonio

fslogix Locked VHDX after Server Reboot unexpected

7 answers