-
Title
Post Release Reset Canceled Not submitted - an earlier reset is already scheduled -
Description
Scheduled password resets fail with a message similar to below, however a manual (forced) password reset works as expected.
5/11/2012 8:07:45 AM The process to change the password for <> on <> timed out after 20 seconds
5/11/2012 8:07:25 AM Password Change process for<> on <>started...5/10/2012 8:10:35 AM Post Release Reset Canceled Not submitted - an earlier reset is already scheduled
-
Cause
The scheduled password reset did not complete in the given timeout period of 20 seconds (default timeout in TPAM)
-
Resolution
Increasing the "Connection Timeout" on the Connection Tab to something greater than 20 seconds allows the connection and password reset. Support recommends at least 45 seconds for Windows systems, but this can change depending on the environment.
When Password Management = None, PPM functions use the System's connection timeout value as no automatic processing occurs.
Log into /TPAM - Systems, Accounts & Collections - Systems - Manage Systems - Select the System to change - Connection Tab - Increase the Connection Timeout based on the environment and platform.
When Password Management = Automatic, PPM functions use the connection timeout in the Password Profiles settings.
Instructions for this are found in this KB: Connection Timeout set on system is not honoured by "Reset Password" in 2.5.915 and above