E1: SCHED: Scheduler Password Gets Corrupted When Changing Parameters For A Scheduled Job.
(Doc ID 2952685.1)
Last updated on DECEMBER 26, 2023
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
Scheduler password gets corrupted after changing other parameters in a scheduled job.
- Create a E1 scheduler job for any UBE like R0010P.
- As a simple test, type in an incorrect password for the Scheduled User first time.
- Verify the password field displays an error message.
- Correct the password, and then save the new E1 scheduler job.
- Click "Advanced Options" in "Row Exit" for the new E1 scheduler job just created.
- Click "Batch Application Override" tab and choose a different "Job Queue".
- Click "OK".
- Save the change you made not receiving any error message about the password.
- Wait until the time the new E1 scheduler job is configured to launch.
The new E1 scheduler job will fail to launch because of the bad password.
jdedebug.log shows:
E1 Scheduler Application should not update the password of Scheduled User, or the Application should warn a user to re-populate the Scheduled Password field again.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |