Troubleshoot AS2 Connections

Learn how to use Vault to troubleshoot your AS2 Connections.

About Troubleshooting AS2 Connections

Vault provides several tools to help you troubleshoot your AS2 Connections, as described in the following sections.

Prerequisites

Your Admin must configure your Vault as described in Enable AS2 Connection Troubleshooting Tools.

Create a Test Transmission for an AS2 Connection

When creating a new AS2 Connection to an agency or partner, sending a Test Transmission can help you confirm that the connection is working correctly before sending your first Transmission for a real Case.

Complete these steps to create and send a Test Transmission for an AS2 Connection:

  1. Navigate to Business Admin > Objects > Transmissions.
  2. Select Create Transmission > Test Transmission.
  3. Enter the following information:
    • Transmission Profile: Select the relevant AS2 Gateway type Transmission Profile. The selected Transmission Profile must also have an active AS2 Connection.
    • File: Select your relevant test E2B file.
    • Transmission Date: Select a transmission date.
    • Sender (User): Select a sender user.
    • Organization: Select the relevant Organization.
    • E2B Message ID: Enter the UUID in your test E2B file.
  4. Select Save.
  5. In the new Test Transmission record page, select the Submit to Gateway action.
    The Test Transmission moves to the Sending ICSR state.

Result

If the Destination sends back an MDN and then a valid ACK message, the Test Transmission record moves to the appropriate E2B ACK lifecycle state. This indicates that the AS2 Connection is valid and ready to receive Transmissions for real Cases.

Obtain Rejected Inbound IPs for an AS2 Connection

If your Vault is not receiving messages from an AS2 Connection for a Partner, you can view the list of rejected inbound IPs for the Connection. This shows which IPs Vault is blocking because they are not in the Connection Allowed List for that Connection.

Complete the following steps to obtain the list of rejected inbound IPs for a Connection:

  1. Navigate to Admin > Connections.
  2. Select the applicable AS2 Connection.
  3. From the All Actions menu, select Send Rejected Inbound IPs Notification.
    For this action to appear, the connection must be in the Registered or Registered - Out of Sync state.

Once Vault alerts you that the new notification is ready, go to the notification area in the upper right of any Vault page and locate the Rejected Inbound IPs for Connection: <connection> notification. The notification includes the Last Transaction Date and IP Address of the five (5) most recently blocked unique inbound IP addresses. The notification shows only the most recent transaction date for each unique IP address.

You can use the information in notifications to confirm with the Partner which of the IPs being blocked are valid. You can then add the valid IPs to the Connections Allowed List for the Partner’s AS2 Connection and resynchronize the Connection. For more information, see the Add Connection Allowed IPs and Synchronize the Connection sections of Configure Custom AS2 Connections.

Process Missing ACK Messages for AS2 Connection Transmissions

When you receive transmission acknowledgments (ACKs) from agencies or partners outside of the AS2 Connection communication channel, such as by email or portal, you can upload these messages to your Vault. During processing, Vault attaches the ACKs to their respective Transmission records. You can upload individual ACK files, or a ZIP file containing multiple ACK files. When processing ZIP files, Vault creates an Acknowledgement document for each valid ACK in the ZIP file before processing each of the documents as described below.

Requirements & Limitations

When uploading files, consider the limitations that apply. For ZIP files, all ACK files must be in the root folder of the ZIP, and the ZIP file created at the file level.

You cannot upload or process ACKs for Gateway Profile transmissions. For more information, see the note in About AS2 Connections.

Upload ACKs

Complete the following steps to upload and process ACKs received outside of the AS2 Connection communication channel:

  1. Upload the ACK files to your document library, using the document type Case > Individual Case Safety Report (ICSR) > Acknowledgement.
  2. From the All Actions menu, select Process ACKs.

Result

Vault processes ACKs as follows:

  1. Moves the Acknowledgement document to the Processing state.
  2. Finds the corresponding Transmission record with a matching E2B Message ID field.
  3. Creates a Transmission Message record on the Transmission record, with the ACK as an attachment, as described in Send a Gateway Transmission.
  4. Moves the Transmission record to the appropriate state.
  5. If the Transmission record has an FDA, CBER, or CDER Transmission Profile and contains Submission attachments, Vault submits these attachments to the requisite AS2 Gateway.
  6. Moves the Acknowledgement document to the Processed state.

If Vault cannot find a corresponding Transmission record for the ACK, Vault moves the Acknowledgement document to the Error state and sends an error notification message and email.

For processed ZIP files, Vault attaches a processing summary document for any invalid files in the ZIP.