Event ID: 1090 - couldn't log the RSoP session status causes loss of mapped drive and VM failure
Posted on 2009-04-14
I have noticed that my 2 guest VM's (XP Pro) running on my XP Pro Host randomly turned off. Users would report that it was suddenly unavailable. They would restart just fine and then disappear a few days later with no apparent pattern.
Upon checking the Event Log I see that the failure has the following pattern: first, event ID: 1090 occurs - Windows couldn't log the RSoP session status. Source - userenv User: NT AUTHORITY\SYSTEM. This is followed after a few seconds by - Event ID: 100 (User: N/A) (Source: vmauthd) - Cannot connect to VMX R:\VMDataStore1\RDP-Court\RDP-Court.vmx
That is the path to the data store and the corresponding vmx file. The data store is mapped to the R:\ drive letter. This error is followed by matching errors for all the other VMs and after that I get several more RSoP failures.
So how do I get the PSoP failures to stop? What more info is needed to troubleshoot this? I assume the RSoP failure is causing the mapped drive problem.