Hi everyone, we have an issue with one of our “After Create” connector rule in the Active Directory source. Since the 25th, the execution was fine, but after that, no sign of any execution in the logs. We have TLS enabled with a self signed certificate and the connection with AD itself works fine…

Hello, just to inform everyone, the issue was resolved with Sailpoint this morning. We had a meeting where we changed the user running the IQService from the “Services” on Windows, with the Admin user. After that we copied the script from the API, re-escaped it using Free Online JSON Escape / Une…

check any non-tls ports are still enabled please, if yes delete/disable IQService.exe -p 0 IQService.exe -p -1 Configuring TLS and Client Authentication for IQService SailPoint Connectors Documentation

Please check the version of the current IQServices and if it is May2025, then it is not supporting non-tls connection. Please refer here New Capability: Integration Service (IQService-May-2025) is now LIVE! Since you already enabled the TLS, follow the link to disable the non-tls communication in t…

Hi, and thanks for the reply. All non TLS ports have been fully removed frtom the configuration.

IQService version is up to date [image]

Hello @antonioantonelli1306 , Can you check the below? Whether Name of Native Rule is correctly configured on the AD source in ISC tenant? If its correct, check if the loggers are getting generated for your After Create. Also, check the IQService loggers. Check whether IQ Service is running on req…

Hi, thanks for your input. All these steps have been already executed with Sailpoint Customer Support, so yes Rule name is correctly configured in the source configuration Logs in the after create are NOT being generated IQService logs show a WARN message saying “Exit code : 1 :” IQService is ins…

Ok! Is anywhere, in any session the log file is still open on IQ Service Box? Also, have you added -Force option while generating the log file in IQ Service Machine? I would also also recommend to put few sleeps before and after calling the Stand Alone Powershell script which your After Create ru…

I would suggest to check few more options, Exit Code:1 occurs majorly due to code syntax. Execute the PS script by using standalone PS command in the server and see whether it throws any error. If not, validate the connector rule by checking the syntax and un-escaping characters in it. Make sure t…

Ok, so PS execution of the script on the Windows machine works flawlessly The account running the IQService is Administrator and is an SVC Same as above Utils.dll was something we checked in the beginning since we had issues with another deployment, and no it’s not locked Execution policy is Remot…

Any idea on what infra should check?

AD After Create Connector Rule not executed

Identity Security Cloud (ISC) ISC Discussion and Questions

antonioantonelli1306 (Antonio Antonelli) August 26, 2025, 3:20pm 5

IQService version is up to date

Topic		Replies	Views
ConnectorAfterCreate Rule No Longer Running Since 7/1 ISC Discussion and Questions rules , identity-security-cloud , connectors	3	121	September 14, 2025
Executing AfterCreateRule following Active Directory Account creation ISC Discussion and Questions rules , identity-security-cloud , provisioning , connectors	18	142	March 19, 2026
IdentityNow After Creation Rule implementation issue ISC Discussion and Questions rules , identity-security-cloud , provisioning , connectors	6	147	August 3, 2025
ConnectorAfterCreate powershell problem ISC Discussion and Questions rules , identity-security-cloud , connectors	5	181	September 6, 2025
ConnectorAfterCreate Rule ISC Discussion and Questions identity-security-cloud	4	181	July 29, 2025

AD After Create Connector Rule not executed

Related topics