Search the VMware Knowledge Base (KB)
View by Article ID

Upgrading to vCenter Server 5.x fails with the error: Exception thrown while executing SQL script (2007864)

  • 5 Ratings

Symptoms

  • Upgrading from vCenter Server 4.x to vCenter Server 5.x fails
  • The following message is displayed by the wizard during upgrade:

    The Wizard was interrupted before VMware vCenter Server could be completely Installed. Please refer to the log files vim-vcs.msi.log, vminst.log

  • You see the error: 

    Exception thrown while executing SQL script

  • In the %temp%\VCDatabaseUpgrade.log file, you see entries similar to:

    Got exception: ERROR [42000] [Microsoft][SQL Server Native Client 10.0][SQL Server]The transaction log for database 'VIM_VCDB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases ERROR [01000] [Microsoft][SQL Server Native Client 10.0][SQL Server]The statement has been terminated.
    Error while upgrading: ERROR [42000] [Microsoft][SQL Server Native Client 10.0][SQL Server]The transaction log for database 'VIM_VCDB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases ERROR [01000] [Microsoft][SQL Server Native Client 10.0][SQL Server]The statement has been terminated.

  • In the C:\ProgramData\VMware\VMware VirtualCenter\Logs\ vpxd.log file, you see entries similar to:

    • Failed to load tableDef 71 from database: Column SPBM_ENABLED does not exist in table VPX_COMPUTE_RESOURCE
    • YYYY-MM-DDT00:34:21.879-05:00 [00648 warning 'VpxProfiler'] ServerApp::Init [TotalTime] took 2012 ms YYYY-MM-DDT00:34:21.879-05:00 [00648 error 'Default'] [VpxdMain] Failed to initialize: vmodl.fault.ManagedObjectNotFound YYYY-MM-DDT00:34:21.879-05:00 [00648 error 'Default'] Failed to initialize VMware VirtualCenter. Shutting down... YYYY-MM-DDT00:34:21.879-05:00 [00648 info 'Default'] Wrote uptime information YYYY-MM-DDT00:34:31.879-05:00 [04060 warning 'VpxProfiler' opID=SWI-c541d78b] VpxUtil_InvokeWithOpId [TotalTime] took 12012 ms YYYY-MM-DDT00:35:19.959-05:00 [00648 info 'Default'] Forcing shutdown of VMware VirtualCenter now

Purpose

Modifying the  VIM_VCDB_log file resolves the issue.

Cause

This issue occurs if the vCenter Server database log does not have sufficient space to continue with the installation.

Resolution

To resolve this issue, modify the VIM_VCDB_log file.
 
To modify the VIM_VCDB_log file:
  1. Restore the vCenter Server database from a backup. For more information on performing a database restore, see the Microsoft article Copy Databases with Backup and Restore.

    Note: The preceding link was correct as of February 11, 2014. If you find the link is broken, provide feedback and 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 Databases folder in the left pane.
  5. Right-click the vCenter Server database and click Properties.
  6. Click File in the left pane.
  7. Modify the VIM_VCDB_log file using one of these options:
    • Increase the log file size under Maximum File Size (the default is set to 460 MB)
    • Select Unrestricted File Growth.

  8. Click OK.
  9. Restart the upgrade process.

Note: If using SQL Express the transaction logs and data file have hard limits, therefore you will not be able to do this workaround. An alternative solution is to restore the vCenter Server 4.x database and purge or truncate data from vpx_event, vpx_task and the vpx_hist_stat[1-4]. This has the added benefit of having a smaller DB and the upgrade should run through quickly. For more information, see Purging old data from the database used by VMware vCenter Server (1025914).

See Also

Update History

03/26/2013 - Added vCenter Server 5.1.x to Product Versions. 02/11/2014 - Added vCenter Server 5.5 to Product Versions.

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

  • 5 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)




Please enter the Captcha code before clicking Submit.
  • 5 Ratings
Actions
KB: