Troubleshooting: Testing JD Edwards EnterpriseOne by Submitting a Report

Issue	Resolution
You get this message: Communication Failure with <server name>	You might see a message referencing an error of 11, indicating a time out occurred because the server was started after the client was run. Try resubmitting the report. A time out might have occurred because of heavy network traffic or server load. Increase the time out value for the JDENETTimeout setting in the [NETWORK QUEUE SETTINGS] section of the jde.ini file on the workstation. The wrong communications port might have been used. Verify that the serviceNameListen value in the [JDENET] section of the jde.ini file on the workstation matches the serviceNameConnect value in the [JDENET] section of the jde.ini on the server. In addition, the serviceNameConnect value in the client jde.ini must match the serviceNameListen in the jde.ini on the server. Other communications problems might exist. Run SERVERADMINISTRATIONWORKBENCH.exe (found in the system\bin32 directory on the workstation). This program displays only the machines on the specified port (also known as service) that are running JD Edwards EnterpriseOne (either client or server). Use this information to track down the problem: If the remote machine is visible, a time-out probably occurred. Rerun the report. If the remote machine is not visible, try to ping the remote machine using the name of the machine. If the ping fails, try to ping the remote machine using its IP address. With this information, determine if the client and server agree on the IP address for the server. If none of these steps identify the problem, a general network error probably occurred (for example, the network is down or a machine is disconnected). Track it down.
The report does not display any data.	No data might exist in the database for the report that you are running, or you do not have access to the data. Try these: Select a different report to verify that some reports do produce data. Verify the database contains data that should be included in the report. Add data if necessary. Change the processing options for the report. Change the OCM and data sources to reference the correct library. If the report is launched on the server, make sure that the vertical tables in the server OCM match those of the OCM for the workstation. If no data is found, it could be because: No data exists. The processing options are incorrect. The OCM for either the client or server is pointing to the wrong data source. The data sources for either the client or server are pointing to the wrong database. The SQL statement is incorrect (possibly due to a program bug). The database drivers are out of date.
The report does not display any data.	An error might have occurred with the report. Review the jdedebug.log and jde.log files for errors.
An error initializing the environment occurs in the log file.	The environment might not be set up correctly: Look for errors in .INI keys or database tables that can cause an initialization failure. Stop JD Edwards EnterpriseOne and determine if the PORTTEST program runs correctly. If not, correct the problems, and then rerun JD Edwards EnterpriseOne manually.
You get this message: Communication Failure with <server name> This error occurs sometimes on the workstation Restarting JDENET_N sometimes gets rid of the error You can ping the server from the workstation	The server might have two network cards, which can confuse JDENET when the net communications are initialized between the client and server. One machine tries to connect using one network card, and the other machine connects using the other network card. The hosts file on the server should list two different IP addresses for the server: one for each network card. The solution for the error involves setting the NetHostName field in the [JDENET] section of the JDE.INI to one of the names for the server given in the hosts file. JDENET then uses the IP address associated with the given network card.