Error Messages for the JD Edwards OneWorld System
The following table describes error messages in the JD Edwards OneWorld system, and provides possible corrections for them.
| Error ID | Possible Cause / Error Description | Possible Correction |
|---|---|---|
| E-JDE0002 | JD Edwards OneWorld JAR files missing. Failed to instantiate class object for JD Edwards OneWorld Java Data Bean. |
Verify path for repository. For more information, see Basic Types. |
| E-JDE0027 | JD Edwards OneWorld JAR files missing. Unable to acquire JD Edwards OneWorld connection object. | Verify your CLASSPATH environment variable. See Updating the CLASSPATH. Verify your credentials. For more information, see Basic Types. |
| JD Edwards OneWorld JAR files missing. Wrong path for repository. |
Verify location of jdeinterop.ini. Verify path for repository set in the jdeinterop.ini file. You must copy jdeinterop.ini manually when importing a JD Edwards OneWorld business process to another computer. |
|
| Unable to acquire JD Edwards OneWorld connection object. | Verify your CLASSPATH settings and logon credentials.. | |
| I-JDE0043 | Wrong App Server, Port, Environment, Path for Configuration File, User, Password. Logon failed. |
Verify your logon credentials. For more information, see Basic Types. |
| I-JDE0048 | If the jdearglist.txt file does not exist or is empty, an informational message appears in the log when Microsoft BizTalk Adapter for JD Edwards OneWorld opens. | Update the jdearglist.txt file to enter a list of parameters so that they are automatically right justified and padded on the left with blanks. See Handling String Values. Every time you change the jdearglist, you must regenerate the schemas for that business object. |
See Also
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for