VCRM on SIM 4.01

[Mike Kapos_3]

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.

[Mat Starling]

I have this same problem, after upgrading from 4.00 my servers cannot see the VCRM.

I too have also tried re-installing both VCRM and SIM with no joy.

[Mike Kapos_3]

There seems to a lot of problems with 4.01 and the VCRM...

Does anyone know what's wrong or how to fix?

I rely on this service to keep my machines up to date...

Thanks

[Markus Hodel_1]

I started from scratch with a new installation of SIM 4.01. Same Problem, VCRM is not working

[StefN]

check your HTTP server log file on errors.
I resolved this by entering the full dns name of the server in the http server option trust.
stef

[Mike Kapos_3]

I've reinstalled Management agents and VC agent, rebooted server NOTHING... I've checked HTTP log and no errors.

Where did you set your HTTP server option trust? My trusts right now are all set to accept all.

[Darrin Rawls]

If you had SIM 4.0 installed on a server, then you uninstalled 4.0 and installed 4.1 (the recent release, which I think is what you are talking about), what will happen is the certificate is now a different cert.

Unfortunately, the upgrade from 4.0 to 4.1 was taken out of the release and we are doing it separately. We ran into a couple of issues we would rather not release until we had them totally addressed. We are aggressively working the issues. An in-place upgrade would have solved this issue.

If you have NOT uninstalled 4.0 (or have a backup of 4.0), I would suggest copying the CERTSTOR directory off, then install 4.1, stop the SIM service, copy the "older" certstor directory over the new one for 4.1, then restart the SIM service.

Your deployed devices should now trust the new 4.1 machine (the older cert is now being used by the 4.1 service).

Hope this helps.

[Darrin Rawls]

BTW, if the servers are set to trust all, they should be fine. Make sure that the Identification task in SIM is run on those devices to make sure it determines that they are trusted (by default this should run once a day).

[Mike Kapos_3]

I don't think this solves the problem as I'm not using certificates. My settings are all set to trust all.

How would this fix the VCRM not showing up? It's installed and service is running.

I uninstalled 4.0 and installed 4.01 on the same server.

[Iain Balmer]

Nope. still doesn't work. tried reinstalling agents, etc. VCRM is not appearing within the agent homepage, even though the service is running. I'm getting seriously hacked off with this. Any other suggestions ?

[Mike Kapos_3]

I agree, I'm getting pretty frustrated with this "upgrade" also. Can someone from HP at least let us know that they are able to reproduce this problem and they are working on a fix?

Thank you

[Darrin Rawls]

I'll get someone to look into it. Has anyone opened a support case? Thanks!

[Mike Kapos_3]

Thanks Darrin for looking into this, please keep us informed.

FYI: I haven't opened a support case.

[Darrin Rawls]

to really "work" an issue, we really need a support case so it can be worked correctly and with the right debug informaion. Can one of you log one? Hate to be a stickler, but the forum wasn't meant for bug fix notifications and stuff, and I want to make sure we can repro it correctly.

Thanks!

[Mike Kapos_3]

I've never actually called for software support, what's the right channel to go through in order to log a call? Or can it be done over the web.

Thanks

[Darrin Rawls]

1-800-OK-COMPAQ (haven't transitioned the 800 number yet :) ) and there is a menu option for ProLiant Essential software about a level or two down.

[Mike Kapos_3]

CASE#3206585419

[James Kennedy_4]

I have the same issue,
For me, I've noticed that even though the service is running, I can't connect to the repository management page

https://localhost:2381/vcrepository

this brings up a page not found error, there seems to be a problem with the Web agents.

[REPSOLYPF]

I have the same problem, VCRM don´t work propert

[Chris Hibbard]

This looks like a proxy takeover issue, which will be fixed once an for all in an upcoming release. Until then, you can decrease the likelihood and frequency of the problem by upgrading all your products until they have the same version of HTTP Server (5.94 is the latest). You can download a patch from the SMH homepage (http://www.hp.com/servers/manage/smh/ ) {direct link to 5.94 patch: http://h18007.www1.hp.com/support/files/server/us/download/20666.html )that will upgrade most of them for you on Windows; Linux you must run an install for each product since the HTTP Server is "built-in".

For a temporary fix (until you reboot or start and stop web-managed services) you can usually get things going by stopping ALL web-managed services, then starting the web managed service with the *latest* HP HTTP Server version first, THEN starting the others.
(NOTE: if you are running ACU-XE/ Array Configuration Utility it does nto show up in Services; you must take other stes to stop and re-start it.)

-Chris Hibbard
System Management Homepage and Version Control QA team lead

[cnlei]

Thank you!
After install the patch, this problem is fixed.

[James Kennedy_4]

Glad to know there is a fix for this, too bad I already spent the last day rebuilding my SIM server from scratch. Now my VCRM is giving me these errors:


Automatic update downloaded 0 files. No Version Control Agents have provided operating system information to use as a download selection criteria.

The automatic repository update process completed successfully. No files were downloaded because the site catalog is unchanged.

[Chris Hibbard]

James,
There should be at least one request from a Version Control Agent to the VCRM, so that the VCRM will know that it has to download the Support pack for the requesting VCA Operating System.
If the VCRM is installed and if there is no request from the VCA to the VCRM, then the VCRM automatic update doesnâ t download any support packs.
This has been documented in the Version Control User guide under FAQ. This document is available on the Management CD. Look for the fAQ named "I installed Version COntrol Repository Manager and configured it for manual updates. Its log says the update suceeded, but there are no files in the reprository...

[Mike Kapos_3]

Unfortunetly the fix posted in the thread is not a fix. It's a workaround that fails as soon as you reboot your server.

The reason it works to begin with is because the patch restarts all the web services. If you reboot your computer the VCRM will again be gone and you'll have to manually restart all the web services again to get it working.

[Chris Hibbard]

Yes, this is a tempory "solution", as I mentioned in the previous post.

The proxy takeover issue is removed once all products are updated to use the same HTTP Server version. Beyond that, this is a different issue.

To help clarify your remaining (portion of the) issue, does the VCRM work fine (temporarily) every time to stop and re-start the services?