Troubleshooting General Problems

You can troubleshoot general enterprise server problems using the Server Manager which enables you to monitor server components, processes, and resources.

To troubleshoot general problems:

Use Server Manager to verify that you are looking at the correct port and the server is operational on that port.
Verify the netTrace setting in the enterprise server jde.ini file:
```
 [JDENET]
```
```
netTrace=0/1 (disabled/enabled)
```
When the variable netTrace=0, JD Edwards EnterpriseOne does not generate Net log information. When netTrace=1, JD Edwards EnterpriseOne generates Net log information.
Note: Using Server Manager, you can turn logging on or off for a particular kernel process.
Return to JD Edwards EnterpriseOne and duplicate the problem.
The trace facilities write debugging information to the jde.log and jdedebug.log files.
After running the business function again, look at the jde.log files on the server.
Search for these message (you must search for lower case): "jdenet_n process."
If you cannot find this message, bring the server down and back up. If you do find this message, look at the jde.log file with the same process ID as the net process.
Verify that the user is running in the correct environment or path code; for example PD920 or DV920.
If this environment is not set up on the server, you receive errors on the workstation jde.log as well as the enterprise server jde.log.
In the jde.logs on the enterprise server, look for a JDENET_SendMSg Failed Error=12 message.
This message means that the JDENET server is down and you must restart it.
In the jde.log file on non-IBM i enterprise servers, look for any "Unable to connect to Oracle" messages. Search on ORA-.
If you find messages, they indicate problems connecting to Oracle. You get an indication of an Oracle connection problem if, in a business function, you select find/browse, data is not found, and no errors are received from the application. You need help from an Oracle database administrator at this point. To debug this problem, see the section in this document about sql.log.
Look in the jdexxx.log file (where xxx is the ID of the process that created the log) on the server for these message: "Could not find symbol in the <BSFN dll name>."
If present, this message might mean that the business function did not build on the enterprise server.
If you have not found a problem indicating why you are unable to run an application on the enterprise server, you will need to debug it on the server.
Note: For Microsoft Windows enterprise servers, if you cannot identify a problem by reading the log, you need to put the business function through debug on the server. This action requires knowledge of C++ and how to debug. See Microsoft documentation for Debugging C++.