Ldap client timeout

nicholas sinclair said:

Trying to test 20.11.1 Migrator Pro for AD in a non-prod environment and I am receiving the below error message almost every time I try to run a pull job to my target domain:

"Error"        "LDAP Exception: The operation was aborted because the client side timeout limit was exceeded.  ErrorCode: 85"

This error appears after exactly 2 minutes from when the query begins. I have been unable to find a reference to this timeout in the Quest documentation, in the application itself, in config files or registry settings. I have tested changing the ldap policy timeouts on the target domain DC as well, along with a number of application server OS settings, but this always happens at 2 minutes regardless of the changes I make. Is there a way to change this timeout in the application, or does anyone know where this timeout is coming from?

Also note, I've only been able to get past this timeout once, when the app was able to create ~200 users on the target domain before hitting this timeout. I had to recreate the sync profile 6 times with the exact same settings for this to work once.

The LDAP Exception with error code 85 indicating a client-side timeout is likely due to a timeout setting within the application or environment that isn't directly visible in the usual configuration files. Since you’ve already adjusted LDAP policy timeouts and OS settings without success, it’s worth checking the application-specific settings or contacting Quest support for detailed assistance. jannat ke pattay novel