Symptoms
- The performance overview in vCenter Server fails.
- You see the error:
Perf-charts experienced an internal error. Report application initialization is not completed successfully. Re-try in 60 seconds
- The Storage view in vCenter Server fails .
- You see the error:
The storage service is not initialized, try again later
- In the Jakarta log located at C:\j2sdk1.4.2_13\jre\lib\zi\Asia, you see the error:
The module path requested, null, is not in the same web application as this servlet, /vws
- In the SMS log located at C:\ProgramData\VMware\VMware VirtualCenter\Logs, you see the error:
Error creating vcdbClient com.vmware.vim.common.vdb.VdbException: Invalid DSN <DSN Name>
Resolution
This issue occurs due to a trailing or leading space in your DSN name.
Note: Ensure that the vCenter ODBC driver is a supported SQL Native Client. For more information, see Upgrading vCenter Server fails with the error: DSN is pointing to an unsupported ODBC driver (1015804).
To resolve this issue:
- Stop the VirtualCenter Server and VirtualCenter Management Webservices services. For more information, see Stopping, starting, or restarting vCenter services (1003895).
- Open ODBC and click the System DSN tab.
- Click Configure.
- Remove the trailing or leading space from the VirtualCenter DSN Windows registry key:
- Click Start> Run, type regedit, and click OK. The Registry Editor window opens.
- Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\VMWare, Inc\VMware VirtualCenter\DB.
- Click the DSN name and remove the leading or trailing space from it.
- Start the VirtualCenter Server and VirtualCenter Management Webservices services. For more information, see Stopping, starting, or restarting vCenter services (1003895).