Troubleshooting Testing JD Edwards EnterpriseOne by Submitting a Report

• If a time-out occurred because the JD Edwards EnterpriseOne server was started after the client, resubmit the report.

• If a time-out occurred due to heavy network traffic or server load, increase the time-out value in the jde.ini file on the workstation and resubmit the report.

  Use the JDENETTime-out setting in the [NETWORK QUEUE SETTINGS] section.

• If the wrong communications port is being used, perform one of these tasks:

  • 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 file on the server.

    In addition, the serviceNameConnect value in the jde.ini file on the workstation must match serviceNameListen in the jde.ini file on the server. If the values of these keys are strings, the numeric value is retrieved from the services file in the c:\winnt\system32\drivers\etc directory (Microsoft Windows: client or server).

  • The services file contains a list of strings and their corresponding port numbers.

    If the port that you are interested in is on the last line of the services file, be sure to include a return at the end of the line or else the string will not be translated to the corresponding port number.

• If the client is using Dynamic Host Configuration Protocol (DHCP) and the server does not have an entry for itself in its hosts file in the c:\winnt\system32\drivers\etc directory, add an entry for the server in the hosts file on the server.

• These situations can occur:

  • Communications failure error message on the workstation.

  • Restarting Network Service or jdenet_n sometimes gets rid of the error.

  • You can ping the server from the workstation.

  These issues can occur because the server has two network cards, which confuses 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. Resolve the error by 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.

• For the error cannot connect to printer in the jde_xxx.log or the log file in the PrintQueue subdirectory:

  • If a general printing error occurred, try to print a text document from Notepad.

    Resolve any issues.

  • If no default printer is set up on the enterprise server, see Overriding Printer Location for Jobs.

  • If you do not have privileges to the printer, define the owner as a local or network account.

    The type of account depends on the type of printer. If the printer is a local printer, the owner could be either a local or network account but either type must have privileges to access the printer. If the printer is a network printer, the owner must be a network account with access privileges.

• All jobs sent to this printer using the current server will conform to the selected orientation.

  Note that the report template or other programs may override this default orientation. If you cannot change the printer orientation, you may not have the right to change the orientation. Log on to Microsoft Windows in an account that has administrative rights for the printer. For a local printer, use an account that has administrative privileges. For a network printer, use an account given administrative privileges by a network administrator.

  If the report does not list any data, the data may not exist in the database for the report that you are running, or you do not have access to the data. Perform one or more of these tasks to resolve the data issue:

  • Select a different report.

  • Add data to the database.

  • Change the processing options for the report.

  • Change the OCM and data sources to point to the correct database.

• If the report is launched on the server, verify the vertical tables in the server OCM match those in the workstation OCM.

  If you believe data should have been found, edit the report jdedebug.log found in the PrintQueue subdirectory.

  Search for the SQL select statement used to retrieve data from the database. You must have some idea what data is being read to do this.

  • Copy the SQL statement.

  • Open the specific database SQL command interface - for example, SQL Plus or ISQL_w.

  • Paste the SQL statement into the SQL command interface.

  • Submit the SQL statement.

• If no data is found, one of these conditions may be true:

  • 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.

  • If an error occurred with the report, look in the jde_xxx.log for error messages.

• If an error initializing the environment occurs in the log file, the environment may not be set up correctly.

  Stop JD Edwards EnterpriseOne and determine if the PORTTEST program runs correctly. If not, correct those problems and then run JD Edwards EnterpriseOne manually.