SO many different things could be wrong. Lets try narrowing things down first:
Have you tried any provisioning activities yet? IS the IQservice up and running or is this a read only connector?
@PhilRawlings1 It’s just a read-only connector at the moment.
Cool, that clears out a lot of options.
What’s the ping time from the VA? The test connector can fail whilst aggregations pass if the VA and the DC are far apart
Hi @Santhakumar ,
Can you try disabling “Use TLS” option in both forest and domain settings? As the connector is just read only, I don’t think its required to have that option enabled. Hope the authentication type is simple.
Please compare both source configurations and check the VA/connector logs at the time of the test.
What is the forest topology you are using? Also, any restrictions on the service account to the root of the forest in the failing case (does the aggregation work at a particular OU)?
@JackSparrow Yes i have disabled the TLS everywhere. And authentication type is Simple only.
Hi Shanta,
This means its making the query Read at AD. But the some configuration logic is failing. The reason could be IQService, TLS/LDAPS Certificate Validation. And If its working with another AD source then check all the configuration from there and then try to make it successful.
As other’s have alluded to, there could be a latency that is coming from the Test Connection that is not being seeing in the aggregation.
Are both ADs configured to use the same VAs and IQService?
Are the DCs in the same Datacenter as the VAs?
Are the AD DCs in the same Datacenter?
All of these could affect it.
Both ADs use the same VA but different IQService. Also the DCs are in the same datacenter as VA and AD.
Hi @Santhakumar - if aggregations are working then my guess would be it is the IQService since that is bypassed for reads. Check that the VA can communicate with the IQService. Also double check your IQService config and any network appliances/firewalls that may be along that path for any issues.
Check the logs for more appropriate error.
@Santhakumar check if you can call the below commands
nc -zv -w 5 ip of ad machine 389
Below is the log for the broken Pipe error. Not sure how to fix this.
{“exception”:{“stacktrace”:“sailpoint.connector.ConnectorException: Broken pipe\n\tat com.sailpoint.ccg.cloud.container.Container.testConnection(Container.java:536)\n\tat com.sailpoint.ccg.cloud.container.ContainerIntegration.ping(ContainerIntegration.java:73)\n\tat com.sailpoint.ccg.handler.TestConnectionHandler.invoke(TestConnectionHandler.java:31)\n\tat sailpoint.gateway.accessiq.CcgPipelineMessageHandler.handleMessage_aroundBody0(CcgPipelineMessageHandler.java:45)\n\tat sailpoint.gateway.accessiq.CcgPipelineMessageHandler$AjcClosure1.run(CcgPipelineMessageHandler.java:1)\n\tat org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:167)\n\tat com.sailpoint.tracing.otel.TracedAspect.lambda$traceExecution$0(TracedAspect.java:38)\n\tat com.sailpoint.tracing.otel.GlobalTracer.trace(GlobalTracer.java:170)\n\tat com.sailpoint.tracing.otel.GlobalTracer.trace(GlobalTracer.java:143)\n\tat com.sailpoint.tracing.otel.TracedAspect.traceExecution(TracedAspect.java:40)\n\tat sailpoint.gateway.accessiq.CcgPipelineMessageHandler.handleMessage(CcgPipelineMessageHandler.java:38)\n\tat com.sailpoint.pipeline.server.PipelineServer$InboundQueueListener$MessageHandler.run(PipelineServer.java:402)\n\tat java.base\/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)\n\tat java.base\/java.util.concurrent.FutureTask.run(FutureTask.java:264)\n\tat java.base\/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)\n\tat java.base\/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)\n\tat java.base\/java.lang.Thread.run(Thread.java:840)\nCaused by: sailpoint.connector.ConnectorException: Broken pipe\n\tat sailpoint.connector.ADLDAPConnector.testIQServiceConnection(ADLDAPConnector.java:5113)\n\tat sailpoint.connector.ADLDAPConnector.testConfiguration(ADLDAPConnector.java:5045)\n\tat sailpoint.connector.ConnectorProxy.testConfiguration(ConnectorProxy.java:478)\n\tat com.sailpoint.ccg.cloud.container.Container.testConnection(Container.java:529)\n\t… 16 more\nCaused by: sailpoint.tools.GeneralException: Broken pipe\n\tat sailpoint.connector.RPCService.execute(RPCService.java:562)\n\tat sailpoint.connector.ADLDAPConnector.testIQServiceConnection(ADLDAPConnector.java:5107)\n\t… 19 more\nCaused by: java.net.SocketException: Broken pipe\n\tat java.base\/sun.nio.ch.NioSocketImpl.implWrite(NioSocketImpl.java:425)\n\tat java.base\/sun.nio.ch.NioSocketImpl.write(NioSocketImpl.java:445)\n\tat java.base\/sun.nio.ch.NioSocketImpl$2.write(NioSocketImpl.java:831)\n\tat java.base\/java.net.Socket$SocketOutputStream.write(Socket.java:1035)\n\tat java.base\/sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:234)\n\tat java.base\/sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:313)\n\tat java.base\/sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:318)\n\tat java.base\/sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:160)\n\tat java.base\/java.io.OutputStreamWriter.flush(OutputStreamWriter.java:248)\n\tat java.base\/java.io.BufferedWriter.flush(BufferedWriter.java:257)\n\tat sailpoint.connector.RPCService.writeHeader(RPCService.java:421)\n\tat sailpoint.connector.RPCService.writeRequestToOutputStream(RPCService.java:757)\n\tat sailpoint.connector.RPCService.execute(RPCService.java:539)\n\t… 20 more\n”,“exception_class”:“sailpoint.connector.ConnectorException”,“exception_message”:“Broken pipe”},“stack”:“ccg”,“pod”:“devrel01-useast1”,“connector-logging”:“177”,“Operation”:“TestConfiguration”,“clusterId”:“ac1d3a30fa6d44cbb413878f2d213d65”,“utilities”:“3.16.0”,“buildNumber”:“1312”,“apiUsername”:“2e14338f-12b0-480b-8d78-3b70a08cca15”,“orgType”:“”,“file”:“BaseHandler.java”,“encryption”:“3.16.0”,“messageType”:“test-connection”,“connector-bundle-identityiq”:“307”,“line_number”:333,“@version”:1,“CB_version”:“843”,“cloud-modules-api”:“3.16.0”,“logger_name”:“com.sailpoint.ccg.handler.BaseHandler”,“mantis-client”:“3.16.0”,“class”:“com.sailpoint.ccg.handler.BaseHandler”,“atlas-api”:“3.41.4”,“va-gateway-client”:“67”,“connector-bundle-utilities”:“17”,“tracing”:“3.16.0”,“clientId”:“2e14338f-12b0-480b-8d78-3b70a08cca15”,“request_milliseconds”:“563”,“source_host”:“a221f8771fcd”,“method”:“handleException”,“org”:“devrel-ga-21899”,“level”:“ERROR”,“IdentityIQ”:“8.3p4 Build 894c6bcd4ef-20260218-032501”,“message”:“Exception “,“pipeline”:“3.16.0”,”@timestamp”:“2026-08-24T16:27:16.941Z”,“thread_name”:“pool-5-thread-9”,“commons-lang-bridge”:“106”,“atlas-util”:“3.41.4”,“metrics”:“3.16.0”,“region”:“us-east-1”,“AppType”:“Active Directory - Direct”,“Application”:“SOC AD [source-1787586701384]”,“request_id”:“c4927e5a4260408a8d398f2362b82a64”,“CB_Type”:“connector-bundle-directories”,“queue”:“devrel01-useast1-devrel-ga-21899-cluster-ac1d3a30fa6d”,“SCIM Common”:“8.0 Build 00b1f252d1b-20200225-190809”} {“stack”:“ccg”,“pod”:“devrel01-useast1”,“connector-logging”:“177”,“Operation”:“TestConfiguration”,“clusterId”:“ac1d3a30fa6d44cbb413878f2d213d65”,“utilities”:“3.16.0”,“buildNumber”:“1312”,“apiUsername”:“2e14338f-12b0-480b-8d78-3b70a08cca15”,“orgType”:“”,“file”:“BaseHandler.java”,“encryption”:“3.16.0”,“messageType”:“test-connection”,“connector-bundle-identityiq”:“307”,“line_number”:344,“@version”:1,“CB_version”:“843”,“cloud-modules-api”:“3.16.0”,“logger_name”:“com.sailpoint.ccg.handler.BaseHandler”,“mantis-client”:“3.16.0”,“class”:“com.sailpoint.ccg.handler.BaseHandler”,“atlas-api”:“3.41.4”,“va-gateway-client”:“67”,“connector-bundle-utilities”:“17”,“tracing”:“3.16.0”,“clientId”:“2e14338f-12b0-480b-8d78-3b70a08cca15”,“request_milliseconds”:“563”,“source_host”:“a221f8771fcd”,“method”:“handleException”,“org”:“devrel-ga-21899”,“level”:“ERROR”,“IdentityIQ”:“8.3p4 Build 894c6bcd4ef-20260218-032501”,“message”:“returnMap {result=error, message={ExceptionType=sailpoint.connector.ConnectorException, LocalizedMessage=Broken pipe}}”,“pipeline”:“3.16.0”,“@timestamp”:“2026-08-24T16:27:16.942Z”,“thread_name”:“pool-5-thread-9”,“commons-lang-bridge”:“106”,“atlas-util”:“3.41.4”,“metrics”:“3.16.0”,“region”:“us-east-1”,“AppType”:“Active Directory - Direct”,“Application”:“SOC AD [source-1787586701384]”,“request_id”:“c4927e5a4260408a8d398f2362b82a64”,“CB_Type”:“connector-bundle-directories”,“queue”:“devrel01-useast1-devrel-ga-21899-cluster-ac1d3a30fa6d”,“SCIM Common”:“8.0 Build 00b1f252d1b-20200225-190809”}`
Able to see connection succeded.
