we are having the same issue (Windows 2012 R2 / SEP Client 12.1.4)
All the affected server were running version 12.1.4xxx. Upgrading to 12.1.6xxx should solve this.
>>is there any document mentioned this issue?
thanks a lot
Hi to all.
In my company we have the same issue: random unresponsive server (2012/2012r2)
We have ESXI 6.0 up.2
We opened different support request (VmWare, Microsoft, etc) but no one tell us why this happened, and no solution.
Then crossing different tables from different console, i noticed that all unresponsive server had same sep version (12.1.2.x).
So i open a technical call to Symantec, and meantime i started to distribute last update of sep client (at time 12.1.6.x). This update require a system reboot, so only 30-40% of systems have been updated in the first step.
Symantec tell me we had old version of SEP, and requested us full Microsoft dump to analize (but this require reboot,too!) as well as update all client version.
No one server with last SEP version (21.1.6.x) got unresponsive.
At the end, Symantec confirm us problem was right in SEP version:
@- Fix ID: 3590578
@ Symptom: System freezes due to a deadlock in File System Auto-Protect driver after updating virus definitions.
@ Solution: Modified File System Auto-Protect driver to avoid this deadlock.
So, UPGRADING SEP TO LAST VERSION, PROBLEM SOLVED.
I hope to have helped.
We have this issue too, VMware support said there is a bug and it should be fixed in the June release. They don't have any official doc on this bug or ready to tell the public. They collected 2 dump files and analyzed it and came with this conclusion.
To temporary fix the Snapshot Quesing the OS you can do this.
1. Stop the VMware Tools service 2. Stop the VMware Snapshot Provider service if it’s running 3. Stop the Volume Shadow Copy service if it’s running 4. Restart the Cryptographic Service 5. Start the VMware Tools service (automatically starts Snapshot Provider and VSS) 6. Attempt to create a quiesced snapshot
Has anyone resolved this?
Thank you so much for this. I just had the same issue. This is the 4th time. After reading your post I can confirmed that we are having the same issue. I will try the update. If issues comes up, I'll post back.
I was look about answer But i try to make update to ESXI 6.5u1 fix to me thisis errors if you want to fix this error try go to update