I am attempting to integrate the AD domain on SailPoint Sandbox, and while it connects successfully at times, it also experiences intermittent connectivity issues resulting in aggregation errors. The specific error message is: [ERROR for domain - dc=ad1,dc=abacus,dc=corp] sailpoint.connector.ConnectorException: java.lang.Exception: [ERROR 1] Failed to connect to server:ldap://pc1wabaddom11.ad1.abacus.corp:389 - java.net.UnknownHostException: pc1wabaddom11.ad1.abacus.corp [ERROR 2] Failed to connect to server:ldap://pc1wabaddom12.ad1.abacus.corp:389 - java.net.UnknownHostException: pc1wabaddom12.ad1.abacus.corp.
I have enabled scheduled aggregation as shown in the attached screenshot. I have also verified the FQDN certificate and confirmed that there are no issues with the Windows Domain. After consulting with the network team, they have confirmed that the network settings are correct, suggesting that the issue may be related to the Windows environment.
I am seeking suggestions on how to address this problem.
Given that error, I would log into both VAs and do some typical linux command line network testing. sounds like you might have some intermittent latency issues from either or both VAs. During aggregation the aggregation job is placed in the VA cluster queue and one of them takes the work and executes so it may be that one of your VAs has an issue while the other does not giving you the intermittent success and failures or it may be that both VAs are experiencing intermittent latency. while you are in the VAs you can check out the log files in /home/sailpoint/logs
Sure Jeff. i will check the both VA and see if there are having any connection issues as all the other source are connected with the same VA’s it is working fine i will cross check once and update you thank you.
Hello Paulo, I investigated the DNS issue by verifying that the hostname and server on the IQ server are successfully pinged. I have also confirmed that the hostname is pinged from the IQ server to the VA’s. Additionally, I will review the logs in the VA’s folder for further information.
I identified the problem by verifying the entries in both virtual assistants’ hosts.yaml files. Once the issue was identified and resolved, everything was working properly. Thank you for your assistance.
