Changing Network Password Causes Application Errors After Client Session Times Out - "Invalid username/password. Please supply correct username/password." Error and NO Window to Enter Values then Crashes with Error Number 2.
(Doc ID 3058801.1)
Last updated on NOVEMBER 15, 2024
Applies to:
Oracle Communications MetaSolv Solution - Version 6.3.1 and laterInformation in this document applies to any platform.
Symptoms
Bug 30394534 was fixed in MetaSolv Solution version 6.3.1.192 to resolve an LDAP/Active Directory user authentication issue where, if they were logged into the application and changed their network password, the application would throw several errors and eventually crash. According to the bug fix, the user should have been prompted to enter their new password in the "Re-enter Password" window. This scenario was tested and the error message indicated the correct password needed to be supplied, but there is no option to enter it. The new behavior is that it keeps throwing the error and attempting to reauthenticate with the original password and. when the user clicks the X to close the application, it crashes with an Error Number 2.
Behavior Manifestation Process
The user logged into MetaSolv Solution, then changed their network password. They let their tbs.exe client session sit idle for 30 minutes to ensure it had timed out. When they resumed activity, they received the error message below. If they hit OK, there was no window to enter the new credentials. The application just looped back to the same window. After 5 attempts, the user clicked the X to close the application before the window came back. It prompted them to save their work and crashed with an Error Number 2.
Error Text (Includes "Details>>>")
Invalid username/password. Please supply correct username/password.
Invalid username/password. Please supply correct username/password.
Crashing Error
Error Number 2.
Error text = Null object reference at line 20 in pfc_default
event of object w_msgwithdetails..
Window/Menu/Object = w_msgwithdetails.
Error Object/Control = w_msgwithdetails.
Script = pfc_default.
Line in Script = 20.
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 |