Windows 64-bit SCM Installation Errors in HDBSetup and hserver.exe

Document ID : KB000049601
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

If, for any reason, you chose to install SCM to a non-default location on a 64-bit Windows platform, you may encounter an error when performing certain activities in HDBSetup. For example, when you attempt to Load Projects with the HDBSetup "LP" option or Load Forms with the HDBSetup "LF" option, you may get a dialog box displaying the error:

hserver.exe - System Error  

The program can't start because jvm.dll is missing from your computer. Try reinstalling the program to fix this error.

and HDBSetup.exe will report on the command line:

"Error running hserver load lifecycle project templates. Check log lplog.log for details."

and even if you are not trying to load projects or forms with HDBSetup, you will get the same error when you try to start the broker and hservers.

You may notice, for instance, that the BKRD broker process and the rtserver process startup correctly, but none of your hserver processes will start.

Solution:

THE PROBLEM
******************

If you are installing SCM on a 64-bit Windows server and you plan to also install the SCM VSIP Visual Studio plugin, you must install the SCM software to a "neutral" location other than the default of C:\Program Files.

The basic reason is because Visual Studio is a 32-bit application. Details about this problem and a workaround for it are discussed on the MyCA web site in the "Tuesday Tip: How to install the Visual Studio Plug in with a 64-bit SCM Client" located here:

https://communities.ca.com/web/ca-software-change-mgmt-global-user-community-harvest/message-board/-/message_boards/view_message/86390082?&#p_19

You are, of course, free to install SCM to any location you choose, so the problem described here applies to any situation where you have chosen to install SCM to a non-default location.

If, for any reason, you chose to install SCM to a non-default location on a 64-bit Windows platform, you may encounter an error when performing certain activities in HDBSetup. For example, when you attempt to Load Projects with the HDBSetup "LP" option or Load Forms with the HDBSetup "LF" option, you may see a dialog box displaying the error:

hserver.exe - System Error  

The program can't start because jvm.dll is missing from your computer. Try reinstalling the program to fix this error.

and HDBSetup.exe will report on the command line:

"Error running hserver load lifecycle project templates. Check log lplog.log for details."

and even if you are not trying to load projects or forms with HDBSetup, you will get the same error when you try to start the broker and hservers.

You may notice, for instance, that the BKRD broker process and the rtserver process startup correctly, but none of your hserver processes will start.

THE SOLUTION
******************

SCM ships with an included Java Runtime Environment (JRE). If you have specified a "neutral" non-default location for installing SCM, the installer ignores it when installing the included JRE yet updates the PATH environment variable to point to the location you specified.

The end result is that your jre cannot be found and any programs or services that depend on the jre will fail to execute.

For example, let's say you chose to install SCM to C:\SCM and specified this location as the target for your SCM software installation. The MSI installer will install to C:\SCM\SCM, but will put the included JRE at C:\Program Files\CA\SCM\jre\bin.

Unfortunately, the installer updates your PATH environment variable to the location you specified. If you examine your PATH variable after install, you will see:

Path=...;C:\SCM\SCM\jre\bin\server;C:\SCM\SCM\jre\bin;...

But that is not where your jre folder actually resides.

The workaround is to copy the entire folder (including sub-directories):

C:\Program Files\CA\SCM\jre  

to your desired target install location:

C:\SCM\SCM  

so that it ends up in:

C:\SCM\SCM\jre  

After copying the jre directory to your %CA_SCM_HOME% location, your hservers will start successfully and all HDBSetup options will work.