Setup waiting at 'Initiazing System Insight Manager' screen

[Edgars Rudans]

Hi all,

Windows 2000 std sp4

Installing System Insight Manager 4.1 sp1. During setup - HP Systems Insight Manger, the setup process seem waiting on 'initialiation complete' for something and cannot continue. Pls. see attached dialog box.

Any ideas?

TIA,
Ed

[Joel Rubenstein]

The problem occurs because when the SIM database is created it uses the collation sequence specified during the SQL 2000 installation. If that collation sequence had been changed from the default (SQL_Latin1_General_CP1_CI_AS) then the SIM installer has problems when creating the necessary database tables.

If you look at the initconfig.log file before you abort the installation you will see errors like:

Creating database 'Insight_v1_0_154547260'...
Creating schema...
*** WARNING: FAILED the following SQL command:
====
CREATE index notice_st_dev_sv_index on notices(State, deviceKey, noticeseverity)
====
java.sql.SQLException: [Microsoft][ODBC SQL Server Driver][SQL Server]Column name 'deviceKey' does not exist in the target table.
*** WARNING: FAILED the following SQL command:
====
CREATE INDEX trap_rcv_lu_index on trapitems (trap_enterprise, trap_generic_id, trap_specific_id)
====
java.sql.SQLException: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot create an index on 'trapitems', because this table does not exist in database 'Insight_v1_0_154547260'.
*** WARNING: FAILED the following SQL command:
====
create view notices_view as ( select devices.Name as 'Device Name', 'Severity' = case when noticeSeverity=100 then 'Informational' when noticeSeverity = 1 then 'Normal' when noticeSeverity=2 then 'Warning' when noticeSeverity=3 then 'Minor' when noticeSeverity=4 then 'Major' when noticeSeverity=5 then 'Critical' else convert(char(10), noticeSeverity) end, 'state' = case when state=1 then 'Discovered' when state=2 then 'Not Cleared' when state = 5 then 'Cleared' when state = 6 then 'IN Progress' end, generated, cleared, largeValue as Description from notices, noticeType, devices, stringresource, stringtablelarge where notices.noticeType = noticeType.noticeType and notices.deviceKey = devices.deviceKey and stringresource.resourceclassname='noticetype' and stringresource.resourceName='description' and noticeType.noticeType=stringresource.subclass and stringtablelarge.id = stringresource.id )
====
java.sql.SQLException: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'stringresource'.
*** WARNING: FAILED the following SQL command:
====
create view view_deviceAssociations as ( select 'associatedDeviceKey'=deviceKey, 'DeviceKey'=device_associations.deviceKey1 , 'associatedDeviceName'=RTRIM(name), 'associatedDeviceStatus'=overallstatus, 'associatedDeviceType'=producttype, 'AssociationTypeNumber'=AssociationTypeNumber from device_associations LEFT OUTER JOIN devices ON (device_associations.deviceKey2= devices.deviceKey ) )
====
java.sql.SQLException: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name 'deviceKey2'.
*** WARNING: FAILED the following SQL command:
====
INSERT FolderQueryStatusPolicy(type,className) Values (1,'com.hp.mx.core.foldermanager.QueryStatusBySeverityPolicy')
====
java.sql.SQLException: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'FolderQueryStatusPolicy'.
*** WARNING: FAILED the following SQL command:
====
INSERT FolderQueryStatusPolicy(type, className) Values (2,'com.hp.mx.core.foldermanager.QueryStatusByEventSeverityPolicy')
====
java.sql.SQLException: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'FolderQueryStatusPolicy'.

[Edgars Rudans]

Joel,

You are right! I have exactly the same situation. Is there any known solution?

Regards,
Ed

[Joel Rubenstein · Accepted solution]

The only solution is to install SIM using a database instance configured to use the default database collation sequence.