Troubleshoot Communication Problems

When you submit an application to an enterprise server through an override of the master business function set in Object Configuration Manager, you might experience communication problems with the enterprise server. The business function then runs locally on the client workstation. JD Edwards EnterpriseOne displays a window to inform you that the business function is running in a new location.

To troubleshoot communication problems:

Note: Use this procedure if JD Edwards EnterpriseOne displays a window to inform you that a business function is running in a new location.

Check the jde.ini on the workstation to make sure the JDENET service name (port number) is correct and valid.
This port number must match the settings in the server jde.ini file, and the JD Edwards EnterpriseOne server must be running to successfully submit reports or to run business logic on a server. Security services and transaction management services also require the JD Edwards EnterpriseOne server to be running:
```
 [JDENET]
```
```
serviceNameListen=service name
```
```
serviceNameConnect=service name
```
If serviceNameListen=service name specifies the communications service port on the TCP/IP network, JD Edwards EnterpriseOne uses this port address to listen for requests on the network. Using a file called services, you can associate the port number with a unique name. The default value is jde_server (port number 6003).
If serviceNameConnect=service name specifies the communications service port on the TCP/IP network, JD Edwards EnterpriseOne uses this port address to connect to the network. Using a file called services, you can associate the port number with a unique name. The default value is jde_server (port number 6003).
On the workstation, exit JD Edwards EnterpriseOne and turn logging on in the jde.ini.
Run the application on the server again, and then check the jde.log file to see if any of these errors are logged:
- JDENET_SendMsg Failed Error=8
  This error can mean you are not using the correct TCP/IP service port or that the enterprise server does not have that JDENET listing.
- JDENET_SendMsgFailed Error=5, 11, or 12
  These errors can mean that the message is being sent to the correct port, but the enterprise server JDENET is down.
From within Server Manager, change the port address to determine if both the workstation and server are using the same port.
Check the services file on the workstation (located in the operating system directory\System32\drivers\etc for Windows).
Ensure that a blank line exists at the end of the file and that you have the service name mentioned in Step 1 (for example, jde_server) going to the correct port address on the server. Verify the port address with the server administrator.
If you receive a Communication Failure message, try resubmitting the application.
A time-out may have occurred.
```
 [JDENET]
```
```
netTrace=0/1 (disabled/enabled)
```
Look in the log file for this message:
```
Could not find symbol in the <BSFN dll name>
```