E1: ESU: CHA: ESU Datasource Created As SSE Rather Than MSDE - FOR SYSTEMS WHERE THE LOCAL DATABASE HAS NOT BEEN UPGRADED FROM MSDE TO SSE
(Doc ID 661966.1)
Last updated on MAY 19, 2018
Applies to:JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.
If a user logs into the DEP* environment (or any non-*PLAN environment) and goes into the Electronic Software Updates application, datasources for new updates will be created with database SSELocal with datasource type X (SSE) even if the system has not be converted to SSE.
The application does give the user an error message alerting them that they are logged into the wrong environment, however, the datasources are already created at that point. When the user logs out and back into the correct environment (PSFTPLAN or JDEPLAN), the database cannot attach and the user is unable to install the ESU patch. The errors in the jde.log are:
3896/5708 WRK:Starting jdeCallObject Wed May 21 20:22:44.385001 MSDEDBAPI.cpp1133 [Microsoft][Microsoft SQL Server Driver][DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. SQLSTATE: 08001 HRESULT:0X80004005 Native Error:17.
3896/5708 WRK:Starting jdeCallObject Wed May 21 20:23:00.417000 MSDEDBAPI.cpp923 MSDE000006 - SQLAttachDatabase failed for 'JJ16120'
The user will also see errors when attempting to go into the P96470 if any of the ESU databases have datasources that are SSE:
- A pop-up box will appear prompting the user for a password for database: EnterpriseOne SSELocal.
- When unable to provide a proper SSELocal password, a pop-up error message, "Unable to connect to EnterpriseOne SSELocal" will appear.
- If you are able to get into the application, the databases associated with the SSE datasources will not appear for the user to Uninstall.
The user must delete the SSE database datasource(s) (see instructions in the Solution section) and log back into PSFTPLAN or JDEPLAN environment to have the datasource(s) be recreated successfully.
This is even more of a problem with Change Assistant as the user may have many ESUs incorrectly updated and Change Assistant does not alert the user that they are logged into the wrong environment.
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