Version Control Agent

[Relloski]

I'm having an issue with the installation of the HP Version Control Agent.

I have rebuilt a server using the Proliant support pack 7.2 the Version control agent hangs upon boot and will not start up.

The system event ID's are:
Event ID 7022: The HP Version Control Agent service hung on starting.

Event ID 7031: The HP Version Control Agent service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: No action.

Where should I look to begin fixing this issue?
I could rebuild the server from scratch, but I wouldn't learn much from that.

Any help is appreciated.

Relloski

[Rob Buxton · Accepted solution]

Check if you have the file libeay32.dll in the system32 directory. If you do there are a couple of options.
Rename it and copy the version from C:\hp\hpsmh\bin into the system32 directory. Then test to see that nothing has been affected by the change.
Or, revert to the previous version of the VCA.

[Mike Hughes_3]

Hi Rob, this is a MAJOR pain. Neither option:

1. Revert back to old VC agent or
2. Replace DLL and check all your apps

is very desirable with a large . Will HP be delivering a PSP v7.20B or just a separate updated VC agent. If so I hope its soon. I've stopped our Enterprise management rollout project becuase of this issue alone with HP SIM. Any ideas on a date for new VC agent ?

[Richard Edwards_4]

I have had this problem before, not with 7.20 agents though.

For me, it seemed to be caused when I locked down SNMP on the server for security reasons.

The VCAgnet does not work unitl you add localhost or 127.0.0.1 to the security tab within the snmp configuration.

Working for me, give it a try.

[Rob Buxton]

Mike,
I've no inside knowledge of VC release dates.
I believe from another thread on the VC Issue that the libeay32.dll file released by HP is a more recent version.
The main question is why it tries to use the system32 version and not the one in its own local directory.
I've also found here that a large number of our Servers do not have this file in the system32 directory. There's no problems for those.

Richard,
Thats standard documented SNMP behaviour. W2003 changed the default from allow all hosts to allow selected hosts. If you retain that config you need to add localhost and the CMS Server to the allowed hosts.

[Relloski]

Richard: By default, we add several IP's to the SNMP Security tab. We always add 127.0.0.1, I wish that were the reason, but it was not.

Rob:
I have opted to uninstall the VC Agent and reverted back to 7.1.

I experienced this problem with only one server, but will not continue with the 7.2 vc agent until I either see/hear something from HP or get my hands on a server which I can test this on.

Thanks for the help All.

Relloski

[Keith Rogers]

Are there any VCA entries in the Application log?

I see that there's another thread on this - so does anyone know what application installed the OpenSSL library in the system32 directory? I don't see it on my 2003 'standard' edition. (Can someone attach the offending DLL to a reply, so we can try to reproduce this?)

[Rob Buxton]

Keith,
Attached is a file from our W2003 Server, this Server has Crystal Enterprise reporting installed on it.
And yes, I agree that not all Servers have this file in the System32 directory.

I find it odd that VCA has this file in a local HP bin directory but seems to default to the system32 directory.

[Relloski]

I rebuilt the server.