HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Error accessing database
Server Management - Systems Insight Manager
1836382
Members
3256
Online
110100
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2007 02:56 AM
08-17-2007 02:56 AM
Error accessing database
Hi -
We have an upgraded HP-SIM 5.1 with hundreds of nodes that has been working fine for a long time.
We upgraded a different application on the same server that uses its own instance of SQL (not the same SQL used by HP-SIM).
However after the work on the other application, HP-SIM is broke. You can't open the console and the error shown below is found in the applicaiton log.
Have reviewed all related forum posts, run
'mxpassword -g', checked all the database.* files in the config folder, etc. no joy.
Suggestions apprecited, thanks,
John
com.hp.mx.database.DbVerificationException: Error loading database verification handler 'com.hp.mx.database.MsSqlVerificationHandler'
com.hp.mx.database.DbVerificationException: Error accessing database
We have an upgraded HP-SIM 5.1 with hundreds of nodes that has been working fine for a long time.
We upgraded a different application on the same server that uses its own instance of SQL (not the same SQL used by HP-SIM).
However after the work on the other application, HP-SIM is broke. You can't open the console and the error shown below is found in the applicaiton log.
Have reviewed all related forum posts, run
'mxpassword -g', checked all the database.* files in the config folder, etc. no joy.
Suggestions apprecited, thanks,
John
com.hp.mx.database.DbVerificationException: Error loading database verification handler 'com.hp.mx.database.MsSqlVerificationHandler'
com.hp.mx.database.DbVerificationException: Error accessing database
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2007 11:43 AM
08-17-2007 11:43 AM
Re: Error accessing database
Hello John,
Check:
1) If you have SQL Server installed locally, verify that it is running. If it is not running verify the logon
credentials. The service login credentials could have changed. The HP SIM service is registered to run under
the credentials used during installation. To resolve this issue:
A. Change the MSSQL service password:
* In Windows, open Services (Start>Control Panel>Services).
* Locate the MSSQL service (SQLserver service for SQL2005) and select Properties.
* Select the Logon tab, and change the password.
* Restart the MSSQL (or SQLserver) service.
B. Change the HP SIM service password:
* In Windows, open Services (Start>Control Panel>Services).
* Locate the HP SIM service, and select Properties.
* Select the Logon tab, and change the password.
* Restart the HP SIM service.
C. If you are using OpenSSH on Windows Server 2000 or 2003, change the OpenSSH Server service
password:
* In Windows, open Services (Start>Control Panel>Services).
* Locate the OpenSSH Server service, and select Properties.
* Select the Logon tab, and change the password.
* Restart the OpenSSH and HP SIM service.
2) TCP/IP is disabled in SQL 2005 by default. To enable TCP/IP:
a. Click Start>Microsoft SQL Server 2005 >Configuration Tools> SQL Server Configuration Manager. The SQL Server Configuration Manager window appears.
b. Select SQL Server 2005 Network Configuration from the left pane. The protocols will be displayed on the right frame.
c. Right click TCP/IP and select Enable.
d. Restart SQL server to reflect the changes.
**************
1. Stop HP SIM.
2. Access the Services control panel and edit the service credentials to provide the new password for
the HP Systems Insight Manager service.
3. Run mxpassword -g and modify the following password:
MxHPSIMServicePassword
4. Restart HP SIM.
**************
1. Stop HP SIM.
2. Run mxpassword -g and modify the following passwords to the new account password:
MxDBUserPassword
MxPMPPassword
3. Restart HP SIM.
**************
1) Verify that the target Microsoft SQL Server service (MSSQL) is running (select Control
Panel>Services>MSSQLSERVER). For SQL Server 2005, servicename will be "SQLServer."
Regards,
James.
Check:
1) If you have SQL Server installed locally, verify that it is running. If it is not running verify the logon
credentials. The service login credentials could have changed. The HP SIM service is registered to run under
the credentials used during installation. To resolve this issue:
A. Change the MSSQL service password:
* In Windows, open Services (Start>Control Panel>Services).
* Locate the MSSQL service (SQLserver service for SQL2005) and select Properties.
* Select the Logon tab, and change the password.
* Restart the MSSQL (or SQLserver) service.
B. Change the HP SIM service password:
* In Windows, open Services (Start>Control Panel>Services).
* Locate the HP SIM service, and select Properties.
* Select the Logon tab, and change the password.
* Restart the HP SIM service.
C. If you are using OpenSSH on Windows Server 2000 or 2003, change the OpenSSH Server service
password:
* In Windows, open Services (Start>Control Panel>Services).
* Locate the OpenSSH Server service, and select Properties.
* Select the Logon tab, and change the password.
* Restart the OpenSSH and HP SIM service.
2) TCP/IP is disabled in SQL 2005 by default. To enable TCP/IP:
a. Click Start>Microsoft SQL Server 2005 >Configuration Tools> SQL Server Configuration Manager. The SQL Server Configuration Manager window appears.
b. Select SQL Server 2005 Network Configuration from the left pane. The protocols will be displayed on the right frame.
c. Right click TCP/IP and select Enable.
d. Restart SQL server to reflect the changes.
**************
1. Stop HP SIM.
2. Access the Services control panel and edit the service credentials to provide the new password for
the HP Systems Insight Manager service.
3. Run mxpassword -g and modify the following password:
MxHPSIMServicePassword
4. Restart HP SIM.
**************
1. Stop HP SIM.
2. Run mxpassword -g and modify the following passwords to the new account password:
MxDBUserPassword
MxPMPPassword
3. Restart HP SIM.
**************
1) Verify that the target Microsoft SQL Server service (MSSQL) is running (select Control
Panel>Services>MSSQLSERVER). For SQL Server 2005, servicename will be "SQLServer."
Regards,
James.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2007 12:45 PM
08-18-2007 12:45 PM
Re: Error accessing database
James - thank you for the good suggestions, however all of those were checked OK before I posted. None of the posted fixes so far in this forum work in this case. I was hoping someone had more in-depth knowledge on this error that could suggest some means to fix it other than what has already been posted in this forum.
Again, I do thank you for your reply.
Again, I do thank you for your reply.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP