When trying to make a connection to a new Agent machine, the user is getting the following error:
Unable to connect to Agent "agent- servername" Agent login failed. Error code: -301
CA Harvest SCM all versions and platforms
This error can happen for a variety of reasons. Some things to check are:
- Do the SCM Client (workbench) and SCM Agent have the same version of SCM and of PEC?
- Can the SCM Client machine successfully ping the SCM Agent machine?
- Can the SCM Client machine successfully telnet to the SCM Agent machine on the Agent’s listening port? (Most Windows machines have disabled telnet, but if you have “Putty” installed you can do this telnet test with that utility.)
- Is there a network firewall between the SCM Client machine and the SCM Agent machine?
- Is there any other application on the SCM Agent machine that uses the same port?
Depending on the checklist above, resolve whatever problems you find. In particular:
- Check to make sure the SCM Client and SCM Agent are the same version. If not, uninstall and reinstall the component whose version is incorrect.
- Check to make sure that the SCM Client machine can resolve the SCM Agent’s machine name to the correct IP address. If it does not, you will need to update your network’s DNS directory or update the C:\Windows\System32\drivers\etc\hosts file.
- Check to make sure the SCM Client can connect to the SCM Agent machine using the SCM Agent’s listening port. If it cannot, check with your Network administrator to assure the SCM Agent’s listening port is open in the firewall.
- Check to make sure no other application on the SCM Agent machine is using the same port number as the SCM Agent. If you find this situation, either the SCM Agent or the other application will have to use a different port.
More information on configuring communication between SCM Components can be found in the CA Harvest SCM Implementation Guide
As always, please contact CA Technologies support for CA Harvest SCM if you have further questions.