Friday, October 23, 2009

The part '%messagepart%' of message '%multipart message%' contained a null value at the end of the construct block.

BizTalk throws the following error when one tries to create a multipart message with a message part that was just created from a map in the same construct shape:

Shape name: Send_1
ShapeId: 11910fdc-f4a1-4391-b09d-6a9bd0275ff8
Exception thrown from: segment 1, progress 11
Inner exception: The part '%messagepart%' of message '%multipart message%' contained a null value at the end of the construct block.

Exception type: NullPartException
Source: Microsoft.XLANGs.Engine
Target Site: Void CheckNonNull()
The following is a stack trace that identifies the location where the exception occured

at Microsoft.XLANGs.Core.Part.CheckNonNull()

Somehow, BizTalk looses the value of the message part that was NOT mapped.

A work-around for this is to create a second construct shape. One just creates the message part in a mapping, and the second shape puts the message parts together.

Thanks, Christian!

Monday, October 5, 2009

If the Pipeline Component doesn't appear in the Pipeline Editor toolbox

If your BizTalk pipeline component doesn't show up in the toolbox of the pipeline editor, you should check these things:
  • Is the GUID of the pipeline component the same in AssemblyInfo and in the class itself (it appears twice there)?

  • Is the right assembly name used when instanciating an object of ResourceManager?

  • Are you using the same namespace outside the class, in the properties, and in the ResourceManager?

  • Is the assembly copied to %biztalk installation%\pipeline components?

  • Are you looking for the right component type (encoder, decoder, ...) in the pipeline editor?