DRAFT: version 1.0 Jump to content English
hp.com home
HP Systems Insight Manager  |  Troubleshooting  |  SQL and MSDE Problems

Troubleshooting
SQL and MSDE Problems

» HP Systems Insight Manager

»Table of Contents
»Index
»Product Overview
»Getting Started
»Monitoring Systems, Events, and Clusters
»Using Tasks
»Using Default Tools
»Reporting
»Administering the Software
»Troubleshooting
»HP Systems Insight Manager Problems
»Installation Problems
»Login Problems
»Microsoft Internet Explorer Problems
»Security Problems
»IP Address Problems
»System, Cluster, and Event Problems
»Operating System Problems
SQL and MSDE Problems
»Agent Problems
»Command Line Interface Problems
»CMS Problems
»Tool Problems
»List Problems
»Task Problems
»Reporting Problems
»Log Problems
»Windows Event Log
»Miscellaneous Problems
»Service and Support
»Glossary
»Using Help
Content starts here
» MSDE Problems
» SQL Problems

MSDE Problems

The system running SQL Server or MSDE system names needs to be changed.

Solution: If you need to change the computer name of the system where SQL Server or MSDE is running, you will need to perform some additional steps on the system where HP Systems Insight Manager is running.

On a Windows sytem:

  1. Stop the HP Systems Insight Manager Service in the Control Panel Services applet.

  2. Once the service is stopped, open the Control Panel and select the ODBC icon.

  3. Change to the System DSN tab. Select the Insight_DB_V3 entry and change the name of the computer running SQL Server/MSDE to match the new computer name.

  4. Change to the directory in which HP Systems Insight Manager is installed. (The default folder is c:\Program Files\HP\HP Systems Insight Manager\.)

  5. Change to the CONFIG directory.

  6. Find the file named DATABASESETTINGS.PROPS, a text file. Edit the entry in this file that contains the old name of the system running SQL Server/MSDE and change it to the new name.

  7. Restart the HP Systems Insight Manager service.

On an HP-UX system:

  1. Please check PostgreSQL version, Nimbus will support PostgreSQL 7.2.* and 7.3.* version.

  2. Look at /var/opt/mx/logs/PgSQL_Config.log to see if there is any error during database configuration.

  3. Use nslookup localhost to make sure that localhost can be resolved correctly.

  4. Run ps -ef | grep post to see if there is any PostgreSQL daemon.

    If there is any PostgreSQL daemon, then run /sbin/init.d/postgresql stop to stop. After that, run ps -ef | grep post again. If PostgreSQL daemon was not stopped, then we find the problem.

    Sometimes PostgreSQL daemons will not work correctly. So HP Systems Insight Manager cannot use it. In this case, use kill to kill all PostgreSQL daemons, and this may correct the problem.

  5. Run /sbin/init.d/postgresql start/stop to make sure that PostgreSQL can be started/stopped successfully. Please also check ps -ef | grep post to see if real daemons are stopped/started.

    If you have error such as An old version of the database format was found. It may because you installed another version of PostgreSQL without removing the old database files. Run next step with "-F" option, it may correct the problem.

  6. Run /opt/mx/lbin/mxconfigrepo -a [-F] to configure PostgreSQL again.

    [-F] option will remove all database files and recreate them. All PostgreSQL DB data will be lost.

    [-F] option is suggested to use when you change PostgreSQL version on the system, or some database files are corrupted.

  7. If you are still having problems, please check the content of /var/opt/iexpress/postgresql/pg_hba.conf and PostgreSQL version to see if it's consistent.

  8. If you are still having problems, contact your administrator for help

SQL Problems

HP Systems Insight Manager cannot establish a connection to the SQL database.

Solution: Click Control Panel—>ODBC to verify that the System DSN from insight_db_V3 is set and referencing the correct SQL Server. Verify, that the SQL Enterprise Manager and the database insight_db_V3 exist.

HP Systems Insight Manager no longer responds to browser requests because of a lost connection with the SQL Server database.

Solution: Verify that HP Systems Insight Manager has indeed lost database connectivity by checking the NT Event Log. Click Start—>Programs—>Administrative Tools—>Event Log and select Application Log. If you see error messages produced by HP Systems Insight Manager that relates to lost database connection, then this is the reason for non-response problem. Lost SQL database connectivity can be due to either (1) the SQL server is stopped, or (2) a cable disconnect has occurred with the SQL server. HP Systems Insight Manager service has a built-in Auto-Restart feature that will continuously attempt to restart the HP Systems Insight Manager application. To solve the non-response problem, simply either restart the SQL server or reestablish the SQL server connection. Within several minutes, the HP Systems Insight Manager application will restart and the SQL server connection will be reestablished.

Stopping Microsoft SQL server while a system is being deleted does not stop the system from being deleted.

Solution: Due to the way the database is designed, HP Systems Insight Manager cannot roll back in the middle of an operation. Everything committed to the database will be completed by the database (for example, deleting systems, deleting events, and so on.).

After creating a user with administrator rights the user name is shown in the user list generated from the SQL Analyzer. However, after editing the UserID file, exiting HP Systems Insight Manager and restarting HP Systems Insight Manager, the user is not listed when clicking Settings—>Accounts; although, the user name is listed in the database.

Solution: Any attempt to manually modify the "users" database table or any user information hash file, will cause the user account to be removed from HP Systems Insight Manager. If this happens, the user can no longer access HP Systems Insight Manager.