profile for Gajendra D Ambi on Stack Exchange, a network of free, community-driven Q&A sites

Monday, February 28, 2011

vSphere 4.1 vCenter Server will not start

Issue: customer said that he is unable to connect to his new physical vCenter server which was working fine few days ago.
Resolution:
checked the VMware vCenter service and it was stopped.
Started the vCenter service but no go.
In the vCenter service properties used a specified account for login but no go.
Customer said that he has not rebooted the vCenter server.
Customer gets the error
|vcenter server could not connect to "vcenter". A connection failure occurred(unable to connect to the remote server)|
when he attempts to log into the vCenter server using the vSphere client.
Customer said that Wednesday was the last successful login.
KB Article: 1007669
made the sqlserver as the dependency service for the vCenter server service to start and rebooted the server and tried to relogin but no go.
When checked the services.msc the service was still starting but later it failed to start and manually starting the service did not help us to relogin but it yielded the same result.
<http://www.ozvms.com/index.php?option=com_content&view=article&id=553:virtualcenter-vpxd-command-line-switches&catid=50:tech-tips&Itemid=49>
Ran the command C:\Program Files\VMware\Infrastructure\VirtualCenter Server\vpxd.exe -s
and it came up with the error that the transaction log is full.
Tried to download and install the sql server management studio express but it threw an error while installing
|The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 29506.|
Disabled UAC and tried reinstalling it but no go.
1.Right click on desktop and click NEW – SHORTCUSTOMERT


2. Create shortcustomert to C:\Windows\SysWOW64\cmd.exe
3. Right click on the new shortcustomert and Run AS ADMINISTRATOR
4. Enter full path and file name: C:\Users\[YOUR NAME]\Downloads\SQLServer2005_SSMSEE_x64.msi
KB Article: 1003980
Issue Resolved.

No comments:

Post a Comment