Server Management - Systems Insight Manager
cancel
Showing results for 
Search instead for 
Did you mean: 

problem upgrading from 5.0sp4 to 5.1

problem upgrading from 5.0sp4 to 5.1

hi everybody,

when upgrading HPSIM I got the following error after the setup copied the HPSIM-files and while populating the database:
"database initialization failed, connection to repository server failed"
after that the user account we use is locked out. But all credential checkin before was correct and of course I'm sure that I used the correct pw.
Whats going on here ???
55 REPLIES
Ole Thomsen_1
Trusted Contributor

Re: problem upgrading from 5.0sp4 to 5.1

I had the exact same error, this is what I did:

- Unlock the user :-)
- Run the installer again to finish setup
- Reboot server
- Run "mxinitconfig -a" to repair HPSIM installation

After that things seem to be fine, have minor issues that I will take a closer look at later...

Ole Thomsen
SEBEMISMNUSA
Frequent Advisor

Re: problem upgrading from 5.0sp4 to 5.1

With a HPSIM 5.0 sp # 5 to HP SIM 5.1 upgrade, I had the exact same situation.
The GUI dialog box stated

Database initialization failed. Setup cannot continue
Error:
1) Connection to the repository server failed.
Please refer to the initconfig.log in the
c:\progra~1\hp\system~1\config directory for more information.

