# 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 <a href="/en/gr/01459/#r242-troubleshooting-tools">Enable AS2 Connections</a>.

## 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: &lt;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 <a href="/en/gr/01458/#add-connection-allowed-ips">Configure Custom AS2 Connections</a>.

## 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 <a href="/en/gr/15085/#source--rendition-file-limits">limitations</a> 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 <a href="/en/gr/703946/#about-as2-connections">About AS2 Connections</a>.

### 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 <a href="/en/gr/15085/">document library</a>, 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 <a href="/en/gr/01266/#types-of-gateway-responses">Send a Gateway Transmission</a>.
4. Moves the _Transmission_ record to the <a href="/en/gr/01266/#transmission-lifecycle-states-for-gateway-transmissions">appropriate state</a>.
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.