Troubleshooting EDI Transmission Failures

Check for EDI transmission problems if the EDI.ADM message group receives a transmission failure message or the associated document remains in the EDI Outgoing Status Queue with a status of ENVELOPED for an extended period of time. What constitutes an extended period of time depends on:

How often you dial into the network.
How much mail (EDI documents) is waiting to come back from the network.
How much mail is waiting to send to the network.
The network to which you subscribe. Keep in mind that some are slower than others.

If you decide that a document has been in the EDI Outgoing Status Queue with a status of ENVELOPED for an extended period of time, display the EDI Activity Log and review the messages in the Transmission Summary Report.

Transmission Messages Associated With a Problem

Transmission messages that indicate a problem can refer to:

Connection failure.
Logon failure.
Transmission failure.
Receive failure.
A Network Call Complete and Network Call Started with no Transmission Summary Report in between.

Connection Failure

Messages

The following messages are associated with a connection failure:

Connect Failed
Logon Failed
Transmit Nothing
Receive Unsuccessful

Cause

The attempt to connect to the network failed.

Solution

Verify that the EDI modem is turned on.
Verify that the cables between the modem and computer and the modem and wall jack are securely connected.
Verify that the telephone line is plugged into the jack on the modem that says Line or Telco, not Phone.
Verify that the telephone line is active. If necessary, connect a telephone to the jack labeled Phone on the back of the modem to confirm that the line is active and you get a dial tone.
If one of the previous steps does not isolate the problem, try resetting the modem by turning it off for 10 seconds and then turning it back on.
If none of these actions fixes the problem, your network or telephone company may be the source of the problem.

Logon Failure

Messages

The following messages are associated with a logon failure:

Connect Okay
Logon Failed
Transmit Nothing
Receive Failed

Cause

The network did not return the appropriate prompts associated with the logon procedures for your network.

Solution

Wait a few minutes and try again.
If retrying does not fix the problem, your network or telephone company is probably the source of the problem.

Transmission Failure

Messages

The following messages are associated with a transmission failure:

Connect Okay
Logon Okay
Transmit Failed
Receive Failed

Cause

The transmission of EDI documents to the network was not successfully completed.

Note: The documents enveloped for the failed transmission attempt will remain enveloped until a successful transmission is made.

Solution

Wait a few minutes and try again.
If retrying does not fix the problem, your network or telephone company is probably the source of the problem.

Receive Failure

Messages

The following messages are associated with a receive failure.

Connect Okay
Logon Okay
Transmit Okay (or Transmit Nothing)
Receive Failed

Cause

The transmission of EDI documents from the network was not successfully completed.

Solution

Wait a few minutes and try again.
If retrying does not fix the problem, your network or telephone company is probably the source of the problem.

Network Call Complete and Network Call Started With No Transmission Summary Report

The entry in the EDI Activity Log for a successful transmission starts with Network Call Complete and the name of your network, is followed by a Transmission Summary Report, and ends with Network Call Started and the name of your network.

The EDI Activity Log reports an occurrence of Network Call Complete and Network Call Started with no Transmission Summary Report. If you only see "Network Call Complete: (the name of your network)" followed by "Network Call Started: (the name of your network)," one of the following may be the cause of and solution to the transmission problem:

Cause of the Problem	Solution
The tty that the EDI modem uses may be enabled and have a getty running on it.	If the tty has a getty, the configuration for the tty in smit may be incorrect. If so, the login for the tty should be disabled and the tty pdisabled. If you need assistance, call Eclipse Support.
If the tty has no getty, the problem may be caused by the tty having a lock on it.	The tty should not have a lock in /etc/locks. If you need assistance, call Eclipse Support.
The tty to which the EDI modem is connected may not be the same one that is defined to EDI. This may happen if a cable is inadvertently disconnected and then reconnected to the wrong location, or if ttys are changed.	If a cable gets disconnected and you know where to reconnect it, do so. If you do not know where to reconnect it, or if ttys are changed, call Eclipse Support for assistance.