SIM install - VCRM failed

[Greg Lawrence]

Have recently intsalled SIM but noticed that VCRM install failed ..not sure why .??
How can it be installed after SIM install
Running on Server 2000....
when selectiong OPTIONS > VERSION CONTROL REPOSITORY get following message :

"Error, the Version Control Repository Manager (VCRM) was not found on any discovered systems. If the VCRM is installed, be sure it is running and that the system it is running on has been discovered by HP Systems Insight Manager. To verify the VCRM is identified, view the Links tab on the system's Device Page. If the system is discovered, but the VCRM does not appear on the systems' Links tab, run an Identify Systems task to that system. "

Thanks

[Jadrice Toussaint]

Hello -

Try downloading it from the link below. Double click on the executable to start the install.

http://h18000.www1.hp.com/support/files/server/us/download/18824.html

Let me know if that helps.

[Greg Lawrence]

thanks Jadrice, will give it a bash

[Mike Kapos_3]

I'm having the same problem. I recently downloaded SIM 4.01. I had 4.00 and VCRM running fine on this server before.

I uninstall 4.00 and installed 4.01.I configured it and SIM is working fine but now my VCRM isn't working.

I've tried uninstalling and reinstalling, deleting repository but nothing is working. The VCRM service is there and running but I can't link to it from the device home page and none of my servers (200+ proliants) can't access the VCRM.

We rely on this to keep our servers updated so any help would be greatly appreciated.

Thank you.

[Iain Balmer]

Same here also. Was running 4.0 and VCRM for loooong time. Installed 4.1, VCRM not working. Tried reinstalling VCRM, still the same. Loggin on locally to the Agent, no sign of the VCRM in there either, although the service is up and running. I think as far as the 'upgrade' process goes... I wish i'd never bothered. Cheers HP, for causing me more work !!

[Craig McKellar]

Had this issue as well after removing 4.0 & installing 4.1, but found that re-installing both the agents and the VCRM on the CIM, then re-identifying the CIM resolved it?

[Kevin Smith_17]

I am also expeiencing this problem and have tried the ideas listed in the previous posts, without success. Does anyone have any other thoughts?

Thanks

[Mark Dale_3]

Afraid I have no answers but I have experienced the same error. I was installing for the first time. SIM works 100% but I just can not get it to see the VCRM.

Anybody find a fix? I've gone down the uninstall reinstall route but without success.

[OlivierV]

Same problem here. The link to the VCRM does no longer appear on the home page. It is not listed in the VCR list and a reinstall does not repair. The VCR service is running.
W2000 SP4 server and Sim 4.1.
Hope support team will give a answer.

[Joel Rubenstein]

This is a known problem and the following procedure should resolve the issue.

Download and install HP Web-Enabled Management Software Security Patch for Windows Version 5.94, which is available as SoftPaq SP25771 from the following URL: http://h18007.www1.hp.com/support/files/server/us/locate/2843.html
Login to the server with administrative privileges.
Stop the following services through the Microsoft Services Applet:

All HP Insight Agents
Array Configuration Utility
HP Version Control Repository Manager
HP Version Control Agent
HP Insight Web Agent
Surveyor
HP Performance Management Pack (PMP)
HP PMP Tools

Rename the directory \compaq\wbem to \compaq\wbem_old.
Create a new directory \compaq\wbem.
Copy the contents of the directory \compaq\wbem_old to \compaq\wbem.
Restart the services that were stopped in step 3 above.
The VCRM will now be accessible from the System Management Homepage and the local host URL.



This is documented in customer advisory ES040719_CW04 REVISION: 0

Version Control Repository Manager (VCRM) Not Accessible After Installing HP Systems Insight Manager (HPSIM) 4.1

[Mark Dale_3]

Excellent! Worked a treat.

Thank you very much.

[OlivierV]

Thanks.
Unfortunaly, I have uninstalled/reinstalled agents and latest vcrm before to read this thread. But it worked also, with the patch specified.