Hi,I have seen recently been seeing errors on the Endpoint Console with an error code a049001e saying 'Deadlock detected while asynchronously scanning file " " for user " "'. The error in question has occurred for about 60 computers.I can't see anything online with regards to this error with a fix or how to troubleshoot this and was wondering if this is a new error that has occurred, after the result of an update. Or has this been an error that has occurred in the past please. Any help or advice on this would be appreciated please?
Also have the DisableAsyncScans registry fix (https://support.citrix.com/article/CTX241246), which just changed the errors and continued to have some issues.
Hopefully endpoint client will be updated soon to address.
Hey Shweta, I'm having the same issue on several PC.
Hi Michael Sanders
I have sent you the steps via PM, could you please try and check if that helps?
The same problem. Why just PM?
We are seeing the same problem as well, deadlocked files in the user profile which is killing Citrix UPM. I have PM'd our case number for assistance. So far, the support engineers we are dealing seem unaware of this.
We are having the same issue with error code a049001e I have logged a call - 03052187 any chance you could help us out as well.
Since Sophos is not fixing the issue we came across a fix for the last time this happened to Citrix when Sophos deployed an update that caused this issue.
Hi Evan Prohaska
Our team is currently investigating this issue, we will update the information once available. I would suggest you implement the workaround as mentioned in this thread and see if it fixes the issue.
Following this thread as we started to notice this in our environment on Thursday 20/08 from around 6am too, most noticeable in our Citrix environment, it’s slowing logins at the interactive session hand off. Logins have gone from 60 seconds to anything up to 10 minutes. WS2016 (1607) Citrix Virtual Desktop and Apps 7.15LTSR CU3.
I’ll try the suggested fix but please can you inform me when there is an official fix..
Hi Mel Lawrence
We're aware of this and this is actively being investigated by our development team. We will definitely update this thread once there is a fix available.