HP Version Control Repository Manager

[Brian Wright_1]

The windows service will not remain started...Can anyone tell me what may be wrong?

The HP Version Control Repository Manager service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 0 milliseconds: No action.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

[Tv_3]

Have you installed the latest agents?

With versions are you running.

For win2K download the PSP 7.20
For Win2K3 download the PSP 7.30

sincerly

[Brian Wright_1]

My SIM/VCRepository Server is 7.20 of the SSP. and running on Windows 2K. I'm not sure, but I'm wondering if it may have something to do with the version of JRE that is installed. Currently it's 1.4.2

[Ananthak23]

Upgrade the VCRM to the latest version from the link below:
http://h18000.www1.hp.com/support/files/server/us/download/22563.html and see if it solves the problem.

[Rob Buxton]

Brian,
I do not believe the JRE is involved.
There has been a problem with both the VCA and VCRM on Servers where there are old SSL Library files installed (e.g. Crystal Enterprise I think). This seems to have been corrected in the latest release of the VCA and VCRM.

[Brian Wright_1]

I have installedthe latest VCRM that I retreived from the link, Is there another for the VCA. The problem seems to have gotten worse....These two events just keep repeating, so I've disabled the service until I can figure it out.

Event logs are as follows:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7031
Date: 5/3/2005
Time: 8:06:17 AM
User: N/A
Computer: INTRANET
Description:
The HP Version Control Repository Manager service terminated unexpectedly. It has done this 123 time(s). The following corrective action will be taken in 0 milliseconds: No action.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 5/3/2005
Time: 8:06:18 AM
User: NT AUTHORITY\SYSTEM
Computer: INTRANET
Description:
The server {9E653AE8-7992-4543-B071-5340E464F75A} did not register with DCOM within the required timeout.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

[Rich Purvis]

Brian,
Starting in the 7.20 SS/Management CD release the VCRM and the VCA require that the HP System Management Homepage be installed and running. Do you know if you have that software also installed and running?

-Rich

[Brian Wright_1]

Yes the SMH is insntalled running, I can manage everything except the Version Control Repository

[Larry Shaw]

We have experienced a similar issue but one that did not cause VCRM to stop. After installing 4.2, we found a large number of DCOM messages in the event log on the CRM with similar timeout messages. We also found that many, but not all, of our client servers were experiencing DCOM timeouts AND started accumulating a lot of sessions of llsmgr.exe. We found that we could eliminate both by turning off WBEM in the Global Protocol setting page in 4.2.

We did have to use pskill or a reboot to get rid of the accumulation of llsmgr sessions on the client servers.