Marcus4Aspern
Contributor
Contributor

[Q] Cannot start any VM - internal error [SOLVED]

Jump to solution

Hallo,

I installed Workstation 8 and cannot start any VM - neither ones created earlier nor new ones. Powering the machine on gives me an "internal error".

My Specs: Win 7 64bit (SP1), Core i7  2600K with 8GB Ram

The vmware log:

011-10-03T19:22:38.013+02:00| vmx| I120: Log for VMware Workstation pid=3424 version=8.0.0 build=build-471780 option=Release
2011-10-03T19:22:38.013+02:00| vmx| I120: The process is 64-bit.
2011-10-03T19:22:38.013+02:00| vmx| I120: Host codepage=windows-1252 encoding=windows-1252
2011-10-03T19:22:38.013+02:00| vmx| I120: Host is Windows 7 Home Premium, 64-bit Service Pack 1 (Build 7601)
2011-10-03T19:22:37.713+02:00| vmx| I120: VTHREAD initialize main thread 0 "vmx" host id 6336
2011-10-03T19:22:37.738+02:00| vmx| I120: LOCALE windows-1252 -> NULL User=c07 System=c07
2011-10-03T19:22:37.738+02:00| vmx| I120: Msg_SetLocaleEx: HostLocale=windows-1252 UserLocale=NULL
2011-10-03T19:22:37.743+02:00| vmx| I120: FILE: FileLockDynaLink: Further process validation tools are: available
2011-10-03T19:22:38.014+02:00| vmx| I120: Hostname=KOENIG
2011-10-03T19:22:38.017+02:00| vmx| I120: IP=fe80::41d:e6a3:5dd2:fa9f%11
2011-10-03T19:22:38.017+02:00| vmx| I120: IP=fe80::1cf:3682:36e8:4ccb%17
2011-10-03T19:22:38.017+02:00| vmx| I120: IP=fe80::1d80:2f6e:979c:b57d%18
2011-10-03T19:22:38.017+02:00| vmx| I120: IP=192.168.1.4
2011-10-03T19:22:38.017+02:00| vmx| I120: IP=192.168.30.1
2011-10-03T19:22:38.017+02:00| vmx| I120: IP=192.168.158.1
2011-10-03T19:22:38.017+02:00| vmx| I120: HOSTINFO 1074415970 @ 3331240Hz -> 0 @ 1000000000Hz
2011-10-03T19:22:38.017+02:00| vmx| I120: HOSTINFO ((x * 2518163806) >> 23) + -322527338056
2011-10-03T19:22:38.037+02:00| vmx| I120: System uptime 321912074 us
2011-10-03T19:22:38.037+02:00| vmx| I120: Command line: "C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe" "-s" "vmx.stdio.keep=TRUE" "-#" "product=1;name=VMware Workstation;version=8.0.0;buildnumber=471780;licensename=VMware Workstation;licenseversion=8.0+;" "-@" "pipe=\\.\pipe\vmxf3ce37cf9b6f9c3e;" "D:\VM\Windows 7 x64\Windows 7 x64.vmx"
2011-10-03T19:22:38.037+02:00| vmx| I120: Msg_SetLocaleEx: HostLocale=windows-1252 UserLocale=NULL
2011-10-03T19:22:38.056+02:00| vmx| I120: UI Connecting to pipe '\\.\pipe\vmxf3ce37cf9b6f9c3e' with user '(null)'
2011-10-03T19:22:38.057+02:00| vmx| I120: VMXVmdb: Local connection timeout: 60000 ms.
2011-10-03T19:22:38.104+02:00| vmx| I120: VmdbAddConnection: cnxPath=/db/connection/#1/, cnxIx=1
2011-10-03T19:22:38.105+02:00| vmx| I120: Vix: [6336 mainDispatch.c:483]: VMAutomation: Initializing VMAutomation.
2011-10-03T19:22:38.105+02:00| vmx| I120: Vix: [6336 mainDispatch.c:780]: VMAutomationOpenListenerSocket() listening
2011-10-03T19:22:38.122+02:00| vmx| I120: Vix: [6336 mainDispatch.c:4067]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0
2011-10-03T19:22:38.122+02:00| vmx| I120: Transitioned vmx/execState/val to poweredOff
2011-10-03T19:22:38.122+02:00| vmx| I120: Vix: [6336 mainDispatch.c:4067]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0
2011-10-03T19:22:38.122+02:00| vmx| I120: Vix: [6336 mainDispatch.c:4067]: VMAutomation_ReportPowerOpFinished: statevar=2, newAppState=1877, success=1 additionalError=0
2011-10-03T19:22:38.122+02:00| vmx| I120: Vix: [6336 mainDispatch.c:4067]: VMAutomation_ReportPowerOpFinished: statevar=3, newAppState=1881, success=1 additionalError=0
2011-10-03T19:22:38.122+02:00| vmx| I120: VMMon_GetkHzEstimate: Calculated 3411189 kHz
2011-10-03T19:22:38.123+02:00| vmx| I120: VMMon_RememberkHzEstimate: Calculated 3411189 kHz
2011-10-03T19:22:38.123+02:00| vmx| I120: TSC kHz estimates: vmmon 3411189, remembered 3411189, osReported 3401000. Using 3411189 kHz.
2011-10-03T19:22:38.123+02:00| vmx| I120: CPU # 0 TSC = 1100186590922
2011-10-03T19:22:38.123+02:00| vmx| I120: CPU # 1 TSC = 1100186590888
2011-10-03T19:22:38.123+02:00| vmx| I120: CPU # 2 TSC = 1100186590603
2011-10-03T19:22:38.123+02:00| vmx| I120: CPU # 3 TSC = 1100186590637
2011-10-03T19:22:38.123+02:00| vmx| I120: CPU # 4 TSC = 1100186590948
2011-10-03T19:22:38.123+02:00| vmx| I120: CPU # 5 TSC = 1100186590906
2011-10-03T19:22:38.123+02:00| vmx| I120: CPU # 6 TSC = 1100186590898
2011-10-03T19:22:38.123+02:00| vmx| I120: CPU # 7 TSC = 1100186590836
2011-10-03T19:22:38.123+02:00| vmx| I120: TSC first measured delta 345
2011-10-03T19:22:38.123+02:00| vmx| I120: TSC min delta 387
2011-10-03T19:22:38.123+02:00| vmx| I120: PTSC: RefClockToPTSC 0 @ 3331240Hz -> 0 @ 3411189000Hz
2011-10-03T19:22:38.123+02:00| vmx| I120: PTSC: RefClockToPTSC ((x * 4294966339) >> 22) + -1100565306901
2011-10-03T19:22:38.124+02:00| vmx| I120: PTSC: tscOffset -1100187618517
2011-10-03T19:22:38.124+02:00| vmx| I120: PTSC: using TSC
2011-10-03T19:22:38.124+02:00| vmx| I120: PTSC: hardware TSCs are synchronized.
2011-10-03T19:22:38.124+02:00| vmx| I120: PTSC: current PTSC=289960
2011-10-03T19:22:38.124+02:00| vmx| I120: Module CPUID initialization failed.
2011-10-03T19:22:38.124+02:00| vmx| I120: Vix: [6336 mainDispatch.c:869]: VMAutomation_LateShutdown()
2011-10-03T19:22:38.124+02:00| vmx| I120: Vix: [6336 mainDispatch.c:819]: VMAutomationCloseListenerSocket. Closing listener socket.
2011-10-03T19:22:38.125+02:00| vmx| I120: Flushing VMX VMDB connections
2011-10-03T19:22:38.125+02:00| vmx| I120: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#1/'
2011-10-03T19:22:38.125+02:00| vmx| I120: VmdbCnxDisconnect: Disconnect: closed pipe for pub cnx '/db/connection/#1/' (0)
2011-10-03T19:22:38.129+02:00| vmx| W110: Failed to initialize VM.

I marked out the error.. I tried to reinstall, clean.... nothing helped.

Oddly I can use the player app to run all VM´s without problem....

Any solutions?

Thanks in advance

Marcus4Aspern

1 Solution

Accepted Solutions
admin
Immortal
Immortal

Does renaming "vmware.exe" to something else help?

View solution in original post

0 Kudos
27 Replies
Marcus4Aspern
Contributor
Contributor

can really nobody help me, please?

TIA
Marcus4Aspern

0 Kudos
continuum
Immortal
Immortal

can you start any VM in vmplayer ?

do you run any agressive antivirus or related tools
do you have games installed that use nProtect gameguard ?
do you have a running process named fix-camera.exe ?


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
Marcus4Aspern
Contributor
Contributor

Dear continuum,

Thanks for your answer.

I am using microsoft antivirus and adaware (I temporarially disabled the protection, but that didn´t change anything).

I don´t have the fix-camera process you mentioned.

For the nprotect games.. don´t know, where can I check this? But I don´t think so, the workstation worked till June (Version 7), then I didn´t use it during summer time and at a sudden I had this error, updated to Version 8, but the error didn´t go away. In the meantime I didn´t install any games. Maybe a windows update (I am on Windows 7 64bit SP1)

I CAN play the VM´s in the player, the problem is only rising using workstation...

