An Unrecoverable Error Has Occurred Stopping The Vmware Virtualcenter Service
NSXVirtual SAN vCenterFusionWorkstationvExpertVMware {code} CloudCredSubmit a Link Home > VMTN > VMware vCenter™ > VMware vCenter™ Server > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 1 Reply Latest reply: Oct 8, 2014 11:24 PM by Praveenmna An unrecoverable problem has occurred, stopping the VMware VirtualCenter service. Error: Error[VdbODBCError] (-1) "ODBC error: (23000) jvalks Oct 8, 2014 10:36 PM Hi,Out of the blue our vCenter server stops when the backup jobs are running (NetApp SnapProtect 10). All I can find in the eventviewer is:The description for https://kb.vmware.com/kb/2003674 Event ID 1000 from source VMware VirtualCenter Server cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.If the event originated on another computer, the display information had to be saved with the https://communities.vmware.com/thread/492064?start=0&tstart=0 event.The following information was included with the event: An unrecoverable problem has occurred, stopping the VMware VirtualCenter service. Error: Error[VdbODBCError] (-1) "ODBC error: (23000) - [Microsoft][SQL Server Native Client 10.0][SQL Server]Violation of PRIMARY KEY constraint 'PK_VPX_TASK'. Cannot insert duplicate key in object 'dbo.VPX_TASK'. The duplicate key value is (500248)." is returned when executing SQL statement "INSERT INTO VPX_TASK WITH (ROWLOCK) (TASK_ID, NAME, DESCRIPTIONID, ENTITY_ID, ENTITY_TYPE, ENTITY_NAME, LOCKED_DATA, COMPLETE_STATE, CANCELLED, CANCELLABLE, ERROR_DATA, RESULT_DATA, REASON_DATA, QUEUE_TIME, EVENT_CHAIN_ID, USERNAME, VM_ID, HOST_ID, COMPUTERESOURCE_ID, DATACENTER_ID, DESCRIPTION) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)"the message resource is present but the message is not found in the string/message tableWe are using version 5.1, SQL Server is on a always-on cluster running 2012.Any idea how to fix this?? 1088Views Tags: none (add) 5.1Content tagged with 5.1, vcenterContent tagged with vcenter This content has been marked as final. Show 1 reply 1. Re: An unrecoverable problem has occurred, stopping the
database and MSCS issue in vSphere 5.1 Categories: vCenter Server by magander3 A couple of months ago a customer of mine changed their vCenter Server database location from a standalone MSSQL 2008 SP2 installation to a Microsoft Cluster Service (MSCS) based MSSQL 2008 R2 SP2 installation. The intention is very good and it all comes down to increase the availability of the MSSQL server since you can do (at least) operating system, of the MSCS nodes, maintenance without taking the MSSQL service out of service. This is only partially true since the MSSQL service will be out of service during the time it takes for the MCSC service to fail over the MSSQL service from one MSCS node (VM or physical machine) to another MSCS node (VM or physical server). My customer runs the following environment: vCenter Server 5.1.0 1123961 ODBC File version on the vCenter Server 6.1.7600.16385 with date modified 2009-07-14 MSSQL 2008 R2 SP 2 10.50.4000 So guess what happens during a MSCS MSSQL service failover from node 1 to node 2? The vCenter Server shuts down! By taking a look in the VM, running the vCenter Server, event viewer (application log) we get the explanation: Event ID 1000: General message: The following information was included with the event: An unrecoverable problem has occurred, stopping the VMware VirtualCenter service. Error: Error[VdbODBCError] (-1) "ODBC error: (42000) - [Microsoft][SQL Server Native Client 10.0][SQL Server]SHUTDOWN is in progress." is returned when executing SQL statement "UPDATE VPX_ENTITY WITH (ROWLOCK) SET NAME = ? , TYPE_ID = ? , PARENT_ID = ? WHERE ID = ?" Click here to get the entire application log message and also the system log message. I have highlighted, in red, the most critical part in the message above. So if the vCenter Server tries to connect to the MSSQL Server during a MSCS fail over it will receive a message, via the ODBC driver, where the MSSQL Server tells the vCenter Server that it is being shut down. This is what actually happens, you stop the MSSQL Server service on on