I wanted to share this issue and workaround for the good of the order. Please be aware that VMware has been notified of this issue and the workaround described below may not be supported by VMware. Please also be aware that there are several other known issues with similar symptoms. If your issue does not match the symptoms described below, then this workaround is likely not for you.
The issue began after upgrading vCenter from 4.1 U2 to U3. The symptoms are:
- Performance Overview indicates the "Report application initialization is not completed successfully"
- Storage Views "the storage service is not initialized"
- vCenter Service Status has a "Storage Management Service" error of "Service initialization failed"
- Licensing Reporting Manager has an error
- sms.log has "[Microsoft][ODBC Driver Manager] Invalid string or buffer length" errors
Microsoft KB2653857 indicates that this is a known issue with SQL Server 2008 R2 prior to SP2 (as of 12/21/2012, SP2 is not supported by VMware), as well as SQL Server 2008 SP3. The issue occurs with JBDC connections when "Force Encryption" is enabled on the SQL Server.
To workaround this issue, perform the following steps:
- Download Java SE 6 U27 and install on a test Windows Server x64 VM.
- On the vCenter Server:
- Stop the "VMware VirtualCenter Management Webservices" service
- Rename "C:\Program Files\VMware\Infrastructure\jre" folder (retain this folder as a backup)
- Copy the "jre6" folder from the test VM to "C:\Program Files\VMware\Infrastructure\jre"
- Start the "VMware VirtualCenter Management Webservices" service