Thanks

Marcus4Aspern

0 Kudos
continuum
Immortal
Immortal

Ok - then you hit a known bug - at the moment I am not aware of any solution.

For now you have to live with it - and occasionally check back here.
The problem has been reported by several users


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
Marcus4Aspern
Contributor
Contributor

OK... Thanks for your help anyway!

Marcus4Aspern

0 Kudos
admin
Immortal
Immortal

Does renaming "vmware.exe" to something else help?

0 Kudos
Marcus4Aspern
Contributor
Contributor

I must admit, I was first sceptical, that renaming of the .exe would change anything....

BUT

That did the trick!!

I cannot immage WHY this changed the behaviour of the program, but now workstation does it´s job...

Thanks for help!

Marcus4Aspern

0 Kudos
admin
Immortal
Immortal

You most likely have something else running on your system that actively attempts to hook itself into vmware.exe and manages to break it (perhaps intentionally).  That also explains why you can power on VMs through Player.

As continuum mentioned, GameGuard has been known to do shenanigans like that.  I wouldn't put it past malware either.

0 Kudos
mustaphaarakji
Contributor
Contributor

renaming the vmware.exe didn't work for me.

antivirus stop didn't work

vmplayer didn't work

my laptop was running on battery, once I plugged in the power, i was able to power the machines !!

0 Kudos
dangerpaz
Contributor
Contributor

You have to verify the windows services running on your computer. In particular, you have to verify "VMware Workstation Server". If it is not started, you have to start it.

ricstc
Contributor
Contributor

For those where renaming the exe makes no sense, running the original exe with administrative rights (right click run ....) works

Try it

ramalingeswar
Contributor
Contributor

Simple problem

it will work 100%

steps as follows: go to Run ------------>services.msc-------->start the service name called VMWare authorization service and try to start vmware workstation it will work.

For any compliments mail to p.ramalingeswar@gmail.com

Regards,

Eswar

Ghost28
Contributor
Contributor

Some times to start the Authorization service you need Administrator rights. So Run Workstation as Admin:smileygrin:

0 Kudos
admin
Immortal
Immortal

Ghost28 wrote:

Some times to start the Authorization service you need Administrator rights. So Run Workstation as Admin:smileygrin:

You always need to be administrator to start or stop services on Windows.

The VMware Authorization Service serves two purposes:

  1. To allow non-administrators to power on VMs (which normally requires administrator privileges).
  2. To allow you to connect to VMs that running in the background.

If you run Workstation as administrator, then #1 isn't necessary (and the VMware Authorization Service isn't used).

sgcvision
Contributor
Contributor

Thank you @dangerpaz, your suggestion solved my problem. "VMware Workstation Server" was not running, after starting it I was able to run my VM.

Question for @VMware: Why is Workstation not smart enough to do this automatically!? The least you could do is provide a meaningful error message.

alex3518
Contributor
Contributor

Poor Idea, and of course, cannot do nothing !

0 Kudos
rengeek33
Contributor
Contributor

If the services (VMWare Authorization Service and VMWare Workstation Server) are already running, then "restart" them.  This is what worked for me.

0 Kudos
alex3518
Contributor
Contributor

- Stop & Start (restart) All VM Services:

Type in CMD:

To Stop:

NET STOP "VMware Authorization Service"

NET STOP "VMware DHCP Service"

NET STOP "VMware NAT Service"

NET STOP "VMware USB Arbitration Service"

taskkill /im vmware-tray.exe /f

taskkill /im vmware-tray.exe /f

To Start:

NET START "VMware Authorization Service"

NET START "VMware DHCP Service"

NET START "VMware NAT Service"

NET START "VMware USB Arbitration Service"

START C:\Progra~2\VMware\VMWARE~1\vmware-tray.exe

START C:\Progra~2\VMware\VMWARE~1\vmware-tray.exe

Or save it as ,bat file with notepad & just Run!!!

Or use Those in attachment>

Respectfully yours Prof.Dr. Aleksandar Blagojević Ph.EMD.,Dip.ING

microshitco@gmail.com

or: 24/7 direct access phone: +381216619460

(Skype: blagoje12354)

0 Kudos
tcailleau
Contributor
Contributor

For me running vmware.exe "As Administrator" resolved the issue.

C:\Program Files (x86)\VMware\VMware Workstation\vmware.exe > "Run As Administrator"