Vcenter Server service

Mikdilly

Continue to have a problem with vcenter service and vcenter web access service not starting. See this error in Windows 2008 event log:

"The description for event ID 1000 from source Vmware virtual center server cannot be found.
Either the component that raises the event is not installed on your local computer or the installation is corrupted.
You can install or repair the component on the local computer."

Knowledge base from vmware seems to point to sql server service not listening on correct port, if vcenter server installed with sql express server on same machine, does it need to be listening?

Ran a "netstat -anb" on vcenter server machine, sql server service shows as listening on port 7005, vmware indicates it should be listening on 1433. Tried using sql configuration manager to change the local port for the ip addresses to use 1433, but even after changing the port and running the netstat command, it still shows sql server service listening on 7005.

IIS is not enabled on the server and ports 80 and 443 are only open for vcenter server.

Can i just cut my losses and uninstall vcenter server and sql express and re-install, what happens if you remove vcenter server without first removing the hosts from a cluster?

meadIT

What version of vCenter are you running? Do the services fail to start only on boot, or also fail if you manually start them?

Did you restart the SQL service after disabling dynamic ports and configuring it to use port 1433?

Can you post the vpx.log from C:\ProgramData\VMware\VMware VirtualCenter\Logs\?

You can uninstall and re-install vCenter, then add the hosts back to it, but you will probably run into the same issue again.

Mikdilly

Vcenter server 5.1, fail on boot and when manually started

yes, restarted sql server service after changing ports, could possibly be changing wrong field, deleted entry in dynamic port and entered 1433 in local port field for ip address entries for ip address and loopback.

Do you mean the vpxd.log? At work now, can't post until tonight, checked it last night but couldn't tell anything from it.

Is it possible to run into anamolies when you continuously re-install the the trial versions onto the same drives? Seems like strange things keep happening as i've probably re-installed the trial version of esxi 5.1 and vcenter at least 4 times. The usb drives are low level formatted each time before the the ESXi trial is re-installed. Vcenter server is re-installed onto the same VM with a fresh copy of the database.

meadIT

Does the SSO service also fail to start? If so, take a look at this blog post and see if it helps. It may be that the SSO service bound its database connection to the dynamic port used during installation. The post details how to reset it to port 1433.

Issue with SSO and SQL Express

Mikdilly

meadIT wrote: »

Does the SSO service also fail to start? If so, take a look at this blog post and see if it helps. It may be that the SSO service bound its database connection to the dynamic port used during installation. The post details how to reset it to port 1433.

Issue with SSO and SQL Express

Never checked SSO service, will check this tonight after work, thanks

Mikdilly

SSO service is started

Last part of vpx log:

2013-06-17T20:42:10.490-04:00 [01688 warning 'VpxProfiler'] Vpxd::ServerApp::Init
[SessionManagerMo::Init()] took 6131 ms
2013-06-17T20:42:10.490-04:00 [01688 error 'vpxdvpxdMain'] [Vpxd::ServerApp::Init]
Init failed: Unexpected exception
--> Backtrace: -->backtrace[00] rip 000000018018977a-->backtrace[01] rip 0000000180100c98--> backtrace[02] rip 0000000180101fae-->
backtrace[03] rip 000000018008aeab--> backtrace[04] rip 00000000006d4971-->backtrace[05] rip 0000000000671298
--> backtrace[06] rip 00000000006716c9-->backtrace[07] rip 00000000005e0fae--> backtrace[08] rip 000000014070bfb8-->backtrace[09] rip 000000013f600078--> backtrace[10] rip 000000013f60016a-->backtrace[11] rip 000000013f600279--> backtrace[12] rip 000000013f600609
--> backtrace[13] rip 000000013f942903--> backtrace[14] rip 00000001400ee4b9--> backtrace[15] rip 00000001400e835c
--> backtrace[16] rip 0000000140308a3b-->backtrace[17] rip 000007fefe24a82d--> backtrace[18] rip 000000007682652d
--> backtrace[19] rip 0000000076f1c521-->
2013-06-17T20:42:10.490-04:00 [01688 warning 'VpxProfiler'] ServerApp::Init [TotalTime] took 141383 ms
2013-06-17T20:42:10.490-04:00 [01688 error 'Default'] Failed to intialize VMware VirtualCenter.
Shutting down...
2013-06-17T20:42:10.571-04:00 [01688 info 'vpxdvpxdSupportManager'] Wrote uptime information
2013-06-17T20:42:13.694-04:00 [02904 warning 'VpxProfiler' opID=SWI-6f2a3302]
VpxUtil_InvokeWithOpId [TotalTime] took 12012 ms
2013-06-17T20:42:16.068-04:00 [01704 info 'Default'] Thread detached
2013-06-17T20:42:16.068-04:00 [02756 info 'Default'] Thread detached
2013-06-17T20:42:26.216-04:00 [02904 warning 'VpxProfiler' opID=SWI-864f0028]
VpxUtil_InvokeWithOpId [TotalTime] took 12012 ms
2013-06-17T20:42:38.737-04:00 [02904 warning 'VpxProfiler' opID=SWI-db5763cd]
VpxUtil_InvokeWithOpId [TotalTime] took 12012 ms
2013-06-17T20:42:40.038-04:00 [00652 info 'Default'] Thread attached
2013-06-17T20:42:40.038-04:00 [02784 info 'Default'] Thread attached
2013-06-17T20:42:51.259-04:00 [02904 warning 'VpxProfiler' opID=SWI-41ae09e3]
VpxUtil_InvokeWithOpId [TotalTime] took 12012 ms
2013-06-17T20:43:03.666-04:00 [02904 warning 'VpxProfiler' opID=SWI-9c5c86bb]
VpxUtil_InvokeWithOpId [TotalTime] took 12012 ms
2013-06-17T20:43:11.934-04:00 [01688 info 'Default'] Forcing shutdown of VMware VirtualCenter now

