Skip to content

Commit 8abcbcf

Browse files
ecfanecfan
committed
Fix Acrolinx and formatting issues
1 parent 048e43f commit 8abcbcf

File tree

1 file changed

+57
-53
lines changed

1 file changed

+57
-53
lines changed

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

Lines changed: 57 additions & 53 deletions
Original file line numberDiff line numberDiff line change
@@ -13,131 +13,135 @@ ms.date: 06/02/2017
1313

1414
# B2B errors and solutions for Azure Logic Apps
1515

16-
This article helps you troubleshoot errors that might happen in Logic Apps B2B scenarios and suggests appropriate actions for correcting those errors.
16+
This article helps you troubleshoot errors that might happen in Logic Apps B2B
17+
scenarios and suggests appropriate actions for correcting those errors.
1718

18-
## Agreement Resolution
19+
## Agreement resolution
1920

20-
### *No agreement found
21+
### No agreement found
2122

2223
| | |
2324
|---|---|
24-
| Error description | No agreement found with Agreement Resolution Parameters|
25-
| User action | The agreement should be added to the integration account with agreed business identities.</br> The business identities should match to the input message ids|
25+
| Error description | No agreement found with Agreement Resolution Parameters. |
26+
| User action | The agreement should be added to the integration account with agreed business identities. </br>The business identities should match to the input message IDs. |
2627
| | |
2728

28-
### * No agreement found with identities
29+
### No agreement found with identities
2930

3031
| | |
3132
|---|---|
32-
| Error description | No agreement found with identities: 'AS2Identity'::'Partner1' and'AS2Identity'::'Partner3'|
33-
| User action | Invalid AS2-From or AS2-To configured for agreement. </br> Correct AS2 message AS2-From or AS2-To headers or agreement to match AS2 ids in AS2 message headers with agreement configurations |
33+
| Error description | No agreement found with identities: 'AS2Identity'::'Partner1' and'AS2Identity'::'Partner3' |
34+
| User action | Invalid AS2-From or AS2-To configured for agreement. </br>Correct the AS2 message's "AS2-From" or "AS2-To" headers or the agreement to match the AS2 IDs in the AS2 message headers with agreement configurations. |
3435
| | |
3536

3637
## AS2
3738

38-
### * Missing AS2 message headers
39+
### Missing AS2 message headers
3940

4041
| | |
4142
|---|---|
42-
| Error description| Invalid AS2 headers. One of 'AS2-To' or 'AS2-From' headers are empty|
43-
| User action | An AS2 message was received that did not contain the AS2-From or AS2-To or both headers. </br> Check AS2 message AS2-From and AS2-To headers and correct them based on agreement configuration |
43+
| Error description | Invalid AS2 headers. One of the "AS2-To" or "AS2-From" headers is empty. |
44+
| User action | An AS2 message was received that did not contain the AS2-From or AS2-To or both headers. </br> Check AS2 message AS2-From and AS2-To headers and correct them based on agreement configuration. |
4445
| | |
4546

46-
47-
### * Missing AS2 message body and headers
47+
### Missing AS2 message body and headers
4848

4949
| | |
5050
|---|---|
51-
| Error description| The request content is null or empty |
52-
| User action | An AS2 message was received that did not contain the message body |
51+
| Error description | The request content is null or empty. |
52+
| User action | An AS2 message was received that did not contain the message body. |
5353
| | |
5454

55-
### * AS2 message decryption failure
55+
### AS2 message decryption failure
5656

