Byte order mark and the MQSC adapter

September 18, 2009

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!