HP SIM 5 - Install of VPM Pack fails

[Ed McDonald_1]

I'm getting the same error numerous times when trying to install the Vulnerability and Patch Management Pack on my SIM 5 server.

I've searched the forums and found a few posts regarding the following error, that indicate to just reinstall from a different folder. However that 'workaround' does not work. Any suggestions?

[Ed McDonald_1]

Ok no responses so far, can anyone tell me whether I can install this on my CMS server running W2003 SP1 and SQL 2000 SP3?
Thanks.

[Joe Wiedow]

What are your TEMP and TMP environment variable set to for your user that is executing the VPM installation and have you disabled NTFS 8.3NameCreation?

Try changing the TEMP and TMP environment variables to a path that does not contain a space and see if that fixes the installation issue.

[Ed McDonald_1]

The TMP and TEMP Environment Variables were set to %userprofile%\localsettings\temp.

I set both of these to C:\temp

I also changed the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem. Create a new DWORD value named NtfsDisable8dot3NameCreation. Set it to 1.

Tried reinstalling - twice with reboots inbetween.

One other question, it seems to be attempting to install MSDE 2000 Desktop Engine during the install. Doesn't this integrate with my current SQL2000 SP3 server on the same server?

Thanks.

[Luana Marques Garcia]

This error happens when ISS has troubles to start the Default Web Site.

According to Microsoft, it happens when there is a conflict on HTTP Port 80.

Please, see the the following advisory:
http://support.microsoft.com/default.aspx?scid=kb;en-us;816944

You might want to uninstall the application that is currently using port 80 in order to install VPM.

Access http://localhost from your browser to know what is the application currently using default HTTP port 80.

[Ed McDonald_1]

Ok that's a problem. I have McAfee ePolicy Orchestrator using ports 80 (and 81) for Agent-Server communication.

So the next logical question is (since I'm NOT uninstalling ePolicy - and cannot reconfigure without numerous issues) how can I install VPM to a port other than port 80?

Thanks for your assistance.

[Bernardo Tagariello]

It is unlikely that you will be able to install to an alternate port. A suggestion would be to turn off the services which are allocating the conflicting ports.

Do the VPM installation as is.

Then reconfigure VPM to use a different port number.

You can adjust VPM after installation by modifying the URLs in the configuration files
statcredentials.xml to have:

http://servername:999/STATScanner/Update/
http://servername:999/STATScanner/Soapbox.dll?Handler=ScanEngine

We have not tested this configuration.
We are awaiting some confirmation from a couple of developers to confirm that this approach should work or not.

tag

[Bernardo Tagariello]

Another approach may be to use the port 443 by turning on HTTPS.

Just some suggestions.

tag

[Luana Marques Garcia]

Please, do the following steps in order to workaround conflicts on HTTP Port 80 :

1. Go to Control Panel -> Administrative Tools -> IIS
2. Right click on folder Default Web Site and select properties
3. Select "Web Site" tab and change "TCP Port" field for 999
4. Start IIS Service
5. Install VPM
6. At VPM Server go to C:\Program Files\HP\VPM\ and edit statcredentials.xml file to have:
http://servername:999/STATScanner/Update/
http://servername:999/STATScanner/Soapbox.dll?Handler=ScanEngine
7. At SIM Server go to C:\Program Files\HP\Systems Insight Manager\hpwebadmin\webapps\ROOT\mxportal\VPM\config and edit statcredentials.xml file to have:
http://servername:999/STATScanner/Update/
http://servername:999/STATScanner/Soapbox.dll?Handler=ScanEngine
8. Restart System Insight Manager service.

[Ed McDonald_1]

Ok thanks for all the previous suggestions.

I tried them all to no avail.

I also reconfigured ePolicy to function on ports other than 80 and 81 and VPM still gives the same error on installation. At this point I'm pretty much ready to attempt installation on a server other than the one hosting CMS and ePolicy.

[Luana Marques Garcia]

In step three, after you change TCP Port to other than 80/81, does the Default Web Site starts using the new Port?

Installation is prevented if there is a current conflict on port 80/81.

[Ed McDonald_1]

Yes.

I do wish there was a way to edit the installation of VPM to attempt initial install on a port other than 80. It's unrealistic to think that there's no other product that may be utilizing the same port that VPM wants to install to.

[Luana Marques Garcia]

Our developer suspects you have a bad metabase from the previous installations.

Could you, please, make sure IIS doesn't have any reference to STAT Scanner WSI under the "Default Website" and Application Pool. And also delete any reference of WSI in C:\WINDOWS\system32\inetsrv\metabase.xml. If this becomes too painful, you can restore an old copy from C:\WINDOWS\system32\inetsrv\history. Just look for a file with no WSI. Please let us know if this works for you.

[Jennifer_74]

Just to clarify. VPM itself is not trying to use port 80. We are trying to find IIS on it's default port of 80.

[Ed McDonald_1]

My ultimate remedy to this problem was to build a second management server, and install VPM. No issues there.