My Oracle Support Banner

E1: KER: Troubleshooting Known Issues on PORTTEST and Network Services During an EnterpriseOne Installation (Doc ID 1547883.1)

Last updated on OCTOBER 23, 2023

Applies to:

JD Edwards EnterpriseOne Tools - Version SP24 and later
Information in this document applies to any platform.



PORTTEST program

The basic PORTTEST procedure ensures connectivity. The PORTTEST program initializes a user and an environment (assuming that EnterpriseOne application release is installed and configured correctly). To verify that the E1 Release is installed correctly, you must run the PORTTEST program for each environment.

If the PORTTEST program fails to run, use this checklist found on Chapter 14 of the Installation Guides to diagnose the problem before calling Oracle Support Services (OSS). Have the answers to the questions in the PORTTEST checklist 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.
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.

For the EnterpriseOne 9.2 Install Guides, refer to - Oracle JD Edwards EnterpriseOne Installation and Upgrade Documentation Release 9.2.x

For the EnterpriseOne 9.1 Install Guides, refer to this link here - JD Edwards EnterpriseOne Installation and Upgrade Documentation - Release 9.1.x.

For the EnterpriseOne 9.0 Install Guides, refer to Doc ID 705463.1 - JD Edwards EnterpriseOne Applications Release 9.0 Installation Guides, Update.


Network Services

After you install the JD Edwards EnterpriseOne Platform Pack on your Enterprise Server, you must start the Network Services. You also need to make your database services have started as well.

JD Edwards EnterpriseOne uses the Network service on the enterprise server. This service is installed during the installation process using the jdesnet -i service from the system\bin32 directory.
When you install this service, the system adds these entries to the Windows registry:

During a new installation, or after you have renamed or moved the directory tree for an existing installation, you should reinstall the services. After the initial installation, you will need to reinstall the Network service only when it has been uninstalled. You will need to uninstall this service only when the JD Edwards EnterpriseOne directory tree is renamed, moved, or deleted. The process to uninstall this service removes these entries from the Windows registry:

After the Network service is installed, you must set up the service under a network account, if you are using a network printer, or a local account, if you are using a local printer. If you are using a network account, it must be in either the Administrators or Power Users group.

After you have installed and set up the Network service, you must start the service before JD Edwards EnterpriseOne can use it. Later, if you need to stop services, you must do so in the proper order.
After JD Edwards EnterpriseOne is shut down, you can determine whether any processes completed abnormally. If so, you need to clean up the enterprise server. Unforeseen circumstances can cause JD Edwards EnterpriseOne processes to terminate abnormally. Processes that terminate abnormally are called runaway processes. After shutting down JD Edwards EnterpriseOne, look for any runaway processes and, if any exist, manually terminate them.

More details about Network Services can be found in the following locations:


NOTE: As per development , PORTTEST should be run after starting the the JDE services.
Although it is possible to run PORTTEST without JDE services running, it is not recommended as it may throw error on metadata kernel in logs .


This document provides general information and assists customers with troubleshooting known issues on the PORTTEST program and Network Services during a JD Edwards EnterpriseOne software installation.

Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Troubleshooting Steps
 Troubleshooting PORTTEST
 Scenario 1 - PORTTEST Failed with Error "Default XXXXXFA Package Spec Tables Empty" (SQL Server)
 Scenario 2 -  PORTTEST Fails with Error "JDB9900436 - Cannot Determine Database Driver Name for Driver Type 'O' "
 Scenario 3 - PORTTEST Fails with a Security Server returned error: eSecInvalidToken: The security token is invalid
 Scenario 4 - PORTTEST fails to run on the Enterprise Server with Errors: KNT0000305 - JDENET Error / SEC0000002 - Unable to connect to security server / JDB1100015 - Failed to complete Security check
 Scenario 5 - PORTTEST Fails With Error: JDB9900160 - Failed to load driver library libora<version>.so
 Scenario 6 - PORTTEST Failing - Error: Table or View does not Exist
 Scenario 7 - Errors and Resolutions for AS/400 PORTTEST Issues
 Troubleshooting Network Services
 Scenario 1 - Running Multiple Releases on Enterprise Server. Unable to Start Services on Second Release
 Scenario 2 - Services Error - Unable to Resolve Hostname to IP Address on Sun Solaris Server
 Scenario 3 - Unable to Start New Enterprise Server - IPC Error: ipcLockResource 27
 Scenario 4 - JDE Services Fail to Start on AS400 Server - JDEJVM0000014 / JDEJVM000001p / JDEJVM0000030 - Failed to create JVM Errors - JdeJvmException exception thrown
 Scenario 5 - PORTTEST and EnterpriseOne Services Fail on New Unix AIX Enterprise Server Install
 Scenario 6 - EnterpriseOne Services & PORTTEST Failed after running Installation Workbench - JDB9900318 / JDB9900913 - Failed to create global table specs Errors
 Scenario 7 - EnterpriseOne Network Services and PORTTEST fails - Errors: JDB3100011 / JDB9900913 / JDB9900307 - Failed to find table specifications
 Scenario 8 - Error Starting EnterpriseOne Services - "JDB9900247 - Failed to find F98611 in cache"

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.