Hi all,
I tried various workarounds I found from in the forum, but they did not work for me. I found a fix outside the forum, and thought it best to post it here. The fix (thanks to Michael Shillingford) was making authorization service depend on wpi service. Found this here:
http://www.mail-archive.com/zenoss-users@zenoss.org/msg01563.html//www.mail-archive.com/zenoss-users@zenoss.org/msg01563.html
Details of registry mod for this:
\----
Windows Registry Editor Version 5.00
\[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VMAuthdService]
"DependOnService"=hex(7):76,00,6d,00,78,00,38,00,36,00,00,00,77,00,6d,00,69,00,00,00,00,00
\----
\- no errors in logs any more!!
\- decreased the time from login to system up and working from 1-2 minutes to 5-10 seconds. \!!!
Fixed:
1) long login times and lumpy system response initially.
2) following errors in my system logs:
"The VMware Authorization Service service hung on starting" as well as
"WMI ADAP was unable to process the PerfDisk performance library due to a time violation in the open function" and
"Unable to collect the FTP performance statistics"
Am running Vmware Server 1.0.1 build 29996 on Win2K Pro SP4.
Seems like other services (like for reporting events???) need to be running before VMware (which requires/invokes IIS) kicks in.
Following workarounds had not fixed my problem for me although they may fix other things like guest processes:
making vmserverd service depend on RPCCS & VMAuthdService
http://www.vmware.com/community/thread.jspa?messageID=412635#412635
increasing the pipe timeout to 5 minutes. Found somewhere in this forum.
Hope this is of use,
Adrien.