Understanding Microsoft Windows Enterprise Server Troubleshooting

This section discusses some typical problems that you might encounter and their solutions. When troubleshooting, follow these guidelines:

• Narrow the definition of any problem that you might have, particularly when communicating the issue to someone, such as JD Edwards Worldwide Customer Support Services.

  For example, rather than reporting that the batch application failed, explain how the batch application failed. The more specific the information, the faster the problem can be solved. For example, rather than reporting that "The report had the wrong data," say that "The batch status is E."

• When communicating an error message to someone, be sure to include all parts of the error message exactly as they appear in the log file or on the screen.

  Parts of the message that may not seem important may actually hold the key to why an error occurs. Also, distinguish between characters that might be misinterpreted (for example, the capital letter O and the number 0).

• As soon as you notice an error, examine the log files.

  Messages near the end of the log files sometimes reveal the most important information about the cause of the error.

• Before you restart JD Edwards EnterpriseOne on the server, either delete or move the jde_xxx.log and jdedebug_xxx.log files (where xxx is a number).

  Do not rename the log files; it is easier to work with logs that use the standard naming convention (jde_xxx.log and jdedebug_xxx.log). If you need to save the log files until the problem is solved, create a temporary directory and move the files there.

• Clear the log directory regularly to avoid filling the file system. If the file system fills up, the specification files become corrupt.

• Always keep a backup of the specification files in case they become corrupt.

  Specification files should be backed up regularly for easy recovery of spec installs. If specification files have to be replaced, all specification installations are lost unless backups are kept.

  Note: To complete the resolutions provided for these issues, you must sign on to the Microsoft Windows enterprise server using an account that has administrative privileges.