Monthly Archive: December 2011


HL7: BizTalk HL7 Accelerator parse errors on ACK / NACK

Next one: You are getting parse errors on the (Negative) Acknowledgment BizTalk wants to send back to the sending system. The scenario BizTalk receives an HL7 message with an error in the header, e.g. MSH|&^\|APP1^^^^^^^^^||APP2||. The MSH_3 data-type will trigger an error, for it’s not valid. The message won’t be parsed and a negative acknowledgement will be generated. The NACK is being picked up by the receive port to return...


HL7: NTE_NotesAndComments segment is not unique

I’ve found quite some bugs (no Microsoft, this is not by design, these are bugs) in the HL7 accelerator for BizTalk. I will try and post some solutions for these bugs over here. First one: The NTE_NotesAndComments segment is not unique. And because HL7 is a flat file with everything on the same level, the definition of the schemas of HL7 version 2.4 is incorrect! This will eventually cause that...


Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0×80131401)

If you get the error below (or something resembling the error below), you should uncheck the 32-bit only flag in your host and be sure the orchestration will be hosted by a new 64-bit instance. xlang/s engine event log entry: Uncaught exception (see the ‘inner exception’ below) has suspended an instance of service ‘Company.CompanyDivision.BizTalk.AutoWarehouse.Orchestrations.HandleMessageFromAutoWarehouse(8a6f1226-bf81-5a66-3929-0fd9a6362777)’. The service instance will remain suspended until administratively resumed or terminated. If resumed the instance will...