Skip to content

Commit 2efa201

Browse files
ecfanecfan
authored
Format content as tables for easier scanning
1 parent be0924b commit 2efa201

File tree

1 file changed

+26
-70
lines changed

1 file changed

+26
-70
lines changed

‎articles/logic-apps/logic-apps-enterprise-integration-b2b-list-errors-solutions.md

Lines changed: 26 additions & 70 deletions
Original file line numberDiff line numberDiff line change
@@ -18,39 +18,23 @@ This article helps you troubleshoot errors that might happen in Azure Logic Apps
1818

1919
## Agreement resolution
2020

21-
### No agreement found
22-
23-
**Error description**: **No agreement found with Agreement Resolution Parameters.**
24-
25-
**User action**: Add an agreement with the appropriate business identities to your integration account. Make sure that the business identities match to the input message IDs.
26-
27-
### No agreement found with identities
28-
29-
**Error description**: **No agreement found with identities: 'AS2Identity'::'Partner1' and'AS2Identity'::'Partner3'**
30-
31-
**User action**: The agreement has invalid **AS2-From** or **AS2-To** values. To match the AS2 IDs in the AS2 message headers for your agreement setup, correct the AS2 message header values **AS2-From** or **AS2-To** or the agreement.
21+
| Error summary | Error | Resolution |
22+
|---------------|-------|------------|
23+
| No agreement found. | **No agreement found with Agreement Resolution Parameters.** | Add an agreement with the appropriate business identities to your integration account. Make sure that the business identities match to the input message IDs. |
24+
| No agreement found with identities. | **No agreement found with identities: 'AS2Identity'::'Partner1' and'AS2Identity'::'Partner3'** | The agreement has invalid **AS2-From** or **AS2-To** values. To match the AS2 IDs in the AS2 message headers for your agreement setup, correct the AS2 message header values **AS2-From** or **AS2-To** or the agreement. |
3225

3326
## AS2
3427

