问题描述
在一台开发机上，我们将BizTalk 2010服务器升级到BizTalk2013.我们正在从另一台计算机向这台计算机发送HL72消息，并得到未找到架构的错误:
On a dev machine, we upgraded a BizTalk 2010 server to BizTalk 2013. We are sending HL72 messaves from another machine to this one and getting a schema not found error:
替代错误号:301 替代错误说明:架构 http://microsoft.com/HealthCare/HL7/2X#ORU_R01_23_GLO_DEF找不到 备用编码系统:HL7-BTA
Alternate Error Number: 301 Alternate Error Description: Schema http://microsoft.com/HealthCare/HL7/2X#ORU_R01_23_GLO_DEF not found Alternate Encoding System: HL7-BTA
该消息将"LAB"指定为发送应用程序，并且我们有一个名为"LAB"的团体，该团体将"http://mycompany/myapplication/HL7/2X/2.3/ORU/v1"指定为架构名称空间，因此我们无法弄清为什么它要寻找ORU R01 2.3 默认microsoft 名称空间中的架构.
The message specifies "LAB" as the sending application, and we have a party called "LAB" which specifies "http://mycompany/myapplication/HL7/2X/2.3/ORU/v1" as the schema namespace, so we can't figure out why it's looking for the ORU R01 2.3 schema in the default microsoft namespace.
我们的信息如下:
MSH|^~\&|LAB|ABC|LAB||201311071138||ORU^R01|D2863329|D|2.3|
PID|1|A00003766|XX00014202|9191610101|Ihhendrickson^Plis||19691202|M|||8423 Panko Pvt^^Here^BC^XXX XXX||111-1111|||||xx0055355x3|9x9x6x0x0x|
PV1|1|R|TRAKBHLB||||93190^Plisihd^xxxxxx^^^Dr^^xxxxxx|||||||||||RCR||BC|||||||||||||||||||xxxxx||REG|||201207261453|
ORC|RE|PT80755100.0010|||CM|N|||201311071138|^xxxxxx^Linda^^^^^xxxx||93190^xxxx^Aaron^^^Dr^^xxxx|xxx|
OBR|1|PT0711:T00001R100.0010|PT0711:T00001R|100.0010^Group \T\ Screen^00050252^34532-2^Blood Type \T\ Indirect Antibody Screen^pCLOCD|R|201311071004|201311071004|||G|||PLIS Testing|201311071004|T|93190^Plisihd^xxx^^^Dr^^Pxxxxx||00050252|||xxx|201311071004||BBK|F|||93190^xxx^Aaron^^^Dr^^xxxx|
NTE|1||Date required: 20131107|
NTE|2||Any previous transfusions? Unknown|
NTE|3||Specify any underlying blood disorders: U|
NTE|4||Has consent for blood products been obtained? Yes|
OBX|1|ST|150.0100^Patient Blood Group^00050252^882-1^Blood Type \T\ Indirect Antibody Screen^pCLOCD||OPOS^O Rh Pos|||||A~S|F|||201311071137|xx^xx^L|IH001^^Blood Group^Patient Blood Group^150.0100|
OBX|2|ST|200.0100^Ab Screen Gel^00050252^XBC1931-6^Blood Type \T\ Indirect Antibody Screen^pCLOCD||NEGATIVE^NEGATIVE|||||A~S|F|||201311071138|xx^xx^L|IH001^^Ab Scr Gel^Antibody Screen Gel^200.0100|
ZDR||xxx^xxxx^Aaron^^^Dr^^^^^^^^^ATP|
ZPR||
有人有我们应该尝试的想法吗?
Anyone have ideas we should try?
推荐答案
对于发送端口，HL7 2.X汇编程序组件应该使用MSH 5字段值来确定要使用的参与方.发送端口上的管道配置应具有启用部分名称解析(EnablePartialNameResolutionForReceivingApplication)的选项，该选项在打开时可能会有所帮助.
For send ports, the HL7 2.X Assembler component is supposed to use the MSH 5 field value to determine the party to use. The pipeline configuration on your send port should have an option to enable partial name resolution (EnablePartialNameResolutionForReceivingApplication), which—when turned on—may help.
在接收位置，HL7 2X Disassembler组件应使用MSH 3进行聚会决议.接收位置的BTAHL72XReceivePipeline配置具有名为EnablePartialNameResolutionForSendingApplication和EnablePartialNameResolutionForReceivingApplication的设置，供您打开.
In receive locations, the HL7 2X Disassembler component should use MSH 3 for party resolution. The receive location's BTAHL72XReceivePipeline configuration has settings called EnablePartialNameResolutionForSendingApplication and EnablePartialNameResolutionForReceivingApplication for you to turn on.
较旧版本的BizTalk需要一个修补程序才能使这些设置起作用，但是这种设置不再有效是必要的.在该页面上，设置的描述为:
Older versions of BizTalk required a hotfix to make those settings work, but that should no longer be necessary. From that page, the description of the settings are:
对于发送管道，BTAHL7 2.X汇编器包含以下属性:
Property name: Enable Partial Name Resolution For Receiving Application
Default value: False
Description for the property:
First check party with name MSH5.1 + MSH5.2 + MSH5.3. If not found, check party with name MSH5.1 + MSH5.2. If not found, check with name MSH5.1.
对于接收管道，BTAHL7 2.X反汇编程序包含以下属性:
Property name: Enable Partial Name Resolution For Receiving Application
Default value: False
Description for the property:
First check party with name MSH5.1 + MSH5.2 + MSH5.3. If not found, check party with name MSH5.1 + MSH5.2. If not found, check with name MSH5.1.
Property name: Enable Partial Name Resolution For Sending Application
Default value: False
Description for the property:
First check party with name MSH3.1 + MSH3.2 + MSH3.3. If not found, check party with name MSH3.1 + MSH3.2. If not found, check with name MSH3.1.
如果这没有帮助，则可以尝试另一种仅尝试发送端口的操作:在参与方配置中，尝试将参与方分配给您的发送端口，如第三步所述此处.这是试图迫使它使用适当的政党的一种方式.但是，这对接收位置无济于事.
If that does not help, then there is one other thing to try for send ports only: In the party configuration, try assigning the party to your send port, as described in step three here. That's one way to try to force it to use the proper party. That will not help with receive locations, though.
这篇关于HL7加速器错误:找不到架构(升级到BizTalk 2013之后)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！