VMware Cloud Community
steve31783
Enthusiast
Enthusiast

VC Crashes 5-8 times a day

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: An unrecoverable problem has occurred, stopping the VMware VirtualCenter service. Check database connectivity before restarting. Error: Error[VdbODBCError] (-1) "ODBC error: (01000) - [ODBC SQL Server Driver][DBNETLIB]ConnectionWrite (send())." is returned when executing SQL statement "UPDATE VPX_ENTITY SET NAME = ? , TYPE_ID = ? , PARENT_ID = ? WHERE ID = ?".

Getting that error from eventvwr. There are several other SQL servers running on the server hosting the VC database, and none of them have lost connectivity. Have tried reinstalling VC, made sure ODBC connections are good, restored to old version of DB, tried pretty much everything.

Any ideas?

0 Kudos
10 Replies
hicksj
Virtuoso
Virtuoso

That error isn't much help. Check the vpx logs under windows\temp. You'll find all sort of (hopefully) useful info there!

0 Kudos
Dave_Mishchenko
Immortal
Immortal

Which version of VC are you running? The logs for the VC sevice will be here: c:\windows\temp\vpx\. Could you post the last bit of log before the service crashes? You'll want to look at the date modified for the log files as vpxd-0.log is not necessarily the most recent. There's a similar problem here you might want to look at. If you're running an older version of VC you may want to upgrade.

http://communities.vmware.com/message/517874

0 Kudos
steve31783
Enthusiast
Enthusiast

Completed host synchronization

Queuing SERVERIP:134 (host-9536)

SERVERIP134 (host-9536)

Updating vpxa for SERVERNAME (spec. genno 138358)

An unrecoverable problem has occurred, stopping the VMware VirtualCenter service. Check database connectivity before restarting. Error: Error[VdbODBCError] (-1) "ODBC error: (01000) - [ODBC SQL Server Driver][DBNETLIB]ConnectionWrite (send())." is returned when executing SQL statement "UPDATE VPX_ENTITY SET NAME = ? , TYPE_ID = ? , PARENT_ID = ? WHERE ID = ?"

Backtrace:

That is all that I see in the vpx logs..everything before those entries looks normal. (remove server name and IP for posting purposes)

0 Kudos
steve31783
Enthusiast
Enthusiast

Running VC2.02 build 61426 (latest and greatest)

0 Kudos
Dave_Mishchenko
Immortal
Immortal

Is it always the same update statement that it fails on?

0 Kudos
steve31783
Enthusiast
Enthusiast

Yes, the error is always identical.

VMWare support has had me try a bunch of things, and now they want me to rebuild the database from scratch but Id rather not...on another odd note, today, all of my permissions (for vm's, folders, etc.) just completely erased...no idea what happend.

0 Kudos
Jae_Ellers
Virtuoso
Virtuoso

VC running on local disk on dedicated HW? What kind of storage? Looks like corrupt DB or problem host configuration.

Does your DB checkout? Have you removed and added the host that always shows just before the svc shuts down?

Any templates on that server? Any new templates or vms added on that server just before things went haywire?

-=-=-=-=-=-=-=-=-=-=-=-=-=-=- http://blog.mr-vm.com http://www.vmprofessional.com -=-=-=-=-=-=-=-=-=-=-=-=-=-=-
0 Kudos
bevirtual
Contributor
Contributor

Was a solution ever found for this problem?

0 Kudos
steve31783
Enthusiast
Enthusiast

This was an odd one... support had me try everything, including completely rebuilding the VC database (which sucked).

The fix ended up being moving the db from one sql server to another. The odd thing is that there were a couple of other db's living on the same sql server that have not had any issues at all. Apparently the vc agent is VERY picky about its connection to the sql db, apparently more picky than other apps.

0 Kudos
bevirtual
Contributor
Contributor

Thanks Steve,

So what was different about the second sql server, fewer other db's?, more memory?, that caused the problem to go away? Just curious why the problem went away?

Jan

Date: Wed, 5 Dec 2007 12:13:20 -0800> From: communities-emailer@vmware.com> To: vir2ualjan@hotmail.com> Subject: http://VirtualCenter 2.x New message: "VC Crashes 5-8 times a day" > > bevirtual,> > A new message was posted in the thread "VC Crashes 5-8 times a day":> > http://communities.vmware.com/message/811880>; > Author : steve31783> Profile : http://communities.vmware.com/people/steve31783>; Message:

0 Kudos