SIM 7.1 can’t detect Version Control Repository Manager in a Windows VM

[CmanI88I]

After upgrading to SIM 7.1 (from 6.3) in a Windows VM, I have a problem with VCRM. A fresh install was the same so it wasn’t the upgrade.

VCRM in SIM 7.1 in a Windows VM couldn’t be detected by SIM 7.1. So there is no “HP Version Control Repository Manager” link in the “Tools & Links” tab and you couldn’t deploy software.

The same SIM 7.1 + VCRM is correctly detected by my other SIM 6.3 in a Windows VM.

I think that it’s due to the difference between 6.3 and 7.1 Identification task.

In SIM 6.3, the Identification log

“* Checking for System Management Homepage and other HP web agents...

Normal:   System Management Homepage (SMH) is installed or is responding on the system(s).  . . .”

In SIM 7.1, the Identification log

“* Checking for System Management Homepage and other HP web agents...

Normal:   The system is not a server, storage or desktop. Skipping the check for System Management Homepage. . . .”

I installed VCRM - SIM 7.1 on a physical server and it got correctly detected by SIM7.1 VM.

My conclusion is that the Identification task in SIM 7.1 skips too quickly while identifying a VM and therefore can’t detect VCRM in a VM. Does anyone else has this problem too? We use VM’s heavily in our test environment.

[SwisspostIT]

I had the same issue and the solution was to import the HP SMH certificate of the HP SIM Server to the trusted certificates list under options --> security --> credentials --> trusted systems... --> trusted certificates

[CmanI88I]

Thanks for the tip. I already had the certificate imported in the SMH of the Sim server and I've imported it again but no changes there. So you had this problem on a SIM7-VCRM too?

[shocko]

Can you check the status of the service that runs the repository and also see if spqsrhsmo.exe is running?

[CmanI88I]

yes, service is running and as stated, this VCRM(SIM7) VM server could be detected correctly by SIM6.3 in a VM, not by itself or other SIM7 in VM. So I wonder if anyone has a correctly running VCRM SIM7 server running in a VM.

[shocko]

Yes, I am running it on a VM.

[shocko]

What exact version of the RM are you running?

[CmanI88I]

Version Control Repository Manager 7.1.0.910

[shocko]

Can you post a screenshot from SIM Options->Software/Firmware->Version Control Repository

[CmanI88I]

here is the print screen

[shocko]

Hmm, can you run the following:

• vcrmcli.exe /show

Also, check the system properties of the machine where VCRM is running and make sure nothing has been hardcocded there i.e. system type or model.

[PrzemekK]

You need to discover again VCRM machine. Do you have any public certificates or from windows PKI ?

[CmanI88I]

C:\hp\hpsmh\data\cgi-bin\vcrepository>vcrmcli /show

VCRM Settings

Repository Path         :- D:\VCRMRepository\
Operating System        :- win2003,win2003x64,win2008,win2008x64,win2008r2,rhel5
,rhel5x64,rhel6,rhel6x64,
Automatic update        :- Disabled

And from your print screen confirms my presumption that my SIM server is not correctly identified as a server.

In my SIM6.3 server, this SIM7 server was identified as system type=Unknown, however, SIM6.3 can further identify the VCRM. However, SIM7 identification stopped there when the server type is unknown.

So I think the issue here is why my VM can't be identified correctly. Thanks for all the help.

[shocko]

What Virtual Platform are you using? Any firewalls in play?

[PrzemekK]

In my case uninstall 7.1.0.17 and install smh 7.0.0-24 resolved problem. After install rescan host.

[ICS]

Did you set the VM CMS system properties as Proliant and the OS as Windows server 200x

[shocko]

I think you had to set the model to proliant in previous version but not in 7+ in my experience.

[CmanI88I · Accepted solution]

I've managed to create a work-around. After supplying a system credential with enough privileges in the identification task, WBEM/WMI will kick in and the task can identify the servers as servers after which VCRM is detected correctly.

[shocko]

Well, you learn something everyday :) I would have thought it didn't matter if you were using SNMP/WMI at all for this type of identification but it obviously does :)

[Paul Kurtz]

Question, I used an Administrator account and this still did not fix the issue on two installs.  Can you provide more detail?  Out of the box the HP SIM install on a VM using ESX 5.0 and Windows Server 2008R2 x64 does not work correctly.  I have done 3 plus installs and same result. 

I will be opening a case with support on this issue, just need to collect data to see if you saw the same issue.

Windows 2008 R2 x64 VM on ESX 5.0 update 1

SNMP service installed

3.5 .net feature installed

SNMP trap set to snmp community string and to send to localhost

SNMP security accept all snmp traps and listed snmp community strings

HP SIM global creds

SNMP set

no sign in

[Paul Kurtz]

The problem is when you install HP SIM 7.1 it installs WMI Mapper services with Log On As NT SERVICE\WMI Mapper and NT SERVICE\WbemConsumer.

Check your services for Pegasus WMI Mapper and Pegasus WMIMapper Indications Services

I changed the services to start with the Local System account.

Then go into HP SIM and change the system credentials on WBEM\WMI to local admin or admin account

HP SIM will identify the system correctly.

SNMP and WBEM should be used. 

You should see System Management Homepage and VCRM as links in HP SIM.

[franr1]

I am having the same issue and the post marked solved and the last post have not fixed the issue.

Furthermore, the HP Version Control Repository Manager is taking longer than 3 hours to start.

Any suggestions?

[CmanI88I]

Maybe you can look in the vcrm log for clues. Our vcrm starts with a "catalog validation" which takes about 25 minutes.

[Sander-A]

The version control repository takes at least 3 hours when starting up or rescanning. If you find a solution please post.

I did have issues with my SIM install, and after opening up a case with support, ran the install again with uac turned off. If you haven't done that you can try it.