E1: SEC: Troubleshooting Login Errors From HTML or FAT Clients
(Doc ID 1405874.1)
Last updated on AUGUST 01, 2023
Applies to:
JD Edwards EnterpriseOne Tools - Version 8.98 and laterInformation in this document applies to any platform.
Purpose
There are many causes why users are not able to login to EnterpriseOne from their client workstation. This document has been created to assist customers in troubleshooting the different scenarios, causes and resolutions for a user login failure.
Troubleshooting Steps
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
| Purpose |
| Troubleshooting Steps |
| Login Errors on the Web Client |
| Scenario 1: HTML/Web Users Are Unable To Login Due to Security Error in Log |
| Scenario 2: Error "F98PWPURequest" When Logging into HTML Client |
| Scenario 3: Errors "Table Not Found", SQL0901 and SQL0913 When Users Login to HTML Client |
| Scenario 4: Sign in Error: An unknown JAS error occurred |
| Scenario 5 - Unable to login to EnterpriseOne "An unknown JAS sign in error occurred" |
| Scenario 6: Unable to sign-in to EnterpriseOne and error of "Sign In Error: User sign in has been disabled. Please contact the System Administrator" |
| Login Errors on the Fat Client |
| Scenario 1: Unable to Login Error: RetrieveUserInformation was not found |
| Scenario 2: Error "error opening F98MOQUE table" When Logging into Client |
| Scenario 3: Database Password Entry and Login failed for user 'sa' |
| Scenario 4: Error "F98PWPURequest" When Logging into the FAT Client |
| Scenario 5: Error Logging into EnterpriseOne 8.12 on any Client |
| Scenario 6: Error "No role associated with the *ALL" when Users Login |
| Scenario 7: Error "KNT0000032 - InitEnv on Server Failed" When Users Login |
| Scenario 8: Users get Database Entry Password Pop Up |
| Scenario 9: Unable to sign-in to EnterpriseOne and error of "Sign In Error: User sign in has been disabled. Please contact the System Administrator" |
| Scenario 10: Unable to sign-in to EnterpriseOne using any E1 username and the popup to enter user and password for database also appears. |
| References |