ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Client Automation - Error "Selected machine is not a Scalability Server" seen on Deployment Wizard.
Article ID: 187194
Updated On:
Products
CA Client Automation - IT Client Manager
CA Client Automation
CA Client Automation - Software Delivery
Issue/Introduction
On Deployment Wizard, while selecting an existing Scalability Server as a source of staged package, after a short loading the following message is shown:
"Selected machine is not a Scalability Server"
The Scalability Servers works fine in any other way, this is the only place where an error or problem is seen.
Cause
Comparing DM Deploy logs while selecting the non working Scalability Server and a working SS, the following can be seen:
- Non working SS (server1):
|INFO | CCFOSGeneral::GetNameFromAddress: 10.20.30.40 resolved to: server1.domain
|DETAIL | isTargetDownV4 - sending echo request for <10.20.30.40>/ID 1
|DETAIL | isTargetDownV4 - echo reply recv'd from 10.20.30.40
|DETAIL | DmIpPing: TARGET IS UP
|DETAIL | Connected to CAM server.
|DETAIL | CAM queue name is CAI014596-00020
|DETAIL | Connected to CAM server.
|DETAIL | CAM queue name is CAI014596-00021
|WARNING| CAM server reachable but application is not connected.
- Working SS (server2):
|INFO | CCFOSGeneral::GetNameFromAddress: 10.50.60.70 resolved to: server2.domain
|DETAIL | isTargetDownV4 - sending echo request for <10.50.60.70>/ID 1
|DETAIL | isTargetDownV4 - echo reply recv'd from 10.50.60.70
|DETAIL | DmIpPing: TARGET IS UP
|DETAIL | Connected to CAM server.
|DETAIL | CAM queue name is CAI014596-00012
|DETAIL | Connected to CAM server.
|DETAIL | CAM queue name is CAI014596-00013
|DETAIL | CAM queue DMPRIMER on host 10.50.60.70 is running or startable
On the working Scalability Servers scenario, the Domain Manager is able to connect to its DM Primer, but on the non working Scalability Server, it's unable to.
This is the cause of the error, in order to use Deployment Wizard, DM Primer has to be installed on the target Scalability Server.
- Non working SS (server1):
|INFO | CCFOSGeneral::GetNameFromAddress: 10.20.30.40 resolved to: server1.domain
|DETAIL | isTargetDownV4 - sending echo request for <10.20.30.40>/ID 1
|DETAIL | isTargetDownV4 - echo reply recv'd from 10.20.30.40
|DETAIL | DmIpPing: TARGET IS UP
|DETAIL | Connected to CAM server.
|DETAIL | CAM queue name is CAI014596-00020
|DETAIL | Connected to CAM server.
|DETAIL | CAM queue name is CAI014596-00021
|WARNING| CAM server reachable but application is not connected.
- Working SS (server2):
|INFO | CCFOSGeneral::GetNameFromAddress: 10.50.60.70 resolved to: server2.domain
|DETAIL | isTargetDownV4 - sending echo request for <10.50.60.70>/ID 1
|DETAIL | isTargetDownV4 - echo reply recv'd from 10.50.60.70
|DETAIL | DmIpPing: TARGET IS UP
|DETAIL | Connected to CAM server.
|DETAIL | CAM queue name is CAI014596-00012
|DETAIL | Connected to CAM server.
|DETAIL | CAM queue name is CAI014596-00013
|DETAIL | CAM queue DMPRIMER on host 10.50.60.70 is running or startable
On the working Scalability Servers scenario, the Domain Manager is able to connect to its DM Primer, but on the non working Scalability Server, it's unable to.
This is the cause of the error, in order to use Deployment Wizard, DM Primer has to be installed on the target Scalability Server.
Environment
Client Automation - All versions
Resolution
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.html
If 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
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.html
If 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
Feedback
Yes
No
Powered by