1. I, too, unlocked the account
(Microsoft Active directory, account was definitely locked; I, too had entered the correct password.

2. Reran the setup to complete the HP SIM 5.1 installation.

3. Rebooted this computer.

4. Ran this command
C:\Program Files\HP\Systems Insight Manager> mxinitconfig -a
which is now running.
Checking Requisites (13):
1. Server Property File ..OK
2. Server Authentication Keys ..OK
3. SSH Keys ..OK
4. Status Property File ..OK
5. Task Results Output Cleanup ..OK
6. Database Configuration ..OK
7. Database Content ..OK
8. Web Server ..OK
9. Setup Property File ..OK
10. JBoss Setup ..OK
11. Agent Configuration ..OK
12. Management Services ..OK
13. Initialization and Database Population ..OK
Requisite scan completed successfully.

Configuring Server Components (13):
1. Server Property File ..Done
2. Server Authentication Keys ..Done
3. SSH Keys ..Done
4. Status Property File ..Done
5. Task Results Output Cleanup ..Done
6. Database Configuration ..19 Jan 2007 18:29:29,892 INFO [HPSIM_DEBUG]
Database Version:
19 Jan 2007 18:29:29,939 INFO [HPSIM_DEBUG]
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

19 Jan 2007 18:29:30,111 INFO [HPSIM_DEBUG]
Database Driver:
jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.0.2

19 Jan 2007 18:29:30,470 INFO [HPSIM_DEBUG]
Database Version:
19 Jan 2007 18:29:30,501 INFO [HPSIM_DEBUG]
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

19 Jan 2007 18:29:30,673 INFO [HPSIM_DEBUG]
Database Driver:
jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.0.2

Done
7. Database Content ..Done
8. Web Server ..Done
9. Setup Property File ..Done
10. JBoss Setup ..Done
11. Agent Configuration ..Done
12. Management Services ..Done
13. Initialization and Database Population ..
13. Initialization and Database Population ....
- Start initialization .........................................................
lots and lots of dots

I will post the results later.

End
SEBEMISMNUSA
Frequent Advisor

Re: problem upgrading from 5.0sp4 to 5.1

The HP SIM computer, a HP Proliant DL360 G3 with 2.4 GHz processors, 4GB ram, mirrored disks (RAID 1) has been running the mxinitconfig -a command since Friday, January 19 at 7 PM until last check at 11 AM Sunday, January 21. The command is still running. There are numerous dots . . . .
The mxpassword task is using processor time. The mxinitconfig task is in the task list.
There are seven hundred computer servers monitored with HPSIM. One thousand clients have been found. Seven hundred fifty printers have been found.

What is going on here?? I have previous HP SIM updates take hours for various sections to complete.
This is taking days, with no apparent end in sight.

End (of this posting) but no my HP SIM upgrade from HP SIM 5.0 sp # 5 (or may be 4) to HP SIM 5.1


SEBEMISMNUSA
Frequent Advisor

Re: problem upgrading from 5.0sp4 to 5.1

This is from my initconfig.log file on Friday, January 19, 2007.
Note: What a wonderful way to spend a weekend. Thank you, HP.

It shows the upgrade from HP SIM 5.0 sp # 5 to HP SIM 5.1 Upgrade From Version = C.05.00.02.00 To Version = C.05.01.00.00
failing at step 6 at 5:30 PM 1/19/2007
Per the previous postings, I rebooted the computer, reran the installation at 6:30 PM 1/1/19/2007

5:30 PM failure
6. Database Configuration
Connecting to database ..
RROR - Connection to the repository server failed. ..Failed
Exception :Configuration failed to complete due to the following exception:
Connection to the repository server failed.

========== Begin Initial Configuration Record ==========
-------------- Operation = Configure
-------------- Upgrade From Version = C.05.00.02.00
-------------- To Version = C.05.01.00.00
-------------- Date = Friday, January 19, 2007 5:32:06 PM CST
-------------- User =
-------------- Host =
-------------- Locale = English (United States)
-------------- Operating System = Windows 2003
-------------- Database Type = MSSQL

Configuring Server Components (13):
1. Server Property File
..Done
2. Server Authentication Keys
..Done
3. SSH Keys
..Done
4. Status Property File
..Done
5. Task Results Output Cleanup
..Done
6. Database Configuration
Connecting to database ..
ERROR - Connection to the repository server failed.
..Failed
Exception :Configuration failed to complete due to the following exception:
Connection to the repository server failed.
Completed with error.

Details can be found in the log files at: E:\Data\HPSIMLogs

-------------- Date = Friday, January 19, 2007 5:32:17 PM CST
-------------- Operation = Configure
========== End Initial Configuration Record ==========

Re-ran setup to complete the installation at 6:30 PM 1/19/2007

========== Begin Initial Configuration Record ==========
-------------- Operation = Configure
-------------- Upgrade From Version = C.05.00.02.00
-------------- To Version = C.05.01.00.00
-------------- Date = Friday, January 19, 2007 6:29:27 PM CST
-------------- User =
-------------- Host =
-------------- Locale = English (United States)
-------------- Operating System = Windows 2003
-------------- Database Type = MSSQL
Checking Requisites (13):
1. Server Property File
..OK
2. Server Authentication Keys
..OK
3. SSH Keys
..OK
4. Status Property File
..OK
5. Task Results Output Cleanup
..OK
6. Database Configuration
..OK
7. Database Content
..OK
8. Web Server
..OK
9. Setup Property File
..OK
10. JBoss Setup
..OK
11. Agent Configuration
..OK
12. Management Services
..OK
13. Initialization and Database Population
..OK
Requisite scan completed successfully.

Configuring Server Components (13):
1. Server Property File
..Done
2. Server Authentication Keys
..Done
3. SSH Keys
..Done
4. Status Property File
..Done
5. Task Results Output Cleanup
..Done
6. Database Configuration
Connecting to database ..
Updating schema 'schema50_51.sql' ..
Creating view 'schema40.sql' ..
Creating view 'DCSchema10.sql' ..
Creating view 'schema40_41.sql' ..
Creating view 'schema41_42.sql' ..
Creating view 'schema42_50.sql' ..
Creating view 'schema50_51.sql' ..
..Done
7. Database Content
Copied to remove directory:C:\Program Files\HP\Systems Insight Manager\remove\parmgr-web-tools.xml
Copied to remove directory:C:\Program Files\HP\Systems Insight Manager\remove\OldSGToolToRemove.xml
Copied to remove directory:C:\Program Files\HP\Systems Insight Manager\remove\svguardview.xml
Copied to remove directory:C:\Program Files\HP\Systems Insight Manager\remove\LicenseManager.xml
Copied to remove directory:C:\Program Files\HP\Systems Insight Manager\remove\remove-tool.xml
Copied to remove directory:C:\Program Files\HP\Systems Insight Manager\remove\swm-ssa-tools-up.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\automationtools.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\bladeimeVersion.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\clustermonitor.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\CWDetailPage.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\dcreport.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\deviceping.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\ems-tools.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\enclosureview.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\ilo-wsman-tools.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\managementurl.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\MpTools.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\mx-tools.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\oa-tools.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\openssh-install.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\pmptools.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\powermgrVersion.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\powerregulator.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\prm-tools.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\proliant-msa-tools.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\property-pages-tools.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\rackview.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\repair-tools.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\rpm-update-tools.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\sam-tools.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\smptools.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\swm-ssa-tools.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\systempage.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\systempageevent.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\vmmAgenttools.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\vmmAgenttools_l.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\vmmcollection.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\vmmqueries.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\vmmqueriesAddAfterSubtypeInit.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\vmmReg.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\vmmReg_l.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\vmmSMP.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\vmmtools.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\vmmtools21.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\vmmtools_l.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\vmmUpgrade.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\wbemsubscriptions.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\webmin.xml
Copied to tools directory:C:\Program Files\HP\Systems Insight Manager\setup\wlsysprotocolsetting.xml
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\AlertCategoryEnums.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\AlertCategoryEnums_ja.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\AlertTypeEnum.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\AlertTypeEnum_ja.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\IPMAlertTypeEnum.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\IPMAlertTypeEnum_ja.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\ListColumnHeaderStrings.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\ListColumnHeaderStrings_ja.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\ListCriteriaNames.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\ListCriteriaNames_ja.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\NodeSubTypeEnums.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\NodeSubTypeEnums_ja.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\NodeTypeEnums.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\NodeTypeEnums_ja.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\NodeUrlTypes.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\NodeUrlTypes_ja.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\ServiceEventStates.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\ServiceEventStates_ja.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\AggrEventStatusSourceReg.xml
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\SampleStatusSourceReg.xml
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\AggrEventStatusSourceReg.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\AggrEventStatusSourceReg_ja.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\CWStatusSourceReg.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\CWStatusSourceReg_ja.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\StatusSourceReg.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\StatusSourceReg_ja.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\deloldeventsquery.xml
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\deloldeventstask.xml
Directory for initial object creation not found:C:\Program Files\HP\Systems Insight Manager\config\preload\51\removefiles
Directory for initial object creation not found:C:\Program Files\HP\Systems Insight Manager\config\preload\51\updatefiles
CRITERIA XML DIR IS C:\Program Files\HP\Systems Insight Manager\config\criteria
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\DirectoryGroupCriteria.xml
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\DirectoryGroupCriteria.properties
Copied xml resource file to startup directory:C:\Program Files\HP\Systems Insight Manager\setup\DirectoryGroupCriteria_ja.properties
..Done
8. Web Server
..Done
9. Setup Property File
..Done
10. JBoss Setup
..Done
11. Agent Configuration
..Done
12. Management Services
..Done
13. Initialization and Database Population

HP Systems Insight Manager Initialization Starts at: Friday, January 19, 2007 6:30:46 PM CST
- Start initialization

From the log file
@!@,2007-01-19 18:30:17 CST,APPLICATION,FAILURE,START,CMS,ERROR: TABLE trapData KEY notice_id may contain 14 entrie(s) not in table notices KEY noticeId,ERROR,as071009\mxadmin,,,
ERROR: TABLE trapData KEY notice_id may contain 14 entrie(s) not in table notices KEY noticeId
@!@,2007-01-19 18:30:17 CST,APPLICATION,FAILURE,START,CMS,ERROR: TABLE trapVarbindData KEY trap_rec_id may contain 1 entrie(s) not in table trapData KEY rec_id,ERROR,as071009\mxadmin,,,
ERROR: TABLE trapVarbindData KEY trap_rec_id may contain 1 entrie(s) not in table trapData KEY rec_id
@!@,2007-01-19 18:30:17 CST,APPLICATION,FAILURE,START,CMS,ERROR: TABLE SecurityNoticesData KEY noticeId may contain 27569 entrie(s) not in table notices KEY noticeId,ERROR,as071009\mxadmin,,,
ERROR: TABLE SecurityNoticesData KEY noticeId may contain 27569 entrie(s) not in table notices KEY noticeId
@!@,2007-01-19 18:30:17 CST,APPLICATION,FAILURE,START,CMS,Pass 1,ERROR,as071009\mxadmin,,,
Pass 1
@!@,2007-01-19 18:30:17 CST,APPLICATION,FAILURE,START,CMS,14 entries fixed in TABLE trapData,ERROR,as071009\mxadmin,,,
14 entries fixed in TABLE trapData
@!@,2007-01-19 18:30:17 CST,APPLICATION,FAILURE,START,CMS,7 entries fixed in TABLE trapVarbindData,ERROR,as071009\mxadmin,,,
7 entries fixed in TABLE trapVarbindData
@!@,2007-01-19 18:30:17 CST,APPLICATION,FAILURE,START,CMS,27569 entries fixed in TABLE SecurityNoticesData,ERROR,as071009\mxadmin,,,
27569 entries fixed in TABLE SecurityNoticesData


From the mxdomainmgr log file, showing the HP SIM startup failing at 6:30 PM. This is before the mxinitconfig - a is run.

End

SEBEMISMNUSA
Frequent Advisor

Re: problem upgrading from 5.0sp4 to 5.1

How to ruin a nice weekend - upgrade to HP SIM 5.1 from HP SIM 5.0 SP # 5
The days running mxinitconfig -a still did not complete. The computer effectively stopped working. Network shares were not available. Simple programs such as notepad would not run on the HP SIM computer. I was trying to check the log files for status messages.

Here is the result of another try to get HP SIM 5.1 working.

1. Reboot the computer
2. Run mxinintconfig -l
Database is still not configured.
13. Initialization and Database Population ..OK
Status : Unconfigured

3. Stop the HP SIM service.
4. Run the mxinitconfig -a command again.
Hope this installation of HP SIM is not destroyed.
13. Initialization and Database Population .... - Start initialization ......................

Details:
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\>mxinitconfig -l
Listing current status of server components (13):
1. Server Property File ..OK
Status : Configured
2. Server Authentication Keys ..OK
Status : Configured
3. SSH Keys ..OK
Status : Configured
4. Status Property File ..OK
Status : Configured
5. Task Results Output Cleanup ..OK
Status : Configured
6. Database Configuration ..OK
21 Jan 2007 13:03:25,875 INFO [HPSIM_DEBUG]
Database Version:
21 Jan 2007 13:03:25,890 INFO [HPSIM_DEBUG]
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

21 Jan 2007 13:03:25,906 INFO [HPSIM_DEBUG]
Database Driver:
jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.0.2

Status : Configured
7. Database Content ..OK
Status : Configured
8. Web Server ..OK
Status : Configured
9. Setup Property File ..OK
Status : Configured
10. JBoss Setup ..OK
Status : Unconfigured
11. Agent Configuration ..OK
Status : Unconfigured
12. Management Services ..OK
Status : Configured
13. Initialization and Database Population ..OK
Status : Unconfigured
Completed all tasks successfully.

Details can be found in the log files at: E:\Data\HPSIMLogs

C:\Documents and Settings\App-098-HPInsightSQL>mxinitconfig -l
Listing current status of server components (13):
1. Server Property File ..OK
Status : Configured
2. Server Authentication Keys ..OK
Status : Configured
3. SSH Keys ..OK
Status : Configured
4. Status Property File ..OK
Status : Configured
5. Task Results Output Cleanup ..OK
Status : Configured
6. Database Configuration ..OK
21 Jan 2007 13:13:20,605 INFO [HPSIM_DEBUG]
Database Version:
21 Jan 2007 13:13:20,636 INFO [HPSIM_DEBUG]
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

21 Jan 2007 13:13:20,683 INFO [HPSIM_DEBUG]
Database Driver:
jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.0.2

Status : Configured
7. Database Content ..OK
Status : Configured
8. Web Server ..OK
Status : Configured
9. Setup Property File ..OK
Status : Configured
10. JBoss Setup ..OK
Status : Unconfigured
11. Agent Configuration ..OK
Status : Unconfigured
12. Management Services ..OK
Status : Configured
13. Initialization and Database Population ..OK
Status : Unconfigured
Completed all tasks successfully.

Details can be found in the log files at: E:\Data\HPSIMLogs

C:\Documents and Settings\App-098-HPInsightSQL>
C:\Documents and Settings\App-098-HPInsightSQL>mxinitconfig -a
Checking Requisites (13):
1. Server Property File ..OK
2. Server Authentication Keys ..OK
3. SSH Keys ..OK
4. Status Property File ..OK
5. Task Results Output Cleanup ..OK
6. Database Configuration ..OK
7. Database Content ..OK
8. Web Server ..OK
9. Setup Property File ..OK
10. JBoss Setup ..OK
11. Agent Configuration ..OK
12. Management Services ..OK
13. Initialization and Database Population ..OK
Requisite scan completed successfully.

Configuring Server Components (13):
1. Server Property File ..Done
2. Server Authentication Keys ..Done
3. SSH Keys ..Done
4. Status Property File ..Done
5. Task Results Output Cleanup ..Done
6. Database Configuration ..21 Jan 2007 13:14:45,308 INFO [HPSIM_DEBUG]
Database Version:
21 Jan 2007 13:14:45,324 INFO [HPSIM_DEBUG]
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

21 Jan 2007 13:14:45,371 INFO [HPSIM_DEBUG]
Database Driver:
jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.0.2

21 Jan 2007 13:14:45,543 INFO [HPSIM_DEBUG]
Database Version:
21 Jan 2007 13:14:45,558 INFO [HPSIM_DEBUG]
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

21 Jan 2007 13:14:45,605 INFO [HPSIM_DEBUG]
Database Driver:
jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.0.2

Done
7. Database Content ..Done
8. Web Server ..Done
9. Setup Property File ..Done
10. JBoss Setup ..Done
11. Agent Configuration ..Done
12. Management Services ..Done
13. Initialization and Database Population ....
- Start initialization ......................

End
Sean Murray_1
Regular Advisor

Re: problem upgrading from 5.0sp4 to 5.1

Good luck. I ran the update last week.
Now my existing database is hosed.
Created a new one on install of course, but I tried to repoint to the old database like I did after last release.
Lots of erros in event log pertaining to table errors, entry error, etc all with the HP SIM Service.
Appears to run and have login screen in browser but will not accept any login acct.

So, now I have to redo it all.

SEBEMISMNUSA
Frequent Advisor

Re: problem upgrading from 5.0sp4 to 5.1

I am still attempting to get HP SIM 5.1 online. I had to restart the mxinitconfig -a command on Sunday, January 21, around 1 PM CST USA. The mxinitconfig is still running as of 11:30 PM 1/21, with the seeminly endless . . . . . . . .

On Sunday morning, 1/21, applications like notepad stopped working on this computer. The network shares like C$ quit working. I only wanted to check the HP SIM log files - to see what was going on. I could not. I rebooted this computer and started again.

How such a seemingly simple update from HP SIM 5.0 sp # 5 to HP SIM 5.1 can get so quickly fouled up is beyone me?

As some of my log files indicated, this is a plain vanilla installation.

As a side note, the same database file is retained. I checked with Microsoft SQL enterprise manager. The same database is used after the HP SIM 5.1 installation was for the HP SIM 5.0 sp #5.

I normally do *not* update when HP releases any HP SIM software. I just need the 7.6 MIB. Others had indicated the 7.6 MIB installation did not work with HP SIM 5.0 sp # x (more software defects).
With HP SIM 5.0 sp # 4 and sp # 5, there is also a severe defect in servers going as unknown after during and after a discovery. I was hoping the severe defect was fixed. I may never know.

Why does HP do this to its customers?
This is the continuing tradition of releasing software with too many defects.

One very angry customer :(

End

OlivierV
Trusted Contributor

Re: problem upgrading from 5.0sp4 to 5.1

Last time I upgraded my HP SIM server (from 4.2 to 5.0), I had to reinit the DB because the data inventory was unavailable. 5 hours to import the devices, recreate the groups, event tasks ...
Since HP SIM 5.1 is released, I don't see any message saying the upgrade went fine. HP is waiting for us to debug the application.
It will take some time before I upgrade my test CMS server, and even more my production one.

Re: problem upgrading from 5.0sp4 to 5.1

sorry for answering so late, here's what i did:

- after the upgrade failed, I de-installed HPSIM
- then I did a new install with v5.1
- I exported the machine names from the v5.0 DB and added them with mxnode in the the new one.
- All other settings I changed from hand

Thanks HP
SEBEMISMNUSA
Frequent Advisor

Re: problem upgrading from 5.0sp4 to 5.1

Summary: Be very careful if you upgrade an existing HP SIM 5.0 sp # x system to HP SIM 5.1.

My recommendation (if you have this luxury)
Create a complete separate HP SIM system (yes, another Proliant computer). Install HP SIM 5.1 on it; migrate your data from the HP SIM 5.0 system to the HP SIM 5.1

Or you may have my experience of struggling to get to a HP SIM 5.1 monitoring system back online. I thought, as most, this would take several hours.

I am doing what I can to get the mxinitconfig -a to work. Hopefully others will benefit from my postings. I have spend hours in the struggle.

Second mx fix attempt
1/21/07 2:30 PM - 1/22/07 10:45 AM still running, the dot generator
HP Systems Insight Manager Initialization Starts at: Sunday, January 21, 2007 2:30:33 PM CST
- Start initialization ..Done
11. Agent Configuration
..Done
12. Management Services
..Done
13. Initialization and Database Population

HP Systems Insight Manager Initialization Starts at: Sunday, January 21, 2007 2:30:33 PM CST
- Start initialization


First mx fix attempt
Friday, January 19 6:30 PM
died or stopped at about Sunday, January 21 at about 1:00 PM
Computer has malfunctions (ex. notepad would not work, networks shares stopped working, ex. C$)

========== Begin Initial Configuration Record ==========
-------------- Operation = Configure
-------------- Upgrade From Version = C.05.00.02.00
-------------- To Version = C.05.01.00.00
-------------- Date = Friday, January 19, 2007 6:29:27 PM CST
-------------- User =
-------------- Host =
-------------- Locale = English (United States)
-------------- Operating System = Windows 2003
-------------- Database Type = MSSQL

End
CA1499584
Regular Advisor

Re: problem upgrading from 5.0sp4 to 5.1

I have done that too, I installed from scrach and the results are .... after finishing with no errors, I can't get to any page after login in, (Page not found) No working at all for me, going back to 5.0 , HP when we can have this solve ?
NJK-Work
Honored Contributor

Re: problem upgrading from 5.0sp4 to 5.1

I guess I am one of the lucky ones...sorry to hear about all the problems people are having.

The one piece of advice I can give, and its a bit pricey, is to image up the SIM server prior to the upgrade. I use Acronis TrueImage Server. I create an image of the server prior to the upgrade, which took about 1 hour because of the size, and then run the upgrade. If it blows up - restore the image. I actually had to do this for one of the pevious SPs - I think it was SP4. The upgrade blew up and I had to restore my image. I was back and running in about 1 hour.

But I understand not everyone has the luxury of throwing $700.00 at a server. There may be cheaper imaging products out there.

Nelson
SEBEMISMNUSA
Frequent Advisor

Re: problem upgrading from 5.0sp4 to 5.1

I gave up with the struggling.
I removed HP SIM 5.1. I re-installed HP SIM 5.0 sp # 5. It is operational again. The database was not destroyed in my upgrade attempt. With some database work, sp_detach and sp_attach commands, I was able to connect the HP SIM database back.

This is where I am at now.
Central management server:
Hostname:
Operating system: Windows 2003
Version: Systems Insight Manager 5.0 with SP5 - Windows
Build version: C.05.00.02.00
Build date: 2006-05-23 11:07
Hotfixes:
User name:

I only wished HP never put this update at their web site.

End
SEBEMISMNUSA
Frequent Advisor

Re: problem upgrading from 5.0sp4 to 5.1

An example (from the HPSIM.log) of an update failure from the HP SIM 5.0 SP # 5 to HP SIM 5.1
Attached are screen shots of what you might see if you attempt this.

[Mon Jan 22 18:34:03 CST 2007]Install Shell:Load: res://E:\Data\SOFTWARE\hpsim\hpsim51\SIM51-win\hpsim\win_ia32\setup.exe/content\custom-status.htm
[Mon Jan 22 18:34:03 CST 2007]Install Shell:window_onload()
[Mon Jan 22 18:34:03 CST 2007]Install Shell:InstallComponent()
[Mon Jan 22 18:34:03 CST 2007]Install Shell:RunComponentInstall(fnInstall[function] nIndex[3])
[Mon Jan 22 18:34:03 CST 2007]Install Shell:launchAndMonitor dwRet == 0
[Mon Jan 22 18:34:03 CST 2007]Install Shell:component install Initial Start return code == 0
[Mon Jan 22 18:34:03 CST 2007]Install Shell:window_onload()
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:ValidPrerequisites()
[01-22-2007][18:34:10][HP Systems Insight Manager]Startup.
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:ValidTCPIP()
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:ValidSNMP()
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:ValidScreenRes()
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:IsIM7Installed()
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:IsTopToolsInstalled()
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:ValidMDAC()
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:InitializeSetup - valid pre-reqs
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:gsFullDNS = COMPUTER-NAME
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:GetInstallType()
[01-22-2007][18:34:10][HP Systems Insight Manager]install upgrade
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:GetDBHost()
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:InitializeWizard()
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:CreateEdit()
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:CreateEdit()
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:CreateEdit()
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:CreateEdit()
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:CreateEdit()
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:CreateEdit()
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:CreateEdit()
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:CreateEdit()
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:CreateEdit()
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:CreateEdit()
[01-22-2007][18:34:10][HP Systems Insight Manager]DEBUG:LoadSQLValues()
[01-22-2007][18:34:37][HP Systems Insight Manager]DEBUG:NextButtonClick(1)
[01-22-2007][18:34:37][HP Systems Insight Manager]DEBUG:welcome page
[01-22-2007][18:34:40][HP Systems Insight Manager]DEBUG:ShouldSkipPage(100)
[01-22-2007][18:34:40][HP Systems Insight Manager]DEBUG:ShouldSkipPage(101)
[01-22-2007][18:34:40][HP Systems Insight Manager]DEBUG:ShouldSkipPage(6)
[01-22-2007][18:34:40][HP Systems Insight Manager]DEBUG:ShouldSkipPage(8)
[01-22-2007][18:34:40][HP Systems Insight Manager]DEBUG:UpdateReadyMemo()
[01-22-2007][18:34:40][HP Systems Insight Manager]DEBUG:ShouldSkipPage(10)
[01-22-2007][18:34:40][HP Systems Insight Manager]DEBUG:ShouldSkipPage(8)
[01-22-2007][18:34:40][HP Systems Insight Manager]DEBUG:ShouldSkipPage(6)
[01-22-2007][18:34:40][HP Systems Insight Manager]DEBUG:ShouldSkipPage(101)
[01-22-2007][18:34:40][HP Systems Insight Manager]DEBUG:ShouldSkipPage(100)
[01-22-2007][18:35:24][HP Systems Insight Manager]DEBUG:NextButtonClick(10)
[01-22-2007][18:35:24][HP Systems Insight Manager]DEBUG:CurStepChanged()
[01-22-2007][18:40:15][HP Systems Insight Manager]DEBUG:CurStepChanged()
[01-22-2007][18:40:15][HP Systems Insight Manager]DEBUG:CreateInitForm()
[01-22-2007][18:40:18][HP Systems Insight Manager]DEBUG:InitFrmOnShow
[01-22-2007][18:40:18][HP Systems Insight Manager]DEBUG:InitFrmBtnNotifyOnClick()
[01-22-2007][18:40:18][HP Systems Insight Manager]HP Systems Insight Manager installation completed.
[01-22-2007][18:40:18][HP Systems Insight Manager]DEBUG:fixFiles
[01-22-2007][18:40:19][HP Systems Insight Manager]DEBUG:SetDefaultUsers()
[01-22-2007][18:40:19][HP Systems Insight Manager]DEBUG:ReplaceValue()
[01-22-2007][18:40:19][HP Systems Insight Manager]DEBUG:ReplaceValue()
[01-22-2007][18:40:19][HP Systems Insight Manager]DEBUG:ReplaceValue()
[01-22-2007][18:40:19][HP Systems Insight Manager]DEBUG:SetOpenSSHUsers()
[01-22-2007][18:40:19][HP Systems Insight Manager]DEBUG:UpdateDatabaseTemplates()
[01-22-2007][18:40:19][HP Systems Insight Manager]DEBUG:ReplaceValue()
Database initialization failed for URL: jdbc:jtds:sqlserver://COMPUTER-NAME:1433/Insight_v50_0_173855153;domain=AD-domain;instance=HPSIM1;prepareSQL=3 Ex: java.sql.SQLException: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Database initialization failed for URL: jdbc:jtds:sqlserver://COMPUTER-NAME:1433/Insight_v50_0_173855153;domain=AD-domain;instance=HPSIM1;prepareSQL=3 Ex: java.sql.SQLException: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Database initialization failed for URL: jdbc:jtds:sqlserver://COMPUTER-NAME:1433/Insight_v50_0_173855153;domain=AD-domain;instance=HPSIM1;prepareSQL=3 Ex: java.sql.SQLException: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Database initialization failed for URL: jdbc:jtds:sqlserver://COMPUTER-NAME:1433/Insight_v50_0_173855153;domain=AD-domain;instance=HPSIM1;prepareSQL=3 Ex: java.sql.SQLException: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Database initialization failed for URL: jdbc:jtds:sqlserver://COMPUTER-NAME:1433/Insight_v50_0_173855153;domain=AD-domain;instance=HPSIM1;prepareSQL=3 Ex: java.sql.SQLException: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Database initialization failed for URL: jdbc:jtds:sqlserver://COMPUTER-NAME:1433/Insight_v50_0_173855153;domain=AD-domain;instance=HPSIM1;prepareSQL=3 Ex: java.sql.SQLException: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Database initialization failed for URL: jdbc:jtds:sqlserver://COMPUTER-NAME:1433/Insight_v50_0_173855153;domain=AD-domain;instance=HPSIM1;prepareSQL=3 Ex: java.sql.SQLException: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Database initialization failed for URL: jdbc:jtds:sqlserver://COMPUTER-NAME:1433/Insight_v50_0_173855153;domain=AD-domain;instance=HPSIM1;prepareSQL=3 Ex: java.sql.SQLException: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Database initialization failed for URL: jdbc:jtds:sqlserver://COMPUTER-NAME:1433/Insight_v50_0_173855153;domain=AD-domain;instance=HPSIM1;prepareSQL=3 Ex: java.sql.SQLException: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Database initialization failed for URL: jdbc:jtds:sqlserver://COMPUTER-NAME:1433/Insight_v50_0_173855153;domain=AD-domain;instance=HPSIM1;prepareSQL=3 Ex: java.sql.SQLException: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
HP Systems Insight Manager shutting down: com.hp.mx.database.DbVerificationException: Error loading database verification handler 'com.hp.mx.database.MsSqlVerificationHandler'
com.hp.mx.database.DbVerificationException: Error accessing database
Password Key "MxDBUserPassword" added


Please close this command window immediately to prevent any clear text passwords from being exposed to unintended eyes.
[01-22-2007][18:40:39][HP Systems Insight Manager]update HPSIM service
[01-22-2007][18:40:39][HP Systems Insight Manager]DEBUG:SetSNMPAccept()
[01-22-2007][18:40:39][HP Systems Insight Manager]DEBUG:AddSNMPHost()
[01-22-2007][18:40:39][HP Systems Insight Manager]DEBUG:AddSNMPHost()
[01-22-2007][18:40:39][HP Systems Insight Manager]DEBUG:mxinitconfig -a -F, C:\PROGRA~1\HP\SYSTEM~1, C:\hpsim.log, ,$, CMD_WAIT + CMD_CAPTURE, 590402

Configuring Server Components (13):
1. Server Property File ..Done
2. Server Authentication Keys ..Done
3. SSH Keys ..Done
4. Status Property File ..Done
5. Task Results Output Cleanup ..Done
6. Database Configuration ..Failed
Completed with error.

Details can be found in the log files at: C:\Program Files\HP\Systems Insight Manager\logs
Configuration failed to complete due to the following exception:
Connection to the repository server failed.
[01-22-2007][18:40:55][HP Systems Insight Manager]DEBUG:InitFrmBtnNotifyOnClick()
[01-22-2007][18:40:55][HP Systems Insight Manager]DEBUG:nProgress = 123
[01-22-2007][18:41:26][HP Systems Insight Manager]Error:Database initialization failed. Setup cannot continue.

Error:
1) Connection to the repository server failed.


Please refer to the initconfig.log file in the
"C:\PROGRA~1\HP\SYSTEM~1\config"
directory for more information.
[01-22-2007][18:41:30][HP Systems Insight Manager]DEBUG:ShouldSkipPage(14)
[01-22-2007][18:41:52][HP Systems Insight Manager]DEBUG:NextButtonClick(14)
[01-22-2007][18:41:52][HP Systems Insight Manager]DEBUG:CurStepChanged()
[01-22-2007][18:41:52][HP Systems Insight Manager]DEBUG:DeInitializeSetup()
[01-22-2007][18:41:52][HP Systems Insight Manager]Shutdown.
[Mon Jan 22 18:41:52 CST 2007]Install Shell:InstallComplete()
[Mon Jan 22 18:41:52 CST 2007]Install Shell:process exit code = 0
[Mon Jan 22 18:41:52 CST 2007]Install Shell:sStatus = Setup failed. Please refer to the C:\hpsim.log and C:\Program Files\HP\Systems Insight Manager\logs\initconfig.logfiles for details.
[Mon Jan 22 18:41:52 CST 2007]Install Shell:nStatus = 4
[01-22-2007][18:41:52][Install Shell]HP Systems Insight Manager
[01-22-2007][18:41:52][Install Shell]return code: 4
[01-22-2007][18:41:52][Install Shell]return msg: Setup failed. Please refer to the C:\hpsim.log and C:\Program Files\HP\Systems Insight Manager\logs\initconfig.logfiles for details.
[Mon Jan 22 18:41:52 CST 2007]Install Shell:InstallComplete(sStatus[Setup failed. Please refer to the C:\hpsim.log and C:\Program Files\HP\Systems Insight Manager\logs\initconfig.logfiles for details.] nStatus[4])
[Mon Jan 22 18:41:52 CST 2007]Install Shell:installComplete: sStatus = Setup failed. Please refer to the C:\hpsim.log and C:\Program Files\HP\Systems Insight Manager\logs\initconfig.logfiles for details. nStatus = 4
[Mon Jan 22 18:41:52 CST 2007]Install Shell:updateComponentStatus(sStatus[Setup failed. Please refer to the C:\hpsim.log and C:\Program Files\HP\Systems Insight Manager\logs\initconfig.logfiles for details.])
[Mon Jan 22 18:41:52 CST 2007]Install Shell:checkIfFailedInstallIsHPSIM()
[01-22-2007][18:41:55][Install Shell]HP Systems Insight Manager failed to install successfully. Setup cannot continue. Click "OK" to exit the installation.
[Mon Jan 22 18:41:55 CST 2007]Install Shell:HtmlFrame_QueryExit()
[Mon Jan 22 18:41:55 CST 2007]Install Shell:Cleanup()
[01-22-2007][18:41:55][Install Shell]Shutdown
[Mon Jan 22 18:41:55 CST 2007]Install Shell:window_onunload()
James Kennedy_5
Regular Advisor

Re: problem upgrading from 5.0sp4 to 5.1

I had the same issue during my upgrade and its toast. I can't seem to get anywhere, so i'm rebuilding the server from scratch.

Anyone know if there's a way to use the old SIM 5.0 SP5 database when installing SIM 5.1 brand new on a fresh server?
CA1499584
Regular Advisor

Re: problem upgrading from 5.0sp4 to 5.1

I don't beleive you can do or use old 5.0 #5 DB with 5.1 since the new one have new views and tables to it. You have to do like we did go back to 5.0#5 and wait for HP to fix the upgrade to 5.1,
SEBEMISMNUSA
Frequent Advisor

Re: problem upgrading from 5.0sp4 to 5.1

Yes, I agree. The update to HP SIM 5.1 from 5.0 sp # 5, at least with Microsoft Windows 2003 using Microsoft SQL server 2000
*DOES NOT WORK*.

Details for HP or your review.
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\>mxgetdbinfo
host=
port=1433
dbname=Insight_v50_0_173855153
user= dbtype=SQLServer

C:\>

C:\>mxinitconfig -l
Listing current status of server components (13):
1. Server Property File ..OK
Status : Configured
2. Server Authentication Keys ..OK
Status : Configured
3. SSH Keys ..OK
Status : Configured
4. Status Property File ..OK
Status : Configured
5. Task Results Output Cleanup ..OK
Status : Configured
6. Database Configuration ..OK
23 Jan 2007 09:53:04,783 INFO [HPSIM_DEBUG]
Database Version:
23 Jan 2007 09:53:04,798 INFO [HPSIM_DEBUG]
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

23 Jan 2007 09:53:04,955 INFO [HPSIM_DEBUG]
Database Driver:
jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.0.2

Status : Configured
7. Database Content ..OK
Status : Configured
8. Web Server ..OK
Status : Configured
9. Setup Property File ..OK
Status : Configured
10. JBoss Setup ..OK
Status : Unconfigured
11. Agent Configuration ..OK
Status : Unconfigured
12. Management Services ..OK
Status : Configured
13. Initialization and Database Population ..OK
Status : Unconfigured
Completed all tasks successfully.

Details can be found in the log files at: C:\Program Files\HP\Systems Insight Manager\logs

C:\>
C:\>mxconfigrepo -f
Performing repository corruption fix.
23 Jan 2007 09:55:51,501 INFO [HPSIM_DEBUG]
Database Version:
23 Jan 2007 09:55:51,517 INFO [HPSIM_DEBUG]
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
23 Jan 2007 09:55:51,517 INFO [HPSIM_DEBUG]
Database Driver:
jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.0.2
23 Jan 2007 09:55:51,595 INFO [HPSIM_DEBUG] Checking for possible database corruption...
23 Jan 2007 09:55:52,814 INFO [HPSIM_DEBUG] Completed database checking with no errors.
Completed repository corruption fix.

C:\>

C:\>mxconfigrepo -f
Performing repository corruption fix.
23 Jan 2007 09:55:51,501 INFO [HPSIM_DEBUG] Database Version:
23 Jan 2007 09:55:51,517 INFO [HPSIM_DEBUG] Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
23 Jan 2007 09:55:51,517 INFO [HPSIM_DEBUG]
Database Driver:
jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.0.2
23 Jan 2007 09:55:51,595 INFO [HPSIM_DEBUG] Checking for possible database corruption...
23 Jan 2007 09:55:52,814 INFO [HPSIM_DEBUG] Completed database checking with no errors. Completed repository corruption fix.

C:\>mxinitconfig -a
Checking Requisites (13):
1. Server Property File ..OK
2. Server Authentication Keys ..OK
3. SSH Keys ..OK
4. Status Property File ..OK
5. Task Results Output Cleanup ..OK
6. Database Configuration ..OK
7. Database Content ..OK
8. Web Server ..OK
9. Setup Property File ..OK
10. JBoss Setup ..OK
11. Agent Configuration ..OK
12. Management Services ..OK
13. Initialization and Database Population ..OK
Requisite scan completed successfully.
Configuring Server Components (13):
1. Server Property File ..Done
2. Server Authentication Keys ..Done
3. SSH Keys ..Done
4. Status Property File ..Done
5. Task Results Output Cleanup ..Done
6. Database Configuration ..23 Jan 2007 09:58:22,033 INFO [HPSIM_DEBUG]
Database Version:
23 Jan 2007 09:58:22,064 INFO [HPSIM_DEBUG]
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
23 Jan 2007 09:58:22,205 INFO [HPSIM_DEBUG]
Database Driver:
jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.0.2
23 Jan 2007 09:58:22,376 INFO [HPSIM_DEBUG]
Database Version:
23 Jan 2007 09:58:22,439 INFO [HPSIM_DEBUG]
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
23 Jan 2007 09:58:22,580 INFO [HPSIM_DEBUG]
Database Driver:
jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.0.2
Done
7. Database Content ..Done
8. Web Server ..Done
9. Setup Property File ..Done
10. JBoss Setup ..Done
11. Agent Configuration ..Done
12. Management Services ..Done
13. Initialization and Database Population ...
This step never ends.

The End
Randy ...
Occasional Visitor

Re: problem upgrading from 5.0sp4 to 5.1

Just wanted to confirm that Ole Thompson's steps at the beginning of the thread resolved our issue. We have upgraded with our database from 5.0 sp5 to 5.1. Sure hope HP fixes this soon for everyone else. It was a real disappointment for us.
CA1499584
Regular Advisor

Re: problem upgrading from 5.0sp4 to 5.1

After various atemp, I install from scratch SIM5.0 SP5 and manually reconfigure it back, Then I try one more time and follow Ole Thomsen instruccions and that work for me...
Darrin Rawls
Respected Contributor

Re: problem upgrading from 5.0sp4 to 5.1

Support is working the case via the logged support calls, but I am wondering if this particular 'workaround' helps anyone else.



Thanks.
Alex HU
Advisor

Re: problem upgrading from 5.0sp4 to 5.1

We had the same problem and the same error!

- We rerun the setup and finished it.
- rebooted the server.
- ran the mxinitconfig -a command and this fixed most of our problems. We are now running SIM 5.1

only problem i encountered now, is that data collection fails on almost every server.

Good luck too all who dare to upgrade :D
Tony Cresswell
Frequent Advisor

Re: problem upgrading from 5.0sp4 to 5.1

Ran the upgrade and it failed like everyone else's.

I've just changed the database.admin and database.props as advised to change the hp.Database.prepareSQL=0

Ran mxinitconfig.exe -a

Started Sim and I have my SIM 5.1 server with all my config and servers listed.

Could be blind luck or an excellent workaround! Who knows!

Thanks anyway
Rancher
Honored Contributor

Re: problem upgrading from 5.0sp4 to 5.1

I have been extremely hesitant to upgrade my SIMS server after reading of all the problems it seems to entail. I saw that to be DST compliant, I have to upgrade now. Since this is a more "crucial" upgrade now than most, I would have hoped that 5.1 would have been less problem-free than it seems to be!
Alex HU
Advisor

Re: problem upgrading from 5.0sp4 to 5.1

We run our SIM server on on a virtual machine. only thing we have to do is clone our machine, update SIM and if it goes wrong (which it did both times) we just shut down the clone and start the other again.

Thanks to VM we had no real problem uppgrading SIM!