-
Title
LDAP directory mapping: "Delaying further processing for 24 hours due to error" -
Description
The TPAM LDAP Directory Mapping shows error: "Delaying further processing for 24 hours due to error"
-
Cause
This error means there was an problem accessing the LDAP directory, it can occur when the functional account for Active Directory is incorrect (Perhaps there is a mismatch on the password or username supplied for the functional account compared to Active Directory.) This can also error when if the LDAP system is not operational, or the DN set does not exist. -
Resolution
1. Review the logs in /admin | System Status/Settings | Agents | Auto Discovery | Agent Log around the same time as the delayed error.
2. Verify that the entered credentials are valid by using the "Test System" button:- Click "Systems, Accounts & Collections" tab; click "Systems | Manage Systems". Click "Listing" tab. Highlight the AD System in question. Verify that the platform is "Windows Active Dir".
- Highlight the AD System in question, and click the "Test System" button at the bottom of the page.
When the results are returned, please look for a line that reads either: "Logon failure: unknown user name or bad password." or "The test of system [your_domain_controller] was successful." If successful, this test is complete.If a logon failure is repeated, please verify the results under the "Connection" tab for the Windows AD System in question. The log may point towards the cause of the error - verify the functional account name and password details specifically.
Correct any errors and repeat the test.
3. From /tpam via Auto Discovery | Source | Select each Distinguished Name in the List and click on the "Validate selected DN and filter" tick button in order to verify.
After any authentication issues have been corrected, starting and stopping the Auto Discovery Agent (under '/admin' via "System Status/Settings | Agents | Auto Discovery") should trigger outstanding LDAP Mappings to run.