[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4342
  • Last Modified:

Unable to shutdown Virtual Machine in ESX 3.5 Host

We are trying to restart a VM using vmware-cmd command since we are not able restart using VI Client.
We tried using the vmware-cmd --getstate command which shows the output as on which means the VM is still on.

When we try to use the vmware-cmd -reset hard or vmware-cmd -reset trysoft option, we get the below mentioned error :

VMControl error -999: Unknown error: SoapError: ServerFaultCode(1604) : (Operation failed since another task is in progress.)

The ESX Host has sufficient disk space and RAM, so I can assure that this is not an issue

Please advise as to how this problem can be resolved
0
kumarnirmal
Asked:
kumarnirmal
  • 3
  • 3
1 Solution
 
za_mkhCommented:
Do you use snapshots for backing up e.g. via VCB. That could be one issue.
But have you tried the following commands?
service mgmt-vmware restart

service vmware-vpxa restart

That should hopefully get them going again.
 
0
 
za_mkhCommented:
Oh this has to be done on the local console of the ESX server and not via an SSH session, as you will get disconnect due to the service restarts!
0
 
kumarnirmalAuthor Commented:
Now we are able to power off the VM, but when we try to recover it using Recovery Console, the CD gets stuck by saying that the disk is initializing and then the VM hangs.
The VM has got Windows XP SP2 as Guest OS.
0
[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

 
kumarnirmalAuthor Commented:
We have cloned the VM into a new VM using vConverter 4.0 and now after the VM was repaired, it has started working again.
0
 
za_mkhCommented:
If the command to restart the two services did allow you to at least start interacting with your vm again, you should at least then give that as an accepted answer as it could help others in the future. I think a snapshot on your VM that didn't get removed properly must have caused your VM to crash but based on your original question, this was another issue.
0
 
kumarnirmalAuthor Commented:
I couldnt disagree with your point.
0

Featured Post

2018 Annual Membership Survey

Here at Experts Exchange, we strive to give members the best experience. Help us improve the site by taking this survey today! (Bonus: Be entered to win a great tech prize for participating!)

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now