HP Version Control Agent Fails to start after 7.20A deployment

[Lenny Davis]

HP Version Control Agent Fails to start after 7.20A deployment. User Insight Manager 4.2 to deploy support pack on W2K server. Upon reboot Version control agent hasn't started autmoatically and when you try and start manually it says Error 1067: The process Terminiated unexpectedly.

I must say these the whole version control setup has been and still is an extremely unreliable function. Have had no end of problems since setting up SIM 4.1 last June / July and not much has changed upgrading to 4.2. HP still have alot of work to do here to get this right. Very disappointing and unnecessarily time consuming.

Thanks

Lenny

[Rob Buxton]

I've had the same on a few Servers, I removed and installed the previous version of the VCA.
There seems to be an issue on some of our Servers with the file LIBEAY32.DLL. It fails with "the ordinal could not be located in library LIBEAY32.DLL" and the Service will then fail to start with the stop you're experiencing.
I've noticed not all of our Servers have this file in the System32 directory.

[Lenny Davis]

Yes I backreved to the previous version which installed and ran OK. Is this a bug in the new software? If anyone has any knowledge of a workaround to install the 7.20A support pack version control agents or information on a forthcoming HP fix this please post the information on this forum post ASAP. Interestingly enough I have tried installing the support pack on 2 servers, one standard W2K server worked OK but it was the Citrix server that generated the VC error.

Thanks

Lenny

[Rob Buxton]

Lenny,
It was just a small percentage of the Servers I updated that failed with this.
I've not yet found a common thread.
I'll post if I hear more.

[Mike Hughes_3]

I've also had the same problem with all of my Win2K servers on SP4. And yes frankly this is disappointing. What's the point of having "dodgy" version control, you may as well apply updates manually. Have also had several failures with HP SIM 4.2. When will HP release a service pack ? When will HP fix PSP 7.20A ? Its becoming more trouble than its worth. Also just to moan some more. Setting up SSH to do the "Initial Proliant Support Pack" deployment, is more work than just installing a PSP manually onto servers. I think HP SIM v4.2 is great, but still lots of bugs and I think you guys need to start looking at the big picture more.

[Jon Ward]

Both libeay32.dll and ssleay32.dll should be in the hp\hpsmh\bin directory. They provide OpenSSH support.

Try opening these files from a working system to a system that is not working to see if it is indeed SSL related. (If they are outright missing, I would expect it to be related).

[Rob Buxton]

Jon,
These files are in the directory you describe, but the libeay32.dll is also in the System32 directory.

My guess is that on these Servers the HP VCA is trying to use the version in the System32 directory that is not compatible rather than the one in the hp directory.

I am unwilling at this point to replace the System32 versions of these files as it might break something else. The version in the HP Directory is the same.

[Jon Ward]

Maybe you could try to just rename the files in the System32 directory, copy over the libeay32.dll and ssleay32.dll files to the hp\hpsmh\bin directory, then observe the results on a lesser critical system. This way, the modification is easily reversible.

It is very possible that the libeay32.dll and ssleay32.dll files currently in the System32 directory are too old.

[Rob Buxton]

Jon,
In the System32 Directory there's only the LIBEAY32.DLL File, no SSLEAY32.DLL

There's no Version Tab on the Properties for the HP Version of the file, but it is larger and more recent. The System32 Version Tab has;
Comments:
This version contains md_rand MT (See OpenSSL CVS checkins 4613, 4951 (Summer 2001) and related) fix and /Oy- compile flag.
Version: 0.9.6.101
Company: The OpenSSL Project
The main purpose of this Server is as a Crystal Enterprise Reporting Server.

On our Development box I've renamed the Libeay32.dll file in the system32 directory and replaced it with the HP Version. I've now asked our Enterprise Reporting folk to test things to see if that has broken anything.

I'm not sure how the order of precedence works but it still strikes me that if HP has a version in its own directory then it should use that rather then the System32 version.

At this point I've not tried reinstalling the VCA. I want to see if the testing throws up anything first.

[Jon Ward]

I would think that the one in the hp\hpsmh\bin directory should be used as well, but the System32 directory is typically specified in the PATH variable, so it is possible that it wins out.

Incidentally, one one system, the only source of the libeay32.dll and ssleay32.dll I had was in the hp\hpsmh\bin; it has little more than the Proliant Support Pack for Windows 2000 installed on it. A Windows Server 2003 server with hp Systems Insight Manager 4.2 with all the trimmings had dozens of locations with these files, though not System32.

[Stephane Hardy]

Renaming an older version of libeay32.dll present in system32 did it for me. Thank you all!

[Rich Purvis]

FYI, this issue was addressed in the SS/Mgmt CD release 7.30 of version control software.

-Rich