5757
| | |
5858
|---|---|
5959
| Error description | [processed/Error: decryption-failed] |
60-
| User action | Add @base64ToBinary to AS2Message before sending to partner
61-
```java
62-
"HTTP": {
63-
"inputs": {
64-
"body": "@base64ToBinary(body('Encode_to_AS2_message')?['AS2Message']?['Content'])",
65-
"headers": "@body('Encode_to_AS2_message')?['AS2Message']?['OutboundHeaders']",
66-
"method": "POST",
67-
"uri": "xxxxx.xxx"
68-
},
69-
60+
| User action | Add @base64ToBinary to AS2Message before sending to partner. |
61+
|||
62+
63+
For example:
64+
65+
```json
66+
"HTTP": {
67+
"inputs": {
68+
"body": "@base64ToBinary(body('Encode_to_AS2_message')?['AS2Message']?['Content'])",
69+
"headers": "@body('Encode_to_AS2_message')?['AS2Message']?['OutboundHeaders']",
70+
"method": "POST",
71+
"uri": "xxxxx.xxx"
72+
},
7073
```
7174

72-
### * MDN decryption failure
75+
### MDN decryption failure
7376

7477
| | |
7578
|---|---|
7679
| Error description | [processed/Error: decryption-failed] |
77-
| User action | Add @base64ToBinary to MDN before sending to partner
78-
```java
79-
"Response": {
80-
"inputs": {
81-
"body": "@base64ToBinary(body('Decode_AS2_message')?['OutgoingMDN']?['Content'])",
82-
"headers": "@body('Decode_AS2_message')?['OutgoingMDN']?['OutboundHeaders']",
83-
"statusCode": 200
84-
},
85-
80+
| User action | Add @base64ToBinary to MDN before sending to partner. |
81+
|||
82+
83+
For example:
84+
85+
```json
86+
"Response": {
87+
"inputs": {
88+
"body": "@base64ToBinary(body('Decode_AS2_message')?['OutgoingMDN']?['Content'])",
89+
"headers": "@body('Decode_AS2_message')?['OutgoingMDN']?['OutboundHeaders']",
90+
"statusCode": 200
91+
},
8692
```
8793

88-
### * Missing signing certificate
94+
### Missing signing certificate
8995

9096
| | |
9197
|---|---|
92-
| Error description| The Signing Certificate has not been configured for AS2 party. </br> AS2-From: partner1 AS2-To: partner2 |
93-
| User action | Configure AS2 agreement settings with correct certificate for signature |
98+
| Error description| The Signing Certificate has not been configured for AS2 party. </br>AS2-From: partner1 AS2-To: partner2 |
99+
| User action | Configure AS2 agreement settings with correct certificate for signature. |
94100
| | |
95101

96102
## X12 and EDIFACT
97103

98-
### * Leading or trailing space found
104+
### Leading or trailing space found
99105

100106
| | |
101107
|---|---|
102-
| 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 |
103-
| User action | The agreement settings to be configured to allow leading and trailing space. </br> Edit agreement settings to allow leading and trailing space |
108+
| 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: <p>"Leading Trailing separator found" |
109+
| User action | The agreement settings to be configured to allow leading and trailing space. </br>Edit agreement settings to allow leading and trailing space. |
104110
| | |
105111

106112
![allow space](./media/logic-apps-enterprise-integration-b2b-list-errors-solutions/leadingandtrailing.png)
107113

108-
### * Duplicate check has enabled in the agreement
114+
### Duplicate check has enabled in the agreement
109115

110116
| | |
111117
|---|---|
112118
| Error description | Duplicate Control Number |
113-
| User action | This error indicates the received message has duplicate control numbers. </br> Correct the control number and resend the message |
119+
| User action | This error indicates the received message has duplicate control numbers. </br>Correct the control number and resend the message. |
114120
| | |
115121

116-
### * Missing schema in the agreement
122+
### Missing schema in the agreement
117123

118124
| | |
119125
|---|---|
120-
| 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" |
121-
| User action | Configure schema in the agreement settings |
126+
| 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: <p>"The message has an unknown document type and did not resolve to any of the existing schemas configured in the agreement" |
127+
| User action | Configure schema in the agreement settings. |
122128
| | |
123129

124-
### * Incorrect schema in the agreement
130+
### Incorrect schema in the agreement
125131

126132
| | |
127133
|---|---|
128134
| Error description | The message has an unknown document type and did not resolve to any of the existing schemas configured in the agreement. |
129-
| User action | Configure correct schema in the agreement settings |
135+
| User action | Configure correct schema in the agreement settings. |
130136
| | |
131137

132138
## Flat file
133139

134-
### * Input message with no body
140+
### Input message with no body
135141

136142
| | |
137143
|---|---|
138144
| 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 ''.'. |
139-
| User action | This error indicates the input message does not contain a body |
145+
| User action | This error indicates the input message does not contain a body. |
140146
| | |
141147

142-
## Learn more
143-
[Learn more about the Enterprise Integration Pack](logic-apps-enterprise-integration-overview.md)

0 commit comments

Comments
 (0)