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

Accessing the Storage tab view in vCenter Server 5.0 fails with an internal error: com.vmware.vim.sms.fault.serviceInitializationException (2015180)

  • 3 Ratings

Symptoms

  • Selecting the Storage Tab view in VMware vCenter Server 5.0 fails with internal error:

    com.vmware.vim.sms.fault.serviceInitializationException

  • You see this alert on the vCenter Service Status window:

    VMWARE vCenter Storage Monitoring Service -> Service initialization failed.In the C:\ProgramData\VMware\VMware VirtualCenter\Logs\sms.log file you see the following errors: 2012-02-27 08:04:30,468 [Thread-17] DEBUG com.vmware.vim.sms.util.SimpleTimeCounter - TIMER STARTED: Query get_vpx_datacenter 2012-02-27 08:04:30,468 [Thread-17] ERROR com.vmware.vim.sms.provider.VcProviderImpl - Failed populating service cache org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Invalid object name 'dual'.)

Cause

  • The vCenter 5.0 instance was previously installed against an Oracle database.
  • During installation, the C:\ProgramData\VMware\VMware VirtualCenter\vcdb.properties file is updated with Oracle drivers.
  • The database is changed to a SQL database.
  • Entries in the vcdb.properties file has never been removed or updated to SQL Server drivers.

For more information on the root cause of this issue, see vCenter 5.0 U1 Release Notes.

Resolution

To resolve this issue, you must:
  1. Backup this file: 

    C:\ProgramData\VMware\VMware VirtualCenter\vcdb.properties

  2. Remove the reference to the Oracle drivers from this file: 

    C:\ProgramData\VMware\VMware VirtualCenter\vcdb.properties 
 
After an upgrade to vCenter Server 5.0, the database type in vcdb.properties may be incorrectly changed, affecting vCenter functionality. This can occur if the database server hostname contains the substrings "db2" or "oracle".
 
To workaround this issue, ensure that the database Server hosting the vCenter Database does not contain the string "db2" or "oracle". Alternatively, you can change the vcdb.properties to the correct format.

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

  • 3 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.
  • 3 Ratings
Actions
KB: