E1: SEC: Troubleshooting Login Issues on Any Client Due to Security Server Errors
(Doc ID 1394957.1)
Last updated on OCTOBER 03, 2020
Applies to:JD Edwards EnterpriseOne Tools - Version 8.97 and Prior and later
Information in this document applies to any platform.
There are many causes why users are not able to log into the system. This document was created to assist customers in troubleshooting the different scenarios, causes and resolutions for login failures due to Security Server errors which can occur from any client (FAT, thin (TSE), HTML or Web Dev client).
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
|Scenario 1: Error "Cannot Locate Security Server"|
|Scenario 2: Error "Unable to Locate Security Server"|
|Scenario 3: Error "Failed to Communicate with Security Server Unable to Locate Security Server"|
|Scenario 4: Error "SEC0000015 - Unable to Locate Security Server"|
|Scenario 5: Error "Security Server is down or cannot be reached"|
|Scenario 7: Error "Unable to Connect to Security Server"|
|Scenario 8: Error "Unable to locate Security Server"|
|Scenario 9: Error "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'|
|Scenario 10: Error "Unable to Send Message to Security Server"|
|Scenario 11: Error "Mulformat BLOB, unknown encryption type" Starting Security Kernel|
|Scenario 12: Metadata Kernel Unable to Communicate with Security Server|
|Scenario 13: Errors "Unable to locate Security Server" and "Failed to validate user JDE by password"|
|Scenario 14: Errors "ODB0000163 - SQLDriverConnect failure. rc=-1" and ODB0000164 "Login failed for user 'JDE'"|
|Scenario 15: Error "The Security server is down or cannot be reached"|
|Scenario 16 : Intermittent error "Security Server is Down or Cannot be Reached"|
|Scenario 17 : Error ODB0000163 - SQLDriverConnect failure. rc=-1 and ODB0000164 - Communication link failure|