Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Upgrading vCenter Server 4.0 to 4.1 fails with the error: Exception Thrown while executing SQL script (1025139)

Symptoms

  • You cannot upgrade from vCenter Server 4.0 to 4.1
  • Upgrading vCenter Server 4.0 to 4.1 fails
  • You see the error:

    Exception Thrown while executing SQL script
  • In vminst.log (located at C:\Users\username\AppData\Local\Temp\2 in Windows 2008 and C:\Documents and Settings\username\Local Settings\Temp in the legacy versions of Windows), you see entries similar to:

VMware VirtualCenter-build-258902: 07/21/10 09:22:00 Getting Property DB_USERNAME = sa
VMware VirtualCenter-build-258902: 07/21/10 09:22:00 Found "C:\vSphere\VMware-VIMSetup-all-4.1.0-259021\vpx\dbupgrade\bin\VCDatabaseUpgrade.exe"
VMware VirtualCenter-build-258902: 07/21/10 09:22:50 Process returned 12
VMware VirtualCenter-build-258902: 07/21/10 09:22:50 Exception thrown while executing sql script.
VMware VirtualCenter-build-258902: 07/21/10 09:22:50 Getting Property UILevel = 5
VMware VirtualCenter-build-258902: 07/21/10 09:22:50 Getting Property ProductName = VMware vCenter Server
VMware VirtualCenter-build-258902: 07/21/10 09:39:33 End Logging
VMware VirtualCenter-build-258902: 07/21/10 09:39:41 Begin Logging
VMware VirtualCenter-build-258902: 07/21/10 09:39:41 --- CA exec: VMCleanupRegistry
VMware VirtualCenter-build-258902: 07/21/10 09:39:41 Getting Property TEMPLATE = x64
VMware VirtualCenter-build-258902: 07/21/10 09:39:41 Warning: Deleting a key that isn't empty: "HKEY_CURRENT_USER\VMW"
VMware VirtualCenter-build-258902: 07/21/10 09:39:41 Warning: Deleting a key that isn't empty: "\InstRTPaths"
VMware VirtualCenter-build-258902: 07/21/10 09:39:41 End Logging

Resolution

This issue may occur if: 
  • The vCenter Server database runs in the SQL Server 2000 compatibility mode when the upgrade is performed. vCenter Server 4.x is not compatible with SQL Server 2000 and supports only SQL Server 2005 or later. If the vCenter Server database runs in SQL Server 2000 compatibility mode during an upgrade, the upgrade fails and leaves the database in an inconsistent state.

    To resolve this issue:
  1. Restore the vCenter Server database from a backup. For information on how to do a database restore, see http://msdn.microsoft.com/en-us/library/ms190436.aspx.

    Note
    : The preceding link was correct as of March 25, 2011. If you find the link is broken, provide feedback and a VMware employee will update the link
    .

  2. Open SQL Server Management Studio.
  3. Enter your login credentials to connect to the SQL server.The login credentials can be a local Administrator account on the host.
  4. Click the Databases folder in the left side pane.
  5. Right-click the vCenter Server database and click Properties.
  6. Click Options on the left side pane.
  7. in the right side pane, click Compatibility Level and select the appropriate level of compatibility.

    For example:

    • If you are using SQL Server 2005, select SQL Server 2005 (90)
    • If you are using SQL Server 2008, select SQL Server 2008 (100)
  • The transaction log for vCenter Server database is full.

    To resolve the issue, increase the size of the SQL Server transaction log. For more information, see Changing the size of the SQL Server Express transaction log (1009149).

  • The SQL Agent jobs are not owned by same the service account that installed the vCenter Server. 

    To resolve this issue, Change the job owner to the same account.

Tags

install-upgrade-vcenter-database-fails  install-upgrade-vcenter-fails-error

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 24 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 24 Ratings
Actions
KB: