ERROR - A GUID must be specified as exactly 32 hexadecimal characters.

[SEBEMISMNUSA]

After a one year pause (as referred to previous forum postings)
I am attempting to get to HP SIM 5.1 (now with sp # 1 and hotfixes) from HP SIM 5. sp # 5. This is a Microsoft Windows 2003 server environment with Microsoft SQL Server 2000 sp # 4.

I see this error during the upgrade attempt.
7. Database Content
ERROR - A GUID must be specified as exactly 32 hexadecimal characters.
Completed with error.

These are details from two log files.
Note: With details not included, I tried this when the database was running Microsoft SQL Server 2005 sp # 2. I see the same error. I imagine there is a row in some table (or tables) that has invalid data. But which row in which table(s)??

While this is being done on a test system, the HP SIM 5.0 sp # 5 production is running fine - that is after Sun Java VM configuration changes and Pegasus WMI mapper for HP SIM version 2.4


2008-01-15 19:57:03,746 INFO [HPSIM_DEBUG]
Database Version:
2008-01-15 19:57:03,746 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)

2008-01-15 19:57:03,761 INFO [HPSIM_DEBUG]
Database Driver:
jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.0.2

2008-01-15 19:57:03,917 INFO [HPSIM_DEBUG]
Database Version:
2008-01-15 19:57:03,917 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)

2008-01-15 19:57:03,917 INFO [HPSIM_DEBUG]
Database Driver:
jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.0.2

2008-01-15 19:58:06,795 INFO [HPSIM_DEBUG] ****** Statement not closed for connection: DEVELOPERS MUST FIX THIS ASAP!!!!!! NodeRepositoryManager.loadAllNodesFromDb() ID:NodeRepositoryManager.loadAllNodesFromDb()
2008-01-15 19:58:06,795 INFO [HPSIM_DEBUG] ****** Statement:com.hp.mx.database.MapleStatement@1c7865b select deviceKey from devices

========= Begin Initial Configuration Record ==========
-------------- Operation = Configure
-------------- Upgrade From Version = C.05.00.02.00
-------------- To Version = C.05.01.00.02
-------------- Date = Tuesday, January 15, 2008 7:57:01 PM CST
-------------- User = App-098-HPInsightSQL
-------------- Host = as071009t.bemisco.net
-------------- 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 ..
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
ERROR - A GUID must be specified as exactly 32 hexadecimal characters.
Completed with error.

Details can be found in the log files at: C:\Program Files\HP\Systems Insight Manager\logs
-------------- Date = Tuesday, January 15, 2008 7:58:06 PM CST
-------------- Operation = Configure
========== End Initial Configuration Record ==========

[SEBEMISMNUSA]

This is the MXGuid in the devices table.
Somehow, there were five devices with blank MXGuids. Perhaps, these entries happened during Java Out of Memory errors (since fixed as listed in a previous posting)

Initial upgrade did not complete

-------------- Upgrade From Version = C.05.00.02.00
-------------- To Version = C.05.01.00.02
-------------- Date = Wednesday, January 16, 2008 4:08:19 PM CST
-------------- 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 ..
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 xml resource file to startup 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: Wednesday, January 16, 2008 4:16:49 PM CST
ERROR - Cannot start HP Systems Insight Manager service.
Possible cause: HP Systems Insight Manager service is not properly installed.
Resolution: Make sure HP Systems Insight Manager service is correctly installed, restart HP Systems Insight Manager then run mxinitconfig again.

Details can be found in the log files at: C:\Program Completed with error.

Stop and started HP SIM service.

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 ..16 Jan 2008 16:27:25,743 INFO [HPSIM_DEBUG]
Database Version:
16 Jan 2008 16:27:25,759 INFO [HPSIM_DEBUG]
Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

16 Jan 2008 16:27:25,837 INFO [HPSIM_DEBUG]
Database Driver:
jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.0.2

16 Jan 2008 16:27:26,024 INFO [HPSIM_DEBUG]
Database Version:
16 Jan 2008 16:27:26,040 INFO [HPSIM_DEBUG]
Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

16 Jan 2008 16:27:26,102 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 .....................................................................................

Hopefully, this will complete (unlike last year, again as listed in a previous posting)

End