Azure 逻辑应用的 B2B 错误和解决方案B2B errors and solutions for Azure Logic Apps

本文可帮助你解决可能会出现在逻辑应用 B2B 方案中的错误,并提供更正这些错误的适当操作。This article helps you troubleshoot errors that might happen in Logic Apps B2B scenarios and suggests appropriate actions for correcting those errors.

协议解析Agreement resolution

没有找到协议No agreement found

错误说明Error description 没有找到具有协议解析参数的协议。No agreement found with Agreement Resolution Parameters.
用户操作User action 应将协议添加到具有议定的业务标识的集成帐户。The agreement should be added to the integration account with agreed business identities.
业务标识应与输入的消息 ID 相匹配。The business identities should match to the input message IDs.

没有找到具有标识的协议No agreement found with identities

错误说明Error description 没有找到具有标识 'AS2Identity'::'Partner1' and'AS2Identity'::'Partner3' 的协议No agreement found with identities: 'AS2Identity'::'Partner1' and'AS2Identity'::'Partner3'
用户操作User action 协议配置无效的 AS2-From 或 AS2-To。Invalid AS2-From or AS2-To configured for agreement.
更正 AS2 消息和“AS2-From”或“AS2-To”标头或协议,以匹配具有协议配置的 AS2 消息标头中的 AS2 ID。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.

AS2AS2

缺少 AS2 消息标头Missing AS2 message headers

错误说明Error description 无效的 AS2 标头。Invalid AS2 headers. “AS2-To”或“AS2-From”中的一个标头为空。One of the "AS2-To" or "AS2-From" headers is empty.
用户操作User action 收到的 AS2 消息不包含 AS2-From 或 AS2-To 标头或均不含。An AS2 message was received that did not contain the AS2-From or AS2-To or both headers.
检查 AS2 消息的 AS2-From 或 AS2-To 标头并基于协议配置进行更正。Check AS2 message AS2-From and AS2-To headers and correct them based on agreement configuration.

缺少 AS2 消息正文和标头Missing AS2 message body and headers

错误说明Error description 请求内容为 null 或为空。The request content is null or empty.
用户操作User action 收到的 AS2 消息不包含消息正文。An AS2 message was received that did not contain the message body.

AS2 消息解密失败AS2 message decryption failure

错误说明Error description [已处理/错误:解密失败][processed/Error: decryption-failed]
用户操作User action 发送给伙伴之前,请将 @base64ToBinary 添加到 AS2Message。Add @base64ToBinary to AS2Message before sending to partner.

例如:For example:

"HTTP": {
   "inputs": {
   "body": "@base64ToBinary(body('Encode_to_AS2_message')?['AS2Message']?['Content'])",
   "headers": "@body('Encode_to_AS2_message')?['AS2Message']?['OutboundHeaders']",
   "method": "POST",
   "uri": "xxxxx.xxx"
},

MDN 解密失败MDN decryption failure

错误说明Error description [已处理/错误:解密失败][processed/Error: decryption-failed]
用户操作User action 发送给伙伴之前,请添加 @base64ToBinary 到 MDN。Add @base64ToBinary to MDN before sending to partner.

例如:For example:

"Response": {
   "inputs": {
   "body": "@base64ToBinary(body('Decode_AS2_message')?['OutgoingMDN']?['Content'])",
   "headers": "@body('Decode_AS2_message')?['OutgoingMDN']?['OutboundHeaders']",
   "statusCode": 200
},               

缺少签名证书Missing signing certificate

错误说明Error description 未对 AS2 参与方配置签名证书。The Signing Certificate has not been configured for AS2 party.
AS2-From:partner1 AS2-To:partner2AS2-From: partner1 AS2-To: partner2
用户操作User action 使用正确的签名证书配置 AS2 协议设置。Configure AS2 agreement settings with correct certificate for signature.

X12 和 EDIFACTX12 and EDIFACT

找到前导或尾部空格Leading or trailing space found

错误说明Error description 分析过程中所遇到的错误。Error encountered during parsing. ID 为“987654”、发送方 ID 为“Partner1”、接收方 ID 为“Partner2”的交换(没有组)中包含的 ID 为“123456”的 EDIFACT 事务集由于以下错误被暂停: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"

用户操作User action 将协议设置配置为允许前导或尾部空格。The agreement settings to be configured to allow leading and trailing space.
将协议设置编辑为允许前导和尾部空格。Edit agreement settings to allow leading and trailing space.

允许空格

协议已启用重复项检查Duplicate check has enabled in the agreement

错误说明Error description 重复控制编号Duplicate Control Number
用户操作User action 此错误表明收到的消息有重复控制编号。This error indicates the received message has duplicate control numbers.
更正控制编号并重新发送消息。Correct the control number and resend the message.

协议中缺少架构Missing schema in the agreement

错误说明Error description 分析过程中所遇到的错误。Error encountered during parsing. ID 为“56422”的功能组中包含的 ID 为“564220001”的 X12 事务集(在 ID 为“000056422”、发送方 ID 为“12345678”、接收方 ID 为“87654321”的交换中)由于以下错误被暂停: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"

用户操作User action 在协议设置中配置架构。Configure schema in the agreement settings.

协议中架构不正确Incorrect schema in the agreement

错误说明Error description 消息具有未知的文档类型,无法解析为协议中配置的任何现有架构。The message has an unknown document type and did not resolve to any of the existing schemas configured in the agreement.
用户操作User action 在协议设置中配置正确的架构。Configure correct schema in the agreement settings.

平面文件Flat file

输入的消息没有正文Input message with no body

错误说明Error description InvalidTemplate。InvalidTemplate. 无法处理操作 "Flat_File_Decoding" 输入中的行 "1" 和列 "1902" 处的模板语言表达式:所需属性“内容”应该有一个值,但为空。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 ''.'.
用户操作User action 此错误表明输入的消息不包含正文。This error indicates the input message does not contain a body.