VMware Cloud Community
ChromeAdmin
Contributor
Contributor

Cannot Connect to VirtualCenter Server

I cannot connect to my VirtualCenter Management Server. When trying to log in I get the error: Cannot connect to host 'servername': No connection could be made because the target machine actively refused it.

I found out that my VMware VirutalCenter Server services is not started and won't start at all. I looked at the vpxd log files and found this:

Log for VMware VirtualCenter, pid=5112, version=2.0.2, build=build-50618, option=Release, section=2

Current working directory: C:\Program Files\VMware\VMware VirtualCenter 2.0

Initializing SSL context

Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000

NFC connection accept timeout: 180000 milliseconds

NFC request timeout: 180000 milliseconds

NFC read timeout: 60000 milliseconds

NFC write timeout: 600000 milliseconds

SQL execution failed with return code -1 : create table VPX_INVT_REP (

INVENTORY_ID int not null,

COLLECT_DATE datetime not null,

constraint PK_VPX_INVT_REP primary key (INVENTORY_ID)

)

Unhandled exception <Error[VdbODBCError] (-1) "ODBC error: (42S01) - [ODBC SQL Server Driver][SQL Server]There is already an object named 'VPX_INVT_REP' in the database." is returned when executing SQL statement "create table VPX_INVT_REP (

INVENTORY_ID int not null,

COLLECT_DATE datetime not null,

constraint PK_VPX_INVT_REP primary key (INVENTORY_ID)

)

">

Please advise as what to do. I have considered deleting the SQL DB and creating a new DB. I am running SQL 2005 on a remote cluster (not local install of SQL 2005 on VCMS box). I am having a rough time getting support from HP (which we unfortunately bought our support through.).

Thanks!

Reply
0 Kudos
8 Replies
IB_IT
Expert
Expert

Was anything recently done? Upgrade, patching? Was this working before it stopped, or is this the 1st time you are trying to connect?

Can you run a repair on your VC management server? Make sure you have a good backup of the DB just in case...

Reply
0 Kudos
ChromeAdmin
Contributor
Contributor

This was a new install that was working for maybe a couple weeks. It was working after I added 2 new ESX servers to it and created a Cluster. I think the issue might have been that from trying to add a server that was already controlled by a different VirtualCenter Server. We used to have 1 esx server and 1 VCM server and I combined all of our licensings and then built a new VCM server and add the 2 new ESX servers to it successfully, then added the old ESX server to the new VCM server and I think that might have contributed to it.

Reply
0 Kudos
RParker
Immortal
Immortal

Check your SQL connection settings in ODBC. That's why VC won't start, it can't connect to the database.

Reply
0 Kudos
ChromeAdmin
Contributor
Contributor

I don't think that is the issue because when I test my ODBC connection, it connects fine. If you look at the error, "Unhandled exception <Error[c-main] (-1) "ODBC error: (42S01) - [c-main][c-main]There is already an object named 'VPX_INVT_REP' in the database." is returned when executing SQL statement "create table VPX_INVT_REP" it's trying to do something with the database and it can't.

Apparently this isn't a very common problem as I couldn't find anything on this site or the knowledgebase. I am thinking about deleting the database and creating a new one but I want to make sure that it won't hurt anything, etc.

Thanks.

Reply
0 Kudos
IB_IT
Expert
Expert

Chrome, I had a very similar problem not too long ago. It wasn't that exact message in the vpx log...it said something along the lines of a null password. DB admin confirmed that it wasn't locked, and I tested the ODBC connection and it tested just fine. I finally opened an SR and the VMWare tech was just as baffled. We ended up running a repair on the VC Management software and that fixed my issue. Not necessarily saying that would fix yours, but it may save you having to wipe your database and start fresh.

Reply
0 Kudos
ChromeAdmin
Contributor
Contributor

IB, thanks for the reply. So I tried to do the repair and ended up getting the following error during the "installing new services" portion of the install:

Error 1923.Service VMware VirtualCenter Server (vpxd) could not be installed. Verify that you have sufficient privileges to install system services. The account used to run the service must be valid and have the "logon as service" privilege." Retry/Cancel.

I am logged in as the domain administrator who is what I installed it as in the first place. I am using Remote Desktop with the "/console" switch and I installed it the first time the same way over Remote Desktop.

Any ideas. Sounds almost like I need to start over and uninstall/reinstall.

Thanks.

Reply
0 Kudos
IB_IT
Expert
Expert

reboot the VC server and run the repair again.

Reply
0 Kudos
IB_IT
Expert
Expert

funny enough, I ran into the same error when I tried to run my repair the 1st time. Found that the VC service was disabled (probably because it uninstalled it during the repair, but got an error while trying to reinstall). I rebooted and ran the repair again and it worked like a charm.

Reply
0 Kudos