Essendon

Could it possibly have something to do with the way the various services come up? Dependency order I guess.

Try setting, SSO to automatic, Inventory service to delayed start, Profile-driven service to delayed start, VCMSDS to delayed start.

Mikdilly

Essendon wrote: »

Could it possibly have something to do with the way the various services come up? Dependency order I guess.

Try setting, SSO to automatic, Inventory service to delayed start, Profile-driven service to delayed start, VCMSDS to delayed start.

Did notice that SQL service is taking a while to start, virtualcenter service is dependent on the sql service and is set to delayed start. Overall, the vm itself seems to run slow, takes a long time to load the desktop. The consumed CPU only shows 52Mhz, consumed host memory is 4041MB, guest memory started out at 3500MB and has gone down as the server loads the desktop. Would like to remove everything having to do with vcenter server on this vm and install on a different vm but the hosts are part of HA and DRS enabled cluster, won't uninstalling vcenter server without first putting the hosts in maintenance mode cause a problem?

Essendon

I've reinstalled vCenter a number of times and havent had any issues. Just leave the database intact, reinstall, use the same database and add the hosts back in. DRS obviously wont work during this time, HA will.

Mikdilly

Seeing as how SQL service was taking a while to start I tried changing SSO and virtualcenter service to manual. Rebooted the VM and waited until SQL service started and then started SSO and then virtualcenter. SSO started but still got an error when starting virtualcenter. The vpxd log is now a lot smaller and shows an error logging into the database.

