Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

AD Account Import Job: Failed Status and Warning Message after Upgrade to V23.5

Nagendra
New Contributor II
New Contributor II

The AD Account import job is displaying a failed status, although the accounts are being imported successfully. However, a warning message stating "Warning StatusThresholdConfig Validation: statusColumn [CUSTOMPROPERTY30] is invalid in STATUS_THRESHOLD_CONFIG" is encountered.

This issue started occurring after upgrading to version 23.5. Are there any other users experiencing the same problem or were there any specific changes made in the update?

Could you please provide information on how to resolve this issue?

6 REPLIES 6

khalidakhter
Saviynt Employee
Saviynt Employee

@Nagendra 

As per the warning message, it seems like the AD connector is not able to find the mapping for CP30 in the ACCOUNT_ATTRIBUTE mapping JSON. 
Please check if the ACCOUNT_ATTRIBUTE JSON contains the mapping for CUSTOMPROPERTY30 with the userAccountControl column if the target application is Microsoft Active Directory.

vivekmohanty_pm
Saviynt Employee
Saviynt Employee

@Nagendra can you please share your ACCOUNT_ATTRIBUTE and STATUS_THRESHOLD_CONFIG?

@vivekmohanty_pm  Please find below  attached file for  Account attribute and status threshold config.

 

vivekmohanty_pm
Saviynt Employee
Saviynt Employee

@sureverma @Nagendra Please mention the customproperty30 in all lower-case.

{
"statusAndThresholdConfig": {
"statusColumn": "customproperty30",
"activeStatus": ["512", "544", "66048", "66080", "262656", "262688", "328192", "328224", "590336", "16843264", "2080", "2163200", "4260352", "1049088", "ACTIVE"],
"deleteLinks": false,
"correlateInactiveAccounts": true,
"inactivateAccountsNotInFile": false,
"accountThresholdValue": 5000
}
}

Regards,
Vivek Mohanty

Nagendra
New Contributor II
New Contributor II

@vivekmohanty_pm  Thanks for your reply. The issue got resolved after updating the CP30 in lowercase.

vivekmohanty_pm
Saviynt Employee
Saviynt Employee

@Nagendra Please click the Accept As Solution button on my previous message to help future users who may have a similar problem.