The first suggestion is to verify that DM Primer is actually installed on the non working Scalability Server, there are few ways to see this, first is to go to Apps section (under Control Panel) and check if it exists or not. If it exist, it may means that the version of DMPrimer is different than the DM, so would be good to uninstall it using this command:
MsiExec.exe /X {A312C331-2E7A-42E1-9F31-902920C402EE} /qn /norestart Then re-deploy the whole SS package to this server (from Deployment Wizard), but using the options "REINSTALL=ALL REINSTALLMODE=vomus" on 'Additional Windows Option', as a way to tell the installer to perform a full installation of the package, as explained here:
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/business-management/clarity-client-automation/14-0/implementing/post-installation-tasks/upgrade-an-installation.htmlIf this doesn't work, the SS can be re-register against the DM following these commands:
cserver unregister
caf setserveraddress localhost
cserver config -h <FQDN of Manager> -j
cserver register -a