• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3298
  • Last Modified:

Cannot start VMware VirtualCenter Server Service

I cannot connect to VMware Infrastructure. I check the log, it says "ODBC error: (08001) - [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied". And in the Event Viewer, it says "The description for Event ID ( 1000 ) in Source ( VMware VirtualCenter Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Failed to intialize VMware VirtualCenter. Shutting down...."

Do you have any idea why this happens? Thanks
0
dongocdung
Asked:
dongocdung
  • 2
3 Solutions
 
ComputerTechieCommented:
This is most likely database connectivity issues. If there are any hiccups with the database VC will crash as it cannot function without the database. You can check your VC server logs for errors. To view the log files directly open Windows Explorer and go to the C:\Windows\Temp\VPX directory on the Virtual Center server. If you use Patch2 it is supposed to handle this better, after you install Patch2 you need to change your Windows service for the VC Server. On the Recovery tab change it to Restart Service for 1st, 2nd and Subsequent failures.

http://www.vmware.com/support/vi3/doc/vc-201-200702-patch.html

From the Patch 2 release Notes...
# VirtualCenter Service Can Be Configured to Re-start Automatically. In previous releases, when the VirtualCenter database server went off-line for any reason, the VirtualCenter service shut down with a normal termination signal, and because the termination signal was deemed normal, the Windows Service Control Manager never attempted to restart the VirtualCenter service. With this release, the service recovery options can be configured to restart the VirtualCenter Server service automatically when this type of event occurs. By default, the service is configured to restart once, but you can modify the VMware VirtualCenter Server service control panel’s Recovery settings to restart after second failure and subsequent failures if you like, as follows:

1. From the Windows Start menu, select Control Panel>Administrative Tools>Services. The Services control panel opens.
2. Scroll down to select the VMware VirtualCenter Server control panel and double click on it to open the Properties dialog.
3. Click on the Recovery tab.
4. Select Restart the Service from the drop-down menu for Second Failure and Subsequent Failure settings.
5. Click OK to save.
6. Close the Control Panel.

If you install Patch2 read these firsts....
Beware Patch2 - http://www.vmware.com/community/thread.jspa?messageID=594826򑎊
Patch2 - http://www.vmware.com/community/thread.jspa?messageID=588439򏪗
Inventory cleared after Patch2 - http://www.vmware.com/community/thread.jspa?messageID=589339򏸛

CT
0
 
isiHelpDeskCommented:
Did this happen after an upgrade of VC to U3?
0
 
dongocdungAuthor Commented:
No....I did not upgrade anything. It just happened...
0
 
isiHelpDeskCommented:
That is strange.  This is the exact issue we had when upgrading to U3.  It is caused by a problem with the DB not being converted properly.  The sucky part is that there is NO solution from VMware techs that we could find.  We rolled back to a snapshot and havent attacked the issue again yet.

I am sorry I cant be of help here, but I hope that the similarity in our errors doesnt have the same conclusion.
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

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