Knowledge Base
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

|
Storage Monitoring Service fails to start (2039067)
Symptoms
- Cannot start the vCenter Server Storage Monitoring service
- vCenter Server Storage Monitoring service fails to start
- In the sms.log file, you see entries similar to:
012-11-07 08:05:05,907 [Thread-15] DEBUG com.vmware.vim.sms.data.DataMapperImpl - Initializing cache database...
2012-11-07 08:05:05,907 [Thread-15] DEBUG com.vmware.vim.sms.data.DataMapperImpl - Executing sql script: C:/Program%20Files/VMware/Infrastructure/tomcat/webapps/sms/WEB-INF/classes/schema/cachedb.sql
2012-11-07 08:05:05,993 [Thread-15] ERROR com.vmware.vim.sms.data.DataMapperImpl - Error initializing cachedb
com.ibatis.common.jdbc.exception.NestedSQLException:
--- The error occurred in com/vmware/vim/sms/data/xml/CacheDbQuerySqlMap.xml.
--- The error occurred while executing mapped statement.
--- Check the runscript.
--- Check the statement or the result map.
--- Cause: org.h2.jdbc.JdbcSQLException: File corrupted while reading record: "-1 of 2057". Possible solution: use the recovery tool; SQL statement:
CREATE PRIMARY KEY PUBLIC.PRIMARY_KEY_A ON PUBLIC.VM(ID) [90030-147]
Cause
Resolution
To resolve this issue, you need to recreate the H2 database.
To recreate the H2 database:
- Stop the VMware Management Webservices service. For more information, see Stopping, starting, or restarting vCenter services (1003895).
- Navigate to the VMware\Infrastructure\tomcat\webapps\sms\WEB-INF\classes\com\vmware\vim\sms\data folder.
- Delete all sms-cache*.* files.
- Restart the VMware Management Webservices service.
The H2 database is now recreated.
See Also
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.
Actions
KB:
- Updated:
- Categories:
- Languages:
- Product Family:
- Product(s):
- Product Version(s):

