Resolving the integration error "Invalid server name. Please try again with a different server name"

Resolving the integration error "Invalid server name. Please try again with a different server name"

Issue description   

The Invalid server name. Please try again with a different server name error appears on the integration configuration page when trying to integrate ADSelfService Plus with one of the following applications:
  • ADManager Plus
  • ServiceDesk Plus
  • Splunk
  • Syslog
  • Log360
  • ServiceDesk Plus
  • Have I Been Pwned
This error prevents successful integration and may disrupt workflows dependent on ADSelfService Plus integrations.

Possible cause 

  • The server name specified during integration cannot be resolved by the machine hosting ADSelfService Plus. This typically indicates a DNS resolution issue or incorrect server entry.

Prerequisite   

  • Have administrator access to the ADSelfService Plus server.

Resolution  

Step 1: Check network connectivity
  • Ensure that the ADSelfService Plus server and the target application server are on the same network (for on-premises products).
  • If integrating with a cloud product, confirm that the ADSelfService Plus server has uninterrupted internet access.
 
Step 2: Verify the server name or IP address
  • If only the IP address is known, update the hosts file to map the IP address to the server name.
  • Open Notepad as an administrator and edit the file located at C:\Windows\System32\drivers\etc\hosts.
Example entry:
192.168.1.10   servername

Step 3: Test DNS resolution
Use PowerShell commands to verify name resolution:
Test-Connection <servername>
Resolve-DnsName <servername>

Step 4: Retry integration
Once connectivity and DNS resolution are confirmed, reconfigure the integration with the correct and reachable server name.

How to reach support             

If the issue persists, contact our support team here

                  New to ADSelfService Plus?