Do you have any jobs running? You can check the same in monitor tab. Recently we have seen this issue where WPS job is running which is updating bunch of details to Servicenow as part attribute sync. This caused timeout issue for the timebeing.
For AD connector failures, usually you can check following:
- VA is active and stable in the VA cluster - you should be able to see this on the Org/Tenant
- Connection between VA and IQ service is stable - you can check this on the CCG logs on VA. If required, you can enable the debug logs for AD connector for this.
CCG Enable Debug Log by Connector - Compass - Connection between IQ service and AD domain controllers is stable - you can check this on IQ service logs on IQ server.
Is this the first time you are connecting?
Hi @AmolGachande,
If you’re connecting it for first time this could be firewall port which VA won’t allow for outbound connection.
Regards,
Vasanth
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.