VMware Cloud Community
iforbes
Hot Shot
Hot Shot
Jump to solution

Virtual Center service terminates unexpectedly...

I'm running ESX 3.0.1. I currently have a license for virtual center and have installed it successfully. We're going through an IP renumbering project and when I changed the IP address of my virtual center host and restarted it all my vm's were in a disconnected state.

I've decided to install another virtual center on a host in the new IP subnet. Since we only have one virtual center license I cut and paste the VC license into my server based license file on the new host (another project is a migration of exisiting vm's to new ESX hosts in the new subnet), which is also a new license server.

The license server installs and the service starts ok. When I then attempt to install virtual center it installs ok, but the service terminates right away. The event log states that the virtual center service failed to initialize.

My question - Why is virtual center service terminating?

Thanks

0 Kudos
1 Solution

Accepted Solutions
VirtualNoitall
Virtuoso
Virtuoso
Jump to solution

Hello,

Is this a remote SQL server? If so Trusted\Windows Authentication is not supported and you need to use standard SQL security.

View solution in original post

0 Kudos
8 Replies
VirtualNoitall
Virtuoso
Virtuoso
Jump to solution

Hello,

VCMS logs can be found in c:\windows\temp\vpx

Have a look in there for anything out of the ordinary. Post back here if you find something but don't know what to make of it.

0 Kudos
dtrottier
Contributor
Contributor
Jump to solution

This is what the log looks like:

Log for VMware VirtualCenter, pid=3948, version=2.0.1, build=build-32042, option=Release, section=2

\[2007-07-12 18:14:09.750 'App' 4048 info] Current working directory: C:\WINDOWS\system32

\[2007-07-12 18:14:09.750 'App' 4048 info] Initializing SSL context

\[2007-07-12 18:14:11.359 'App' 4048 info] Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000

\[2007-07-12 18:14:11.421 'BaseLibs' 4048 info] NFC connection accept timeout: 180000 milliseconds

\[2007-07-12 18:14:11.421 'BaseLibs' 4048 info] NFC request timeout: 180000 milliseconds

\[2007-07-12 18:14:11.421 'BaseLibs' 4048 info] NFC read timeout: 60000 milliseconds

\[2007-07-12 18:14:11.421 'BaseLibs' 4048 info] NFC write timeout: 600000 milliseconds

\[2007-07-12 18:14:11.468 'App' 4048 info] Starting VMware VirtualCenter 2.0.1 build-32042

\[2007-07-12 18:14:11.468 'App' 4048 info] Account name: SYSTEM

\[2007-07-12 18:14:11.468 'App' 4048 info] \[VpxOsLayer] Enabled low-frag process heap.

\[2007-07-12 18:14:11.468 'App' 4048 info] \[VpxOsLayer] Enabled low-frag crt heap.

\[2007-07-12 18:14:11.468 'App' 4048 info] \[VpxLRO] 32 max LROs

\[2007-07-12 18:14:11.468 'App' 4048 info] \[VpxLRO] 6 reserved internal LROs

\[2007-07-12 18:14:11.468 'App' 4048 info] \[VpxLRO] 6 reserved blocker LROs

\[2007-07-12 18:14:11.468 'App' 4048 info] \[VpxLRO] 6 reserved short LROs

\[2007-07-12 18:14:11.468 'App' 4048 info] \[VpxLRO] 2 reserved long LROs

\[2007-07-12 18:14:11.468 'App' 4048 info] \[VpxLRO] 600-second task lifetime

\[2007-07-12 18:14:11.984 'App' 4048 error] ODBC error: (28000) - \[Microsoft]\[ODBC SQL Server Driver]\[SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

\[2007-07-12 18:14:11.984 'App' 4048 error] Failed to intialize VMware VirtualCenter. Shutting down...

\[2007-07-12 18:14:11.984 'App' 4048 info] Shutting down VMware VirtualCenter now

\[2007-07-12 18:14:12.000 'App' 4048 error] SetServiceStatus failed: The handle is invalid

It looks like it's an OBDC SQL authentication issue. I've configured the SQL authentication to use Windows NT authentication using the network logon ID. When I test the OBDC connection it's sucessful. Why does the log indicate that it's trying to use 'NT AUTHORITY\ANONYMOUS LOGON'?

0 Kudos
VirtualNoitall
Virtuoso
Virtuoso
Jump to solution

Hello,

Is this a remote SQL server? If so Trusted\Windows Authentication is not supported and you need to use standard SQL security.

0 Kudos
dtrottier
Contributor
Contributor
Jump to solution

Yes. It was a remote connection. Thanks for letting me know about that. One other question. I now used standard SQL security and created an instance on SQL 2005. When I try and configure the ODBC connection, it gets refused. I created another instance on SQL 2000 and the ODBC connection was successful. Is there some support issue with SQL 2005?

0 Kudos
VirtualNoitall
Virtuoso
Virtuoso
Jump to solution

Is your SQL 2005 server setup for standard SQL security? I would check that.

0 Kudos
masaki
Virtuoso
Virtuoso
Jump to solution

You did it on the system DSN but which password did you give to the DB user when you install VC?

0 Kudos
iforbes
Hot Shot
Hot Shot
Jump to solution

I just ended up using the sql login for authentication and not integrated windows authentication.

Thanks for the help

0 Kudos
masaki
Virtuoso
Virtuoso
Jump to solution

thanks are welcome. Points are much better.

Please assign points for helpful answers.

See you on VMTN

0 Kudos