获得“Wildcardschema”处理837P - 你能帮忙吗？ （我添加了打印屏幕） [英] Getting "Wildcardschema" processing 837P - Can you help? (I added print screens)
问题描述
嗨！
我读了关于" wildcardschema 的所有其他帖子"并且已经花了相当多的时间来确定EDI解析器抱怨的内容。为了方便您帮助我，我添加了打印屏幕。我知道我错过了一些东西，也许你可以提供帮助。
上下文：我正在尝试处理 837P 来自一个合作伙伴。该文件包含121个事务集。我正在使用100％的消息传递方案（没有编排）。我有一个接收端口/位置，它使用接收EDI管道，我有一个使用PassThrough管道的发送端口，它将XML文件写入目录。 非常简单的东西。
Visual Studio验证：该文件在visual studio中验证（我收到成功的消息） 。我通过添加批处理模式（在部署项目之前删除）验证整个交换。
BizTalk应用程序：我有一个BizTalk应用程序。它引用了BizTalk EDI应用程序和BizTalk.System（参见打印屏幕 - > http://m2msysonline.com/forums/biztalk/incident.1.wildcardschema/reference_to_edi_project.jpg）
837P架构：我已将架构部署到我的项目中（请参阅打印屏幕 - > http://m2msysonline.com/forums/biztalk/incident.1.wildcardschema/schema_837P_deployed.jpg）
合作伙伴配置：我有我的伙伴配置为发件人，我确实为837P事务指定了GS和ST段（ http://m2msysonline.com/forums/ biztalk / incident.1.wildcardschema / partner_sender_configuration.jpg）
暂停服务实例： EDI接收管道对事务进行了分配，我有121个暂停（可恢复）实例（ http://m2msysonline.com/forums/biztalk/incident.1。 wildcardschema / suspended_resumable.jpg）
消息上下文：在查看我的121个服务实例之一的消息上下文时，我看到了对" wildcardschema "我有错误"组件的输出消息"Unknown"在接收管道中"Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive"由于以下错误而被暂停：未知。挂起的消息的序列号是"。消息上下文如下 http://m2msysonline.com/forums/biztalk/incident.1.wildcardschema/message_context.jpg" ;.
837P文件：GS8设置为00401X098A - 其他一切似乎都没问题。
你能让我知道我缺少什么吗？
我感谢您的帮助，期待收到您的来信！
谢谢，
FP
查看您的上下文属性，看起来它成功解析了ISA和GS段。在错误描述下，它说"解析过程中出错"。 ..."我记得在我的一个项目中收到了一些这些未知错误。这听起来像消息的主体与预期的不匹配。我认为问题是消息体或派对命名空间配置。我会将聚会的EDI属性看作EDI接收器，以确保给定的架构的命名空间是您部署的架构。
我首先在管理控制台的消息上下文视图中展开ErrorDescription上下文属性，看它是否给出关于身体哪个部分导致问题的更准确信息。然后检查事件查看器日志以获取更多错误。
谢谢，
Hi!
I read all the other post regarding the "wildcardschema" and already spent considerable time trying to identify what is the EDI parser complaining about. To make it easier for you to help me, I added print screen. I know I'm missing something and maybe you can help.
Context: I'm trying to process a 837P coming from one partner. The file contains 121 transaction sets. I'm using a 100% messaging scenario (no orchestrations). I have a receive port/location, that uses the Receive EDI pipeline, and I have a send port that using the PassThrough pipeline, that writes the XML file onto a directory. Pretty simple stuff.
Visual Studio Validation: The file validates in visual studio (I get a successful message). I validate the entire interchange by adding the batch schema (removed prior to deploy the project).
BizTalk Application: I have one BizTalk application. It references both the BizTalk EDI application and the BizTalk.System (see print screen -> http://m2msysonline.com/forums/biztalk/incident.1.wildcardschema/reference_to_edi_project.jpg)
837P Schema: I have deployed the schema onto my project (see print screen -> http://m2msysonline.com/forums/biztalk/incident.1.wildcardschema/schema_837P_deployed.jpg)
Partner Configuration: I have configured my partner as a sender, and I did specify the GS and ST segments for 837P transaction (http://m2msysonline.com/forums/biztalk/incident.1.wildcardschema/partner_sender_configuration.jpg)
Suspended Service Instances: the EDI receive pipeline debatches the transactions, and I have 121 suspended (resumable) instances (http://m2msysonline.com/forums/biztalk/incident.1.wildcardschema/suspended_resumable.jpg)
Message Context: While looking into the message context of one of my 121 services instances, I see the reference to the "wildcardschema" and I have the error "An output message of the component "Unknown" in receive pipeline "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive" is suspended due to the following error: Unknown. The sequence number of the suspended message is ". The message context is as follows http://m2msysonline.com/forums/biztalk/incident.1.wildcardschema/message_context.jpg".
837P file: the GS8 is set to 00401X098A - everything else seems ok.
Can you let me know what I'm missing?
I appreciate your help and look forward to hearing from you!
Thanks,
F P
Looking at your context properties it looks like it is successfully parsing the ISA and GS segments. Under the Error Description it says "An error occurred during parsing. ..." I remember getting some of these Unknown errors on one of my projects. It sounds like something with the body of the message is not matching what is expected. I would think the problem is either with the message body or the party namespace configuration. I would look at the EDI properties of the party as EDI receiver to make sure that the namespace of your schema given there is the schema that you deployed.
I would first expand the ErrorDescription context property in the message context view of the admin console to see if it gives more exact information on which segment of the body is causing problems. Then check the event viewer logs for more errors.
Thanks,
这篇关于获得“Wildcardschema”处理837P - 你能帮忙吗？ （我添加了打印屏幕）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
