After upgrading to SCM v14.5.01, when testing the SCM Workbench and Administrator Tool applications installed on the broker machine, we were unable to connect to the broker.
Harvest Software Change Manager all versions
Here are the initial things to check:
CA_SCM_HOME=C:\Program Files\CA\SCM
CA_SCM_LOCALHOME=C:\Program Files\CA\SCM
HARVESTHOME=C:\Program Files\CA\SCM
LOCALHARVESTHOME=C:\Program Files\CA\SCM
RTARCH=i86_w64
RTHOME=C:\Program Files (x86)\CA\SharedComponents\PEC
C:\Program Files (x86)\CA\SharedComponents\PEC\bin;
C:\Program Files\CA\SCM\x86;
C:\Program Files\CA\SCM;
C:\Windows\system32;
C:\Windows;
C:\Windows\System32\Wbem;
C:\Windows\System32\WindowsPowerShell\v1.0\;
cd %CA_SCM_HOME%
workbench.exe -data "@user.home/.cascm/workspaceAdmin" -perspective "com.ca.harvest.ui.harvestAdminPerspective" -vmargs -Dorg.eclipse.equinox.p2.reconciler.dropins.directory="%CA_SCM_HOME%\adminDropins"
cd %CA_SCM_HOME%
workbench.exe
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.
It is very important that all installation activity for the Harvest product be done on the Windows operating system with a userid that is a member of the local Administrator group, and that all Harvest-related processes, including the "rtserver.exe" process be shut down before installing and uninstalling.