Schema http://microsoft.com/HealthCare/HL7/2X#MSH_25_GLO_DEF not f

[Mr G]

Please advise.

We have built and deployed a BTAHL72xCommon, BTAHL7231Common, and
BTAHL7231ADT01 project per the HL7 Developer Guide for HL7 Accelerator 2.0.

The messages are processed correctly in my virtual VPC. However, it does not
work in our development Biztalk Server in a distrubuted environment that was
upgraded to Biztalk 2006 R2.

The following error is generated when processing a hl7 2.3.1 ADT_A01 pipe
dilimeted message:

Error:
There was an error in parsing header
Error # 1

Alternate Error Number: 301
Alternate Error Description: Schema
http://microsoft.com/HealthCare/HL7/2X#MSH_25_GLO_DEF not found
Alternate Encoding System: HL7-BTA

You help is appreciated...I'v looked at almost every blog about this and did
not get a clear resolution....to the point of giving up...and doing a full
reinstall of BTS2006 R2. BTW we using the Developer edition in the VPS and
the enterprise edition in the distributed environment.

[Eric Stott]

Dumb question,
Have you used the btsasmext.dll to make sure that the 2.5 ACK schema is
deployed and it shows up in your schema list in the admin console?

Eric
http://blog.hl7-info.com

Post by Mr G
Please advise.
We have built and deployed a BTAHL72xCommon, BTAHL7231Common, and
BTAHL7231ADT01 project per the HL7 Developer Guide for HL7 Accelerator 2.0.
The messages are processed correctly in my virtual VPC. However, it does not
work in our development Biztalk Server in a distrubuted environment that was
upgraded to Biztalk 2006 R2.
The following error is generated when processing a hl7 2.3.1 ADT_A01 pipe
There was an error in parsing header
Error # 1
Alternate Error Number: 301
Alternate Error Description: Schema
http://microsoft.com/HealthCare/HL7/2X#MSH_25_GLO_DEF not found
Alternate Encoding System: HL7-BTA
You help is appreciated...I'v looked at almost every blog about this and did
not get a clear resolution....to the point of giving up...and doing a full
reinstall of BTS2006 R2. BTW we using the Developer edition in the VPS and
the enterprise edition in the distributed environment.

[Mr G]

It turns out that deploying the BTAHL72x? assemblies from the Visual Studio
IDE on the workstation to a remote Biztalk Server does not update the Biztalk
GAC even though you get a successful deploy notice in Visual Studio. This is
confusing because you do see the assemblies appear in the Biztalk Server
application resource folder fooling you into thinking the deploy worked.

A workaround for now is to manually deploy the BTAHL72x? assemblies from the
Biztalk Server resource folder...by adding the assemblies from the visual
studio project obj\assembly folder on the workstation. Will look at
automating this later.

A clue is that you get the same error message when you delete all relevant
assemblies in the Biztalk resource folder - ie the schemas required are
truely missing.

Post by Mr G
Please advise.
We have built and deployed a BTAHL72xCommon, BTAHL7231Common, and
BTAHL7231ADT01 project per the HL7 Developer Guide for HL7 Accelerator 2.0.
The messages are processed correctly in my virtual VPC. However, it does not
work in our development Biztalk Server in a distrubuted environment that was
upgraded to Biztalk 2006 R2.
The following error is generated when processing a hl7 2.3.1 ADT_A01 pipe
There was an error in parsing header
Error # 1
Alternate Error Number: 301
Alternate Error Description: Schema
http://microsoft.com/HealthCare/HL7/2X#MSH_25_GLO_DEF not found
Alternate Encoding System: HL7-BTA
You help is appreciated...I'v looked at almost every blog about this and did
not get a clear resolution....to the point of giving up...and doing a full
reinstall of BTS2006 R2. BTW we using the Developer edition in the VPS and
the enterprise edition in the distributed environment.

[Tom Canter - Neudesic]

I would strongly encourage you to learn the MSI building functionality
in BizTalk (new in 2006) that allows you to build and deploy single
click installer solutions.

I discourage use of the Visual Studio BizTalk Explorer in a production
environment, and you have seen just one limit of that approach.

Thansk,
Tom

[Mr G]

I agree. In this case though, I first need to get the DLL's from Visual
Studio obj/deployment folder into the development Biztalk server first....and
then from there build the msi files for production with its own binding files.

BTW, there is a related hot fix for the r2 biztalk hl7 accelerator 2.0 that
is required when customising names spaces for these schemas.
see KB 949781 http://support.microsoft.com/kb/949781

Appreciate your help.

Post by Tom Canter - Neudesic
I would strongly encourage you to learn the MSI building functionality
in BizTalk (new in 2006) that allows you to build and deploy single
click installer solutions.
I discourage use of the Visual Studio BizTalk Explorer in a production
environment, and you have seen just one limit of that approach.
Thansk,
Tom