Error message at start of installing HP SIM v5.3 with SP1

[switch]

When I execute the setup for HP SIM v5.3 with SP1, the first page of the installation Wizard starts with:
HP Systems Insight Manager
Database Configuration

When I continue I get the following error message:

TCP/IP Protocoll is not enabled for the specified database server
Please enable TCP/IP Protocoll.

Subsequently I am unable to continue the installation and have to cancel the setup process.

I am running Windows Server 2008 Enterprise SP2 on an HP M350 G5 server (with 2 X Quad processors and 16 GB RAM).

For your information: I have disabled in the registry IPv6, because else my Exchange Server 2007 SP1 won't work. This apparently very rare anomaly is described in Microsoft's KB 952842.

I am looking forward to a resolution to this issue.

[Rob Buxton]

That's part of a DB set up requirement. Are you using the DB that HPSIM is installing or are you pointing it to a remote DB server?
If the latter then you'll need to get your DBA's involved.

[switch]

Thanks Rob for your feedback. Somehow it points to a Database indeed, because the Wizard does not offer the option to install SQL/SQL Express. The SQL/SQL Express option is selected (as default). Unless Exchange uses an embedded version of SQL, I am unaware of an installed version of SQL or SQL Express i.e. I never installed it myself.

As Instance name it is referring to Microsoft##SSEE. I have no clue what that means.

I searched my server (Windows Server 2008 SP2 + Exchange Server 2007 SP1)if it includes an SQL database. Nothing found. So, I'm puzzled.

In the meantime I enabled IPv6 on my NICs and deleted the registry entry which disabled IPv6. I thought that this could play a role. It doesn't make a difference. So, I leave IPv6 enabled on my system now.

Isn't there any log file relating to the setup attempt for SIM v5.3, in Windows Server 2008? This would help me tracing the existence of the database SIM setup looks at during the install process.

[sandeep_raman]

You can verify if SQL or SQL Express exists on the server by checking the Add-Remove Programs. If you find it installed,
Navigate to
All Programs - MS SQL 2005 - SQL Configuration Manager
Here you would find the TCP/IP option

[switch]

Well, it was pointing to the Instance Name Microsoft##SSEE. I found out that Microsoft##SSEE refers to the Windows Internal Database. This WID is also referred to as SQL Server Embedded Edition. See: http://en.wikipedia.org/wiki/Windows_Internal_Database

So, I decided to install SQL Server 2008 Express 64-bit (runtime). I succesfully installed this Instance.

Aftwards I succesfully enabled TCP/IP for SQL Server 2008 Express following this howto:
http://msdn.microsoft.com/en-us/library/bb909712.aspx

I encountered another error message: Unable to get information from the specified database server.

This HP document, http://docs.hp.com/en/418812-004/ch14s01.html, listed the solution of tis problem:

Go to Start > Administrative Tools > Services >enable SQL Service Browser.

After this hurdle, HP SIM v5.3 installed succesfully (a very long process, as it populates the SQL server database with data).

Thanks all for your feedback and suggestions.

[switch]

I add some more issues, which I had ommitted to mention in my previous posting:

1. Go to Server Manager > Security Information > Configure IE ESC and set Internet Explorer Enhanced Security Configuration (IE ESC) to Off for Administrator and Users
2. Services > enable SQL Server Agent (this was disabled)
3. Setup HP SIM without WMI Mapper initially. After rebooting run the HP SIM setup again. The Pegasus WMI Mapper v2.6 will start. You get the option to choose and I choose Typical installation.

WMI Mapper did NOT succuesfully install when it was carried out with all other HP SIM features (exit error 1603=fatal error during installation).

So, above summarizes the few additional actions I additionally made.

The story is not over yet. After having successfully completed the installation of HP SIM, an Operating System Account has to be created and configured in the System Management Homepage. Subsequently each Version Control Agent has to be configured to use this same account.

The latter I didn't do yet. Keep fingers crossed.