After upgrade to v14, the SCM Administrator won't start
search cancel

After upgrade to v14, the SCM Administrator won't start


Article ID: 206094


Updated On:


CA Harvest Software Change Manager CA Harvest Software Change Manager - OpenMake Meister


Installation of the SCM v14 full client completed successfully, but when I try to start the Administrator Tool I get an error message:

This application failed to initialize properly.

Please contact your administrator or Customer Support.

Error code=0x00005211


Release : all releases

Component : CA Harvest Software Change Manager


There could be many causes for this error message.


Here are the initial things to check:

  • Did the person installing the SCM Client have "Local Administrator" permissions on the computer?
  • Did they execute the installation program in "Run as Administrator" mode?
  • Did they reboot after installation completed?
  • When executing the Administrator Tool for the first time, did you select "Run as Administrator" mode?
  • Your system environment variables should include these settings:

CA_SCM_HOME=C:\Program Files\CA\SCM





RTHOME=C:\Program Files (x86)\CA\SharedComponents\PEC

  • Your system path should include these folders:

C:\Program Files (x86)\CA\SharedComponents\PEC\bin;

C:\Program Files\CA\SCM\x86;

C:\Program Files\CA\SCM;





  • If your environment variables look OK, the next thing you can do is try to execute the Administrator Tool from a command prompt window to see if any additional error messages are shown.  To do this open a command prompt window "Running as Administrator" and execute:


ADvantage.exe -Product="SCM Administrator"

  • Another thing to try is to re-register the dlls that SCM Administrator Tool depends on.  To do this open a command prompt in "Running as Administrator" and execute:


copy RegisterRelease.bat test.bat

notepad test.bat

In notepad, you will see a list of Regsvr32 commands. Remove the "/S" option from each command line, then save and exit the file. Once this is done, execute test.bat.

Do the dlls register OK? If not, what error message do you receive?

  • If all these fail, the next thing to do is uninstall all SCM components on the computer, reboot, and then reinstall the SCM client from the command line so that we can collect a log file of the installation:
    • On the Windows desktop navigate to Control Panel -> Programs - Select and uninstall "Enterprise Communicator" first
    • When that is complete, then uninstall SCM Client
    • Reboot the computer
    • Open a command prompt window (running as administrator) and navigate to the folder containing the SCM Client's "setup.exe" installation program
    • Execute the following:

setup.exe /qf /v"/l \"C:\Temp\client_install.log\"

Make sure the C:\Temp folder already exists before running the command.  The result should be a client_install.log file containing more information about any problems encountered during installation.

In the end, uninstalling Enterprise Communicator and SCM 64-bit Client, then deleting the CA-related folders and registry entries, rebooting and installing the SCM 32-bit Client resolved the problem.

Additional Information

With the introduction of SCM v14.5, the Administrator Tool has moved to the Eclipse platform resulting in the following changes to the above suggestions:

When running the Administrator Tool from a command prompt use this command instead: 
   "C:\Program Files\CA\SCM\workbench.exe" -data "@user.home/.cascm/workspaceAdmin" -perspective "" -vmargs"C:\Program Files\CA\SCM\adminDropins"

The "RegisterRelease.bat" file is not included in the SCM v14.5 client installation.