Anything for sysadmins!


The transaction log for database ‘VIM_VCDB’ is full

Today my VMWare vCenter crashed. The event viewer showed me the cause of the problem. The VIM_VCDB database used for performance logs amongst others has a growth restriction set to 500MB. If you add a lot of VMs or if you increase the log level, you might run into this error.


  • Can't connect to vCenter with vSphere client
  • VMWare Virtual Center Server service is not started
  • Event viewer shows critical events with ID 9002 and ID 1000 (below)
Event Type:    Error

Event Source:    VMware VirtualCenter Server

Event Category:    None

Event ID:    1000

Date:        12/22/2010

Time:        1:06:02 AM

User:        N/A

Computer:    <server>


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. Error: Error[VdbODBCError] (-1) "ODBC error: (42000) - [Microsoft][SQL Native Client][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" is returned when executing SQL statement "UPDATE VPX_HOST WITH (ROWLOCK) SET DATACENTER_ID = ? , DNS_NAME = ? , HOST_KEY = ? , IP_ADDRESS = ? , EXPECTED_SSL_THUMBPRINT = ? , HOST_SSL_THUMBPRINT = ? , USER_NAME = ? , PASSWORD = ? , PASSWORD_LAST_UPD_DT = ? , SOAP_PORT = ? , AUTHD_PORT = ? , ENABLED = ? , VPXA_ID = ? , MASTER_GEN = ? , MASTER_SPEC_GEN = ? , VMOTION_ENABLED = ? , FAULTTOLERANCE_ENABLED_FLG = ? , LICENSED_EDITION = ? , LOCAL_IP_ADDRESS = ? , ADMIN_DISABLED_FLG = ? , MANAGEMENT_IP = ? WHERE ID = ?".

Event Type:    Error

Event Source:    MSSQL$SQLEXP_VIM

Event Category:    (2)

Event ID:    9002

Date:        12/22/2010

Time:        1:06:02 AM


Computer:    <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


Change the autogrowth settings in the SQL Management Studio. You might have to install the SQL Server Management Studio Express, but you can also use the full version if you have it installed.

  1. Right click the VIM_VCDB database and select Properties
  2. Click Files in the left menu and click the Autogrowth edit button of the VIM_VCDB_log
  3. Set the Maximum File Size to an appropriate value, 2GB in my case
  4. Start the VMware VirtualCenter Server service on the vCenter Server

If you run into the problem again you can repeat the steps and increase the Restricted File Growth even more

Filed under: Uncategorized No Comments

Reset the domain (controller) policy GPOs

Somehow the default domain policy got borked during an import of GPOs. I had to restore the domain policy and luckily Microsoft created a tool for that. The tool is included in Windows 2003 and Windows 2008 and is specially made for restoring the Default Domain Policy and Default Domain Controller Policy group policy objects.

C:\>dcgpofix /?

Microsoft(R) Windows(R) Operating System Default Group Policy Restore Utility v5.1

Copyright (C) Microsoft Corporation. 1981-2003

Description: Recreates the Default Group Policy Objects (GPOs) for a domain

Syntax: DcGPOFix [/ignoreschema] [/Target: Domain | DC | BOTH]

/target: {Domain | DC | BOTH}Optional. Specifies the GPO to be restored -- the Default Domain Policy GPO, the Default Domain Controllers Policy GPO, or both.


Optional. Use this switch to have this tool ignore the schema version of the Active Directory. Otherwise this tool will only work on the same schema version as the Windows version in which the tool was shipped.

As easy as that!