Anything for sysadmins!


RESTORE cannot operate on database because it is configured for database mirroring

If you're trying to remove database mirroring from a DB, the mirror server will keep the DB in recovery mode. To take it out of recovery mode you'll have to run the following query:

Filed under: Uncategorized No Comments

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

Passwords are like underwear

Recently I found this statement on and as I work in a company where I can put things like this on a board, I couldn't resist to create a slightly altered version. We'll just mark it as user education…

Passwords are like underwear

You shouldn't leave them out where people can see them

You shouldn't loan them out to strangers

You should change them regularly

Tagged as: No Comments