Using the PORTTEST Checklist
If the PORTTEST program fails to run, use this checklist to diagnose the problem before calling Global Customer Support. Please have the answers to these questions as well as copies of error messages, your Enterprise Server, and any error logs, such as JDE.log or JDE_xx.log.
PORTTEST may fail if replication, security server, or transaction processing have been installed incorrectly. If problems occur after the installation of one or more of these services, check the setup of those services for incorrect parameters.
PORTTEST will also fail if the Enterprise Server does not have an appropriate 32-bit database client installed. Refer to the chapter of this guide entitled: Working With the Enterprise Server in the section entitled: Installing a 32-bit Database Client.
Additionally, if PORTTEST reports warnings that indicate data dictionary or company constants are invalid, it may be because the F0010 table is empty. As is true with the full JD Edwards EnterpriseOne installation, this is a normal condition in Pristine and Production environments.
General Issues |
Yes\No |
|---|---|
Is the user logged on with administrator privileges? |
|
Is the JDENET Service starting with a network domain user? |
|
Is the JDENET Service account included in the local administrator group? |
|
Are all the environment variables set? |
|
Is the C compiler installed with Unicode module? |
|
Can you query the database on the Enterprise Server? |
|
Is a PostScript or PCL printer connected to this machine? |
|
Are the printer drivers for this printer installed? |
|
Is this printer configured as the default printer? |
jde.ini Issues |
Yes\No |
|---|---|
Is your jde.ini located in the correct directory? |
|
Does your jde.ini have the correct permissions? |
|
Are the following jde.ini parameters set properly? |
|
[Network Queue Settings] Default Printer OUTQ=your printer |
|
[UBE] If you use PostScript, is the correct filter set up? |
|
[DB System Settings] Verify all parameters, especially the following: Default Env= your default environment Default Pathcode = your default path code Server = database server name |
|
[JDENET] serviceNameListen = port number serviceNameConnect = port number |
|
[INSTALL] E920=your path |
Communications Issues |
Yes\No |
|---|---|
Do the Development Clients and server agree on the IP address of the server? |
Other Issues |
Yes\No |
|---|---|
Were your server map tables (F98611 and F986101) edited properly? |
|
Run the Verify OCM application and verify: |
|
Do only host databases exist? |
|
No entries for batch applications exist. |
|
Are OneWorld tables accessible to the host? |
|
Can you query the F0902 table? |
|
Does PORTTEST run without error for each valid path code? |
|
Does the user name match that of a valid Release 9.2 account? Remember that the user name is case sensitive. |
|
Is the password valid for the given Release 9.2 account? |
|
Does the environment name match a valid Release 9.2 environment? Remember that the environment name is case sensitive. |
|
Does JDENET start and stop properly? |
If you answered no to any of these questions, your batch application might not run. If you answered yes to all the questions, submit a batch application now.
If your batch application does not run correctly, turn on error logging and resubmit the batch. This log helps Global Customer Support diagnose the exact problem.