Hi Guys,
I've got vCenter 4.1 and SQL 2008 R2 installed on the same Windows 2008 R2 host. My issue is that the vCenter Service fails to start upon reboot. I can start the service manually, but it will not start automatically upon reboot of the server.
I have created dependences on the vCenter Service for MSSQLSERVER and ADAM_VMwareVCMSDS but this has made no difference. SQL starts fine, as does Update Manager, but vCenter does not. I've delayed the start-up of the service but this makes no difference. My ODBC links are OK as I can start the service manually once the host has booted up. Here are the extracts from my log files...
Section for VMware VirtualCenter, pid=2920, version=4.1.0, build=build-258902, option=Release
Current working directory: C:\Windows\system32
Log path: C:\ProgramData\VMware\VMware VirtualCenter\Logs
Using system libcrypto, version 9080CF
Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000
Starting VMware VirtualCenter 4.1.0 build-258902
Log directory: C:\Windows\system32\config\systemprofile\AppData\Local\VMwarevpx.
Total virtual memory available for the process 8589934464 KB
Enabled low-frag process heap.
Calling: VpxCallbackDesc::Init(MakeFunctor(this, &ServerApp::RequestShutdown))
Calling: VpxLroList::Init(ltud)
Calling: VpxdCharacterizeThreadpool(ltud)
Calling: VpxdCertificate_Load(gDB, CERTIFICATE_VMDBPATH )
Calling: VpxdVdb::Init(VpxdVdb::GetVdb(), false, false)
ODBC error: (28000) - [http://SQL Server Native Client 10.0|http://SQL Server Native Client 10.0][SQL Server]Login failed for user 'virtualcenter'.
Error getting configuration info from the database
Init failed: VpxdVdb::Init(VpxdVdb::GetVdb(), false, false)
Failed to intialize VMware VirtualCenter. Shutting down...
Forcing shutdown of VMware VirtualCenter now
Any help or advice would be great! Thank you...
Regards,
BlackMesa
Have you double checked the context under which the VM services are running?
Make sure that all credentials etc are set correctly and that your GPOs / Local machine policy allows the user account for the service all relevant rights (Run as a service etc) - Check your Windows event logs for failure codes, as these will show whether a) the service actually tried to load, b) What errors were logged
Secondly, make sure that the Account being used for the service ( user 'virtualcenter' in your case) has all the relevant access rights to the SQL database.
i have once had an instance where I upgraded a Virtual Center and all thes econfig settings were reset to defaults - which did not have the full access rights to the SQL DB etc.
