Byte order mark and the MQSC adapter

I was experiencing a problem today when sending messages to a non windows MQ Series server as every message that was send included an unidentified invalid character. This problem had me stumped!


I tried a number of things to try and resolve this issue:

  • Using the PassThrouhTransmit pipeline
  • Using the XMLTransmit pipeling
  • Inspecting the message using a unicode enable text editor

It wasn’t until I received some advice from a fellow BizTalker (thanks Thaigo) that I should look at the pipeline properties.

As it turns out these unidentified invalid characters were the unicode byte order mark, and that this can be surpressed when sending messages from this pipeline.

So there you go mystery solved!


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: