Recover Lost or Corrupt Password in E1 Local (OEE) Database

One of the standard errors while running JD Edwards EnterpriseOne Standalone Demo is - “Unable to Locate Security Server”.
But what when  you get that error after 6 or odd months when your standalone was working perfectly fine?

Our JD Edwards EnterpriseOne Standalone Demo 9.0.2 or 9.0 or prior running on Oracle Database will cease to work after 6 months. This is due to the Oracle Database Password Expiration policies, which just expires the passwords. You can verify this in your JDE.LOG files, which would say Unable to logon – Password Expired.

The issue above can also occur in one of the following situations:

• If the Deployment Server or FAT client is replaced with a new hardware or hard drive after a crash or as part of an upgrade.
• If the SYSTEM/SYS password of the Local Oracle database is not getting encrypted for some reason and there are errors in C:\ReconfigureMSDE.log

Thankfully, Oracle has a solution to fix this. This applies to JD Edwards EnterpriseOne Tools – Version: 8.98 (Oracle Support ID: 1064181.1). Here are the steps to connect to the Local Oracle (OEE) database with NT administrator credentials. Once connected as an admin, then simply reset the SYSTEM/SYS password.

1. Navigate to the OEE directory and locate the sqlnet.ora file. It should be located in the path
   E1Local\network\admin.
2. Change this file (sqlnet.ora) and set SQLNET.AUTHENTICATION_SERVICES=(NTS).
3. Restart the OEE E1Local instance.
4. Login to the machine with an administrator account.
5. Connect to the local database using “sqlplus / as sysdba”.
6. Run the SQL command:  Alter user system identified by admin;
7. Now exit sqlplus and run ReconfigureMSDE.exe (at system\bin32). You will now be able to encrypt the password for SYSTEM/SYS.
   Enter “admin” without quotes in the Change from password, and set the To password to Encrypted E1 Password.
   
8. Go back and disable the NT authentication in OEE by setting the SQLNET.AUTHENTICATION_SERVICES=(NONE) in the same sqlnet.ora.
9. Restarting the E1Local instance is required.

Once this is done, you will be able to access / login to your JD Edwards EnterpriseOne Standalone.