https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# microsoft-fslogix
s
This message was deleted.
m
f
It could be 🙂 I did notice your post. I'll wait a little while to see if anybody has an answer. If no answer I will create a ticket with Microsoft.
m
I've read your post, seems like the same issue
If I wait for 5-10 minutes, it works most of the time. Until then the "CloudCacheProvider" Log states 100+ lines off: [155454.136][tid00000ca0.000059d0][ERROR00000000] Failed to acquire a shared reader lock '\\xa-wms2019-01.domain.local\profiles_ctx$\anyusername_S-1-5-21-2505351160-4269483969-3991436212-4185\Profile_anyusername.VHDX.lock': SMBStorage.cpp(809): [WCODE: 0x00000005] Unable to open/create the lock file: \\xa-wms2019-01.domain.local\profiles_ctx$\anyusername_S-1-5-21-2505351160-4269483969-3991436212-4185\Profile_anyusername.VHDX.lock [155454.248][tid00000ca0.000059d0][ERROR00000000] Failed to read lock file: SMBStorage.cpp(809): [WCODE: 0x00000005] Unable to open/create the lock file: \\xa-wms2019-01.domain.local\profiles_ctx$\anyusername_S-1-5-21-2505351160-4269483969-3991436212-4185\Profile_anyusername.VHDX.lock [155454.350][tid00000ca0.000059d0][ERROR00000000] Failed to read lock file: SMBStorage.cpp(809): [WCODE: 0x00000005] Unable to open/create the lock file: \\xa-wms2019-01.domain.local\profiles_ctx$\anyusername_S-1-5-21-2505351160-4269483969-3991436212-4185\Profile_anyusername.VHDX.lock [155454.454][tid00000ca0.000059d0][ERROR00000000] Failed to read lock file: SMBStorage.cpp(809): [WCODE: 0x00000005] Unable to open/create the lock file: \\xa-wms2019-01.domain.local\profiles_ctx$\anyusername_S-1-5-21-2505351160-4269483969-3991436212-4185\Profile_anyusername.VHDX.lock [155454.555][tid00000ca0.000059d0][ERROR00000000] Failed to read lock file: SMBStorage.cpp(809): [WCODE: 0x00000005] Unable to open/create the lock file: \\xa-wms2019-01.domain.local\profiles_ctx$\anyusername_S-1-5-21-2505351160-4269483969-3991436212-4185\Profile_anyusername.VHDX.lock [155454.655][tid00000ca0.000059d0][ERROR00000000] Failed to read lock file: SMBStorage.cpp(809): [WCODE: 0x00000005] Unable to open/create the lock file: \\xa-wms2019-01.domain.local\profiles_ctx$\anyusername_S-1-5-21-2505351160-4269483969-3991436212-4185\Profile_anyusername.VHDX.lock [155454.756][tid00000ca0.000059d0][ERROR00000000] Lock file read retry count exceeded
I created a ticket.
a
Hi, I've started the original post on MS forums, just to add that so far I was not able to make this work or to find the cause. Tested it with different FSLogix versions including the latest one with the same results (2nd session delay in my case is always arround 160sec) no matter what OS W2K8R2/W2K16/W2K19).
m
Do you also see the following in your logs over and over again?
[155454.136][tid00000ca0.000059d0][ERROR00000000] Failed to acquire a shared reader lock '\\xa-wms2019-01.domain.local\profiles_ctx$\anyusername_S-1-5-21-2505351160-4269483969-3991436212-4185\Profile_anyusername.VHDX.lock': SMBStorage.cpp(809): [WCODE: 0x00000005] Unable to open/create the lock file: \\xa-wms2019-01.domain.local\profiles_ctx$\anyusername_S-1-5-21-2505351160-4269483969-3991436212-4185\Profile_anyusername.VHDX.lock [155454.248][tid00000ca0.000059d0][ERROR00000000] Failed to read lock file: SMBStorage.cpp(809): [WCODE: 0x00000005] Unable to open/create the lock file: \\xa-wms2019-01.domain.local\profiles_ctx$\anyusername_S-1-5-21-2505351160-4269483969-3991436212-4185\Profile_anyusername.VHDX.lock [155454.350][tid00000ca0.000059d0][ERROR00000000] Failed to read lock file: SMBStorage.cpp(809): [WCODE: 0x00000005] Unable to open/create the lock file: \\xa-wms2019-01.domain.local\profiles_ctx$\anyusername_S-1-5-21-2505351160-4269483969-3991436212-4185\Profile_anyusername.VHDX.lock [155454.454][tid00000ca0.000059d0][ERROR00000000] Failed to read lock file: SMBStorage.cpp(809): [WCODE: 0x00000005] Unable to open/create the lock file: \\xa-wms2019-01.domain.local\profiles_ctx$\anyusername_S-1-5-21-2505351160-4269483969-3991436212-4185\Profile_anyusername.VHDX.lock [155454.555][tid00000ca0.000059d0][ERROR00000000] Failed to read lock file: SMBStorage.cpp(809): [WCODE: 0x00000005] Unable to open/create the lock file: \\xa-wms2019-01.domain.local\profiles_ctx$\anyusername_S-1-5-21-2505351160-4269483969-3991436212-4185\Profile_anyusername.VHDX.lock [155454.655][tid00000ca0.000059d0][ERROR00000000] Failed to read lock file: SMBStorage.cpp(809): [WCODE: 0x00000005] Unable to open/create the lock file: \\xa-wms2019-01.domain.local\profiles_ctx$\anyusername_S-1-5-21-2505351160-4269483969-3991436212-4185\Profile_anyusername.VHDX.lock [155454.756][tid00000ca0.000059d0][ERROR00000000] Lock file read retry count exceeded
f
I would love to hear the result of your ticket - if you ever get a response 🙂
a
I don't have any log files with me at the moment, but as far as I recall i did have that error logged "[ERROR:00000000] Failed to read lock file: smbstorage.cpp(809) [WCODE: 0x00000020] Unable to open/create the lock file \\path\RW.vhd.lock. In my case it was not in repeated way like yours, but when you look at it its logged somewhere in the middle of the overall delay of 160secs before the disk gets attached
[163221.212][tid:000008f8.00001234][INFO]          ===== End Session:    SMB Cloud Cache Provider [163307.477][tid000008f8.00001234][ERROR00000000]    Failed to read lock file: smbstorage.cpp(809): [WCODE: 0x00000020] Unable to open/create the lock file: \ \filer01\FSLogixProfiles\S-1-5-21-4075742445-2671179031-2475658168-1135_test-s01\RW.vhd.lock [163457.290][tid:000008f8.00000da0][INFO]              Successfully attached \ \filer01\FSLogixProfiles\S-1-5-21-4075742445-2671179031-2475658168-1135_test-s01\Profile_test-s01.vhd
f
We also se A LOT of "Unable to open/create the lock file", for 3-5 minutes. Midway through the waiting, error changes to say "failed to aquire exclusive lock". Strange actually. The second logon should not try to create the lock file, nor try to lock it exclusively, as it is already locked from the first logon and should not be locked again. My understanding is that it should use the RO file locally instead.
I will create a ticket today, hopefully this will help bump up the issue with Microsoft.
Just created a ticket, referencing that you guys have issues also. We have a gold partner support contract, I hope Microsoft will prioritize it.
a
I agree with you, on the other hand, when you use VHD Location (no CC) with type 3 profile for example it works as expected.
f
You are right Asmir. But we actually plan on using it in a physical environment, both desktops and laptops. Cloud Cache is a critical component of this setup to handle offline usage etc.
m
We also opened our Ticket via Gold Partner support. I used the FSLOgix support collector tool, and handed in the zip file. Support is currently investigating the zip file.
a
Great 👍, i'd be interested to hear what the support says about this issue.
f
Created my ticket 24 hours ago as Critical. Haven't heard a single word yet 🤣
m
I received my first response yesterday. Told me to check the offical Anti Virus exclusions. I had those already in place, and double checked them. Shouldn't be Anti Virus for me. Together with my case I also provied the FSLogix Log ZIP Bundle, created by the support tool.
f
I still haven't heard anything from MS Support, besides the generic "your ticket has been created" message.
a
I did my tests without AV installed and the result was the same. I don't think it is related to AV either.
m
I received another message, stating that I should now (despite having all recommended exclusions in place) test without Anti Virus. This is not helpful.
a
My installation was W2K16 based (vanilla) with latest MS patches at the time, with only Citrix VDA and FSLogix installed. Nothing else involved to be as clean as possible .. 😞
f
Hi Guys. Did you completely disable the built-in Windows Defender? Otherwise I think it will still scan. I have a scheduled meeting with Microsoft Support today. They also told me to do the A/V exclusions. I'm currently deploying a small test-environment, hopefully I can reproduce it with Defender removed/disabled.
m
Defendet is disabled via GPO
I now raised a ticket with the Anti Virus support, also I don't have much hope. Issue happend again today. User logged off and on and couldn't reconnect. Error was once more: [155454.136][tid00000ca0.000059d0][ERROR00000000] Failed to acquire a shared reader lock '\\xa-wms2019-01.domain.local\profiles_ctx$\anyusername_S-1-5-21-2505351160-4269483969-3991436212-4185\Profile_anyusername.VHDX.lock': SMBStorage.cpp(809): [WCODE: 0x00000005] Unable to open/create the lock file: \\xa-wms2019-01.domain.local\profiles_ctx$\anyusername_S-1-5-21-2505351160-4269483969-3991436212-4185\Profile_anyusername.VHDX.lock
f
I reproduced the issue Yesterday on 2 “vanilla” Win10 VMs with defender disabled with gpo. Microsoft supporter said MS is working on a fix, expected release i March. I hope that holds true 👍
m
You are also using Cloud Cache, am I right?
a
Hi, yes I did try that by completely removing defender module (after seeing some trade on Fslogix forum stating there was an issue with the Defender) but it didn't give any improvements. So let's hope to that fix. Thanx for info. 👍
f
@Marco Hofmann - yes, I am also using Cloud Cache 😉
m
I received answer from our Anti Virus support (ESET). They don't believe that they are the problem, but gave me an FSLogix AV exclusions list, which has more entries than the Microsoft one. The entries I should add are as following:
Copy code
C:\ProgramData\FSLogix\*
*.vhdx
C:\Program Files\FSLogix\*
C:\Windows\TEMP\*.VHDX
\\fileserver01\profiles_ctx$\*
\\fileserver02\profiles_ctx$\*
f
Yep, I got that directory from MS Support as well.
Let's see how it turns out when the patch arrives 🙂
m
Sry the list wasn't ready, hit enter to early. I did get a list from MS, but especially the hint exclude the Cloud Cache SMB UNC paths was new to me, and the C:\ProgramData was also not mentioned by MS.
f
Ahh Yes - thanks Marco, I will make a note of that. (Y)
m
March is still 4 weeks away, that's not funny.. Seems like Cloud Cache still has it's problems.
We are now much further with our testings. We have deployed MCS clones without ESET AntiVirus, and still Cloud Cache logins will fail after a few days. Has anybody new informations? It's still the same error as before. WS2016 with latest FSLogix 2.9.7237.48865
3 Views
Open in Slack
PreviousNext
Powered by