and more in a single search tool across platforms. Read the announcement here. |
11/01/2022 06:32 AM
Hello,
Our Provisioning Jobs are failing (for at least two different security systems) with the following error and all associated Pending Tasks remain to be Pending even after the Provisioning Job ends as "success" under Job Control Panel.
There seems to be a connection error following a getToken call. Any advise on why this is happening and where this could possibly be configured would really help us troubleshoot this further.
----- ATTACHED FULL WSRETRY LOG EXCERPT -----
Solved! Go to Solution.
11/01/2022 06:45 AM
11/01/2022 06:50 AM
Hello Rushikesh,
Thanks for the quick response.
Thanks,
Maruthi
11/01/2022 06:53 AM
Which connector ?
Does connector have createAccountJSON
Does any comments visible under tasks after provisioning job executed ?
11/01/2022 06:57 AM
This is a DB connection. We have following CREATEACCOUNTJSON
{
"createaccountqry": "Insert into targetusers (FirstName,LastName,EmailAddress,Username) values ( '${user.firstname}', '${user.lastname}', '${user.email}','${user.username}')";
}
No Provisioning Metadata or Comments were present (attached screenshot)
11/01/2022 09:31 AM
createAccountQry
{
"createAccountQry": "Insert into targetusers (FirstName,LastName,EmailAddress,Username) values ( '${user.firstname}', '${user.lastname}', '${user.email}','${user.username}')";
}
11/02/2022 03:05 AM - last edited on 11/02/2022 11:23 AM by Dave
Hello Rushikesh,
We tried using createAccountQry and are still seeing the same errors when provisioning job is run.
Please note that when we turn on instant provisioning, accounts are getting created on target system. But, whenever we have pending tasks (instant provisioning is turned off) & when we run WSRETRY job, we don't see any outcome and see the following errors
11/02/2022 11:28 AM
java.net.ConnectException: Connection timed out
You have connectivity issue.
11/11/2022 06:29 AM
Hello Everyone,
The issue got resolved. We had an issue with SC2 Connect. Hence the below message in logs before the error.
DEBUG externalws.ExternalConnectorService - Preparing POST call - POST http://192.168.255.2:4444/connect2/api/login HTTP/1.1