2013-06-17T23:44:24.521-04:00 [01584 error 'Default'] A database error occurred: ODBC error:
(28000) - [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.
2013-06-17T23:44:25.412-04:00 [01584 warning 'VpxProfiler'] Vpxd::ServerApp::Init [VpxdVdb::Init(VpxdVdb::GetVcVdbInstId(), false, false, NULL)] took 30326 ms
2013-06-17T23:44:25.412-04:00 [01584 error 'vpxdvpxdMain'] [Vpxd::ServerApp::Init] Init failed: VpxdVdb::Init(VpxdVdb::GetVcVdbInstId(), false, false, NULL)
--> Backtrace:
--> backtrace[00] rip 000000018018977a
--> backtrace[01] rip 0000000180100c98
--> backtrace[02] rip 0000000180101fae
--> backtrace[03] rip 000000018008aeab
--> backtrace[04] rip 0000000000415c2c
--> backtrace[05] rip 0000000000436512
--> backtrace[06] rip 000000014062993c
--> backtrace[07] rip 000000014062835c
--> backtrace[08] rip 0000000140848a3b
--> backtrace[09] rip 000007fefe0ea82d
--> backtrace[10] rip 0000000076ba652d
--> backtrace[11] rip 0000000076eec521
-->
2013-06-17T23:44:27.663-04:00 [01584 warning 'VpxProfiler'] ServerApp::Init [TotalTime] took 34523 ms
2013-06-17T23:44:27.663-04:00 [01584 error 'Default'] Failed to intialize VMware VirtualCenter. Shutting down...
2013-06-17T23:44:27.663-04:00 [01584 info 'vpxdvpxdSupportManager'] Wrote uptime information
2013-06-17T23:44:27.663-04:00 [01584 error 'Default'] Alert:false@ d:/build/ob/bora-799731/bora/vpx/vpxd/util/vdb.cpp:422
--> Backtrace:
--> backtrace[00] rip 000000018018977a
--> backtrace[01] rip 0000000180100c98
--> backtrace[02] rip 0000000180101fae
--> backtrace[03] rip 000000018009752a
--> backtrace[04] rip 000000013fde1899
--> backtrace[05] rip 00000001406278e2
--> backtrace[06] rip 000000014062839a
--> backtrace[07] rip 0000000140848a3b
--> backtrace[08] rip 000007fefe0ea82d
--> backtrace[09] rip 0000000076ba652d
--> backtrace[10] rip 0000000076eec521
-->
2013-06-17T23:44:27.663-04:00 [01584 info 'utilvpxdVdb'] Registry Item DB 5 value is '50'
2013-06-17T23:44:27.663-04:00 [01584 info 'utilvpxdVdb'] [VpxdVdb::SetDBType] Logging in to DSN: VMware vCenter with username
2013-06-17T23:44:27.679-04:00 [02288 info 'Default'] Thread attached
2013-06-17T23:44:29.818-04:00 [03008 warning 'VpxProfiler' opID=SWI-f2fc2bab] VpxUtil_InvokeWithOpId [TotalTime] took 12012 ms
2013-06-17T23:44:35.626-04:00 [02288 info 'Default'] Thread detached
2013-06-17T23:44:35.626-04:00 [02752 info 'Default'] Thread attached
2013-06-17T23:44:37.171-04:00 [00252 info 'Default'] Thread detached
2013-06-17T23:44:41.839-04:00 [03008 warning 'VpxProfiler' opID=SWI-3c90d4a1] VpxUtil_InvokeWithOpId [TotalTime] took 12012 ms
2013-06-17T23:44:53.860-04:00 [03008 warning 'VpxProfiler' opID=SWI-51a49aa8] VpxUtil_InvokeWithOpId [TotalTime] took 12012 ms
2013-06-17T23:45:00.199-04:00 [02876 info 'Default'] Thread attached
2013-06-17T23:45:00.199-04:00 [02880 info 'Default'] Thread attached
2013-06-17T23:45:01.807-04:00 [01584 info 'Default'] [VdbSchemaLoader::LookupSchemaFromDB] Loaded schema and index information from DB
2013-06-17T23:45:05.881-04:00 [03008 warning 'VpxProfiler' opID=SWI-16106d54] VpxUtil_InvokeWithOpId [TotalTime] took 12012 ms
2013-06-17T23:45:17.902-04:00 [03008 warning 'VpxProfiler' opID=SWI-2db19de6] VpxUtil_InvokeWithOpId [TotalTime] took 12012 ms
2013-06-17T23:45:30.017-04:00 [03008 warning 'VpxProfiler' opID=SWI-965c291f] VpxUtil_InvokeWithOpId [TotalTime] took 12105 ms
2013-06-17T23:45:42.038-04:00 [03008 warning 'VpxProfiler' opID=SWI-30cb1bd5] VpxUtil_InvokeWithOpId [TotalTime] took 12012 ms
2013-06-17T23:45:54.059-04:00 [03008 warning 'VpxProfiler' opID=SWI-31fcb27e] VpxUtil_InvokeWithOpId [TotalTime] took 12012 ms
2013-06-17T23:45:57.728-04:00 [01584 info 'Default'] Forcing shutdown of VMware VirtualCenter now

jibbajabba

Is the SQL Server remotely or local installed on the same box ?

If on the same box, have you tried to edit your ODBC connection and re-test the settings ?



If remotely, then you might need to change the ODBC settings as it mentions the System Account, which won't have access over the network.

Mikdilly

SQL server installed on same VM that vcenter is running on, what would be the steps to edit the ODBC connection and re-test?

jibbajabba

Control Panel > Administrative Tools > Data Sources and edit the vcenter connection. Just go through the settings without changing anything until you see the screen I have posted.

Mikdilly

Tested OK



Going to try what Essendon recommended and re-install Vcenter

Essendon

And you want SQL to come up before vCenter does.

Mikdilly

Could not re-install vcenter on original VM, could not connect at step to use existing database, wouldn't even install a new database. Went to a different VM on different host, was able to install all required pieces for vcenter but after it was installed noticed the VM ran as slow as the old one, looked as task mgr and saw 3 java.exe using large amounts of memory, phys memory showed at 96%.

Used tweaks from this site to limit java memory usage:

Tweaking Java.exe memory usage on vCenter Server 5.1 « Default Reasoning


Phys memory is now down to 65% and vcenter server is now up and running.

Essendon

So looks like the VM was screwed somehow. Glad you got it running.