35-
### Missing AS2 message headers
36-
37-
**Error description**: **Invalid AS2 headers. One of the "AS2-To" or "AS2-From" headers is empty.**
38-
39-
**User action**: A received AS2 message didn't contain the headers for **AS2-From**, **AS2-To**, or both. Check the AS2 message **AS2-From** and **AS2-To** headers, and correct them based on your agreement setup.
40-
41-
### Missing AS2 message body and headers
28+
| Error summary | Error | Resolution |
29+
|---------------|-------|------------|
30+
| Missing AS2 message headers | **Invalid AS2 headers. One of the "AS2-To" or "AS2-From" headers is empty.** | A received AS2 message didn't contain the headers for **AS2-From**, **AS2-To**, or both. Check the AS2 message headers for **AS2-From** and **AS2-To**, and correct them based on your agreement setup. |
31+
| Missing AS2 message body and headers | **The request content is null or empty.** | A received AS2 message didn't contain a message body. Make sure that a message body exists. |
32+
| AS2 message decryption failure | **`[processed/Error: decryption-failed]`** | Apply the `@base64ToBinary()` function to the AS2Message before sending the message to the trading partner. See [Example - AS2 message decryption failure example](#as2-decryption-failure). |
33+
| Message Disposition Notification (MDN) decryption failure | **`[processed/Error: decryption-failed]`** | Apply the `@base64ToBinary()` function to the MDN before sending the notification to the partner. See [Example - Message Disposition Notification (MDN) decryption failure](mdn-decryption-failure). |
34+
| Missing signing certificate | **The Signing Certificate has not been configured for AS2 party. AS2-From: partner1 AS2-To: partner2** | Set the AS2 agreement settings with the correct certificate for the signature. |
4235

43-
**Error description**: **The request content is null or empty.**
44-
45-
**User action**: A received AS2 message didn't contain a message body.
46-
47-
### AS2 message decryption failure
48-
49-
**Error description**: **`[processed/Error: decryption-failed]`**
50-
51-
**User action**: Apply the `@base64ToBinary()` function to the AS2Message before sending the message to the trading partner.
52-
53-
For example:
36+
<a name="as2-decryption-failure"></a>
37+
### Example - AS2 message decryption failure
5438

5539
```json
5640
"HTTP": {
@@ -62,13 +46,8 @@ For example:
6246
},
6347
```
6448

65-
### Message Disposition Notification (MDN) decryption failure
66-
67-
**Error description**: **`[processed/Error: decryption-failed]`**
68-
69-
**User action**: Apply the `@base64ToBinary()` function to the MDN before sending the notification to the partner.
70-
71-
For example:
49+
<a name="mdn-decryption-failure"></a>
50+
### Message Disposition Notification (MDN) decryption failure example
7251

7352
```json
7453
"Response": {
@@ -79,49 +58,26 @@ For example:
7958
},
8059
```
8160

82-
### Missing signing certificate
83-
84-
**Error description**: **The Signing Certificate has not been configured for AS2 party. AS2-From: partner1 AS2-To: partner2**
85-
86-
**User action**: Set the AS2 agreement settings with the correct certificate for the signature.
87-
8861
## X12 and EDIFACT
8962

90-
### Leading or trailing space found
91-
92-
**Error description**: **Error encountered during parsing. The EDIFACT transaction set with ID '123456' contained in interchange (without group) with ID '987654', with sender ID 'Partner1', receiver ID 'Partner2' is being suspended with following errors: "Leading Trailing separator found"**
63+
| Error summary | Error | Resolution |
64+
|---------------|-------|------------|
65+
| Duplicate check is enabled in the agreement. | **Duplicate Control Number** | This error indicates that the received message has duplicate control numbers. Correct the control number, and resend the message. |
66+
| Missing schema in the agreement | **Error encountered during parsing. The X12 transaction set with ID '564220001' contained in functional group with ID '56422', in interchange with ID '000056422', with sender ID '12345678', receiver ID '87654321' is being suspended with following errors: "The message has an unknown document type and did not resolve to any of the existing schemas configured in the agreement"** | Set up the schema in the agreement settings. |
67+
| Incorrect schema in the agreement | **The message has an unknown document type and did not resolve to any of the existing schemas configured in the agreement.** | Set up the correct schema in the agreement settings. |
68+
| Leading or trailing space found | **Error encountered during parsing. The EDIFACT transaction set with ID '123456' contained in interchange (without group) with ID '987654', with sender ID 'Partner1', receiver ID 'Partner2' is being suspended with following errors: "Leading Trailing separator found"** | Set up or edit the agreement settings to allow leading and trailing whitespace. See [Example - Allow leading and trailing whitespace](#allow-leading-trailing-whitespace). |
9369

94-
**User action**: Set up or edit the agreement settings to allow leading and trailing whitespace.
70+
<a name="allow-leading-trailing-whitespace"></a>
71+
### Set up agreement settings to allow leading and trailing whitespace
9572

9673
![Screenshot shows example for setting to allow leading and trailing whitespace.](./media/logic-apps-enterprise-integration-b2b-list-errors-solutions/leadingandtrailing.png)
9774

98-
### Duplicate check is enabled in the agreement
99-
100-
**Error description**: **Duplicate Control Number**
101-
102-
**User action**: This error indicates that the received message has duplicate control numbers. Correct the control number, and resend the message.
103-
104-
### Missing schema in the agreement
105-
106-
**Error description**: **Error encountered during parsing. The X12 transaction set with ID '564220001' contained in functional group with ID '56422', in interchange with ID '000056422', with sender ID '12345678', receiver ID '87654321' is being suspended with following errors: "The message has an unknown document type and did not resolve to any of the existing schemas configured in the agreement"**
107-
108-
**User action**: Set up the schema in the agreement settings.
109-
110-
### Incorrect schema in the agreement
111-
112-
**Error description**: **The message has an unknown document type and did not resolve to any of the existing schemas configured in the agreement.**
113-
114-
**User action**: Set up the correct schema in the agreement settings.
115-
11675
## Flat file
11776

118-
### Input message with no body
119-
120-
**Error description**: **InvalidTemplate. Unable to process template language expressions in action 'Flat_File_Decoding' inputs at line '1' and column '1902': 'Required property 'content' expects a value but got null. Path ''.'.**
121-
122-
**User action**: This error indicates that the input message doesn't contain a body.
77+
| Error summary | Error | Resolution |
78+
|---------------|-------|------------|
79+
| Input message with no body | **InvalidTemplate. Unable to process template language expressions in action 'Flat_File_Decoding' inputs at line '1' and column '1902': 'Required property 'content' expects a value but got null. Path ''.'.** | This error indicates that the input message doesn't contain a body. Make sure that the input message contains a body. |
12380

12481
## Related content
12582

12683
- [Exchange B2B messages between partners using workflows in Azure Logic Apps](/azure/logic-apps/logic-apps-enterprise-integration-b2b)
127-

0 commit comments

Comments
 (0)