Data Protection Advisor (DPA): DPA agent failed to register to Application Server with exception.name_conflict error

New installed DPA agent fails to register to the DPA Application Server. Within the dpaagent.log, the following error indicates the registration fails due to name conflict:      
However, the above error does not provide the exact conflict name, even with agent debug low level enabled.

The agent registration failure is caused by name conflict as seen in dpaagent log. Once the hostname which is causing the conflict is removed the agent is able to successfully register with the DPA Application server.

The conflict name is not be found in dpaagent log, even with debug low level enabled, as the DPA Application Server tracks this information. To determine the conflict name and resolve the issue, follow the below steps:      

1. Access the DPA Application Server and navigate to the server.log under <DPA install dir>/services/logs/.
2. In the server.log, search for keyword "Node already found". Something similar to the below should be seen:      

3. Go to DPA GUI > Inventory > Object Library > Hosts tab and search for host YYYYYY.
4. Select host YYYYYY's properties > Aliases section and look for the conflict name XXXXXX.
5. Make a copy of all the Alias names in case there is an issue.
6. Select alias name XXXXXX and click Delete.
7. Click Apply, then OK.
8. Restart the DPA agent which failed to register, and it should be able to register to DPA Application Server.

If the agent continues to fail to register, review an updated agent log as a different error or issue may now be occurring. It is possible there may be an additional name conflict error which must be resolved using the above steps.

Contact Dell EMC Technical Support Team for further details or information.