Skip to main content

VMware Workstation unrecoverable error - NOT_IMPLEMENTED - A log file is available in .log

Another issue I faced few days back was - VMware Workstation unrecoverable error: (vmx).

VMware Workstation unrecoverable error: (vmx)
NOT_IMPLEMENTED d:/build/ob/bora-185404/bora/vmx/main/pollVMX.c:3651
A log file is available in "G:\VPC\RakhiQAXPProfQtp\vmware.log".  A core file is available in "G:\VPC\RakhiQAXPProfQtp\vmware-vmx-4392.dmp".  Please request support and include the contents of the log file and core file. 
To collect data to submit to VMware support, select Help > About and click "Collect Support Data". You can also run the "vm-support" script in the Workstation folder directly.
We will respond on the basis of your support entitlement.

image

Resolution: This is not a documented method but something that worked for me. I think of it because of my extensive experience with restarting the Microsoft Windows for the resolution of many issues :)

Steps:

  1. Close VMWare
  2. Restart the Host operating system
  3. Start VMWare
  4. Select the Virtual Machine and click Run.
  5. It will show you the error as display above.
  6. Click OK and click at Run again.
  7. Now it will show you an option to select start in Safe Mode. Select this option and hit enter. It will start the loading process. You may see a message that you will not able to do this & that while in safe mode. Click Ok to that.
  8. Your virtual machine should open in safe mode.
  9. Now shut down the virtual machine (Start->Shut Down)
  10. Run the virtual machine again. This time no need to select Safe Mode.
  11. Your virtual machine should back to normal.
  12. It works for me. Once I had to do this steps twice but otherwise it work as listed here. Remember to re-start your host operating system so it release some of the files it may have locked.
Labels:

Comments

  1. Abel Braaksma5:53 AM, June 16, 2016

    When I received this error, it worked for me to simply restart the guest OS. The necessity to start in Safe Mode did not occur in my case. This happened with VMWare WorkStation 8.0.6 build-1035888.

    After restarting the guest OS, the error magically disappeared.

    ReplyDelete

Post a Comment

Popular posts from this blog

SharePoint WebPart Error - Unable to add selected web part (s) – MOSS 2007

ISSUE: Recently I faced this issue that when I try to deploy my WebPart.  Unable to add selected web part(s). WebPartName: Cannon unregister UpdatePanel with ID ‘ctl00RTMPanel’ since it was not registerd with the ScripManager. This might occure if the UpdatePanel was removed from the control tree and later added again, which is not supported. Parameter name: updatePanel.   I faced this issue twice and both the time the issue was not what display here. This could be sure to any error in the WebPart. Following are list resolution from multiple instances.   RESOLUTION: 1. Check the WebPartName.webpart file. Check whether you have a proper PublicKeyToken value. When I face the issue the value was PublicKeyToken=$PublicKeyToken$. If you have used WSP builder then in the Visual Studio you will find this file at \WebPartsProject\12\TEMPLATE\FEATURES\WebPartName\WebPartName.webpart. Sometime when you create a new WebPart using WSP builder then ...
4 comments
Read More >>>

Could not open virtual machine – vmx is not a valid virtual machine configuration file

I recently faced an issue with one of my VMWare virtual machine that when I try to run this virtual machine it did not work. VMWare display this message that “Could not open virtual machine: .vmx. ".vmx" is not a valid virtual machine configuration file.” ISSUE: Could not open virtual machine: G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx. "G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx" is not a valid virtual machine configuration file. I try to open .vmx file [G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx] in notepad then I found it was empty (0 KB). Resolution: I wanted to resolve it quickly so I try following method and it worked very well. But this is not a valid documented process so please try with caution. Following are the steps 1. First of all go to the folder where you have your virtual machine and delete all .lck folders. 564df2d4-03de-04e8-d1c3-bd2d53dcb1b7.vmem.lck Windows XP Professional.vmdk.lck ...
13 comments
Read More >>>

Google Chrome Error - Ah, Snap! Something went wrong while displaying this webpage

Many users are facing following error when they try to load the new Google Chrome Browser. Due to this error they could not use Google Chrome browser on their machine. This error is coming right after they installed the Google Chrome browser. The error message says: "Ah, Snap! Something went wrong while displaying this webpage. To continue, press Reload or go to another page." Following is a screen shot of the error. Error message asks to reload the or go to another page but no matter what they do, they still see this error message. Thanks to Rupesh Bhochhibhoya for solution to this problem. As per him, this problem is most probably because of anti-virus. The solution I learn is: goto properties of browser shortcut then append --no-sandbox on target line. Like: "C:\Documents and Settings\Administrator\Local Settings\Application Data\Google\Chrome\Application\chrome.exe" --no-sandbox then you are ready to go!! Please post in the comment if you have furt...
25 comments
Read More >>>