Hello,
Since yesterday after a reboot of my host (E6410 DELL, W7 SP1 64 bits, 8GB RAM, 2x750GB SATA3 running WorkStation 9.0.2, up to date Windows Update), I cannot open any of my existing VM.
I often get "Cannot find a valid peer process to connect to" and sometime before : "Transport (VMDB) error -32: Pipe: Read failed" or "Transport (VMDB) error -14: Pipe connection has been broken"
I've been working for 2 years on this machine without a hitch, upgrading from WS7 to WS9 without any issue.
FYI : we have changed the domain 3 months ago, but this has never be a problem.
I've googled and search on several forum. So far I've tried to :
- restart vmware-auth service as admin
- launch vmware.exe as admin
- stop/start vmx86 service
- uninstall / reboot / install Workstation. 3 times. First using control panel's uninstaller, then doing a /clean before install and finally hunting down any file/reg entry.
- asked IT if any change in group policy have been done recently (like not allowing to run vmware.exe ?!)
- rename vmware.exe (the logs I have look similars to what is in this post : http://communities.vmware.com/thread/331099?start=0&tstart=0 ... but no luck)
- excluded vmware.exe in my the AV (Microsoft ForeFront). Unfortunalely I'm not allowed to disabled it...
- open VM using the player ==> don't work either.
This is not a corrupted file in a VM (even backup -7zipped- are not working on my laptop ... but launch on another).
Even a newly created WM (without an OS), do not boot ! :-(
*BUT TO BE NOTICED* : if a VM is created as a shared VM, I can start it as remote localy ! And this same VM, if started (thru the.vmx) is not working using Workstation GUI !?
I've attached the 2 logs. The working one (vmware.log thru remote) and the non-working (vmware-vmx-4072.log thru WS GUI).
From what I seen (and the few I understand), it's like the CPU cannot be detected ?!
Both logs have this line :
FeatureCompat: EVC masks:
but the non-working goes-on with
Module CPUID initialization failed.
while the working display info on the CPU (hostCPUID name / family / type ...etc...)
Any idea is welcome.