Symptoms

Consider the following scenario:

  • You have a receive location that is configured to use the Microsoft BizTalk Adapter for WebSphere MQ (MQSC Adapter) that is included in Microsoft Host Integration Server 2010 or Microsoft Host Integration Server 2009 to receive messages from IBM WebSphere MQ.

  • The messages that are received from the IBM WebSphere MQ queue are encrypted EBCDIC messages.

In this scenario, the beginning and end of some received messages may contain garbage (invalid) characters after the messages are converted by using the character set (for example, UTF-8) that is specified in the MQSC Adapter configuration. When this occurs, you may receive an error message that resembles the following:

A message received by adapter "MQSC" on receive location "receive_location_name" with URI "URI" is suspended.

Error details: There was a failure executing the receive pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "XML disassembler" Receive Port: "Port Name" URI: "URI" Reason: No Disassemble stage components can recognize the data.

Cause

The MQSC Adapter was not correctly converting messages based on the character set that was specified in the adapter settings because of issues that are related to the length of the received message.

Resolution

Cumulative update information

Host Integration Server 2013

The fix that resolves this issue is included in cumulative update package 1 for Host Integration Server 2013. To obtain Cumulative Update 1, see the following Microsoft Knowledge Base article:

2908834 Cumulative Update Package 1 for Host Integration Server 2013

Host Integration Server 2010

The fix that resolves this issue is included in cumulative update package 9 for Host Integration Server 2010. To obtain Cumulative Update 9, see the following Microsoft Knowledge Base article:

2897923 Cumulative update package 9 for Host Integration Server 2010

Host Integration Server 2009

The fix that resolves this problem is included in cumulative update package 7 for Host Integration Server 2009. To obtain Cumulative Update 7, see the following Microsoft Knowledge Base article:

2975320 Cumulative Update 7 for Host Integration Server 2009

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have Microsoft Host Integration Server 2009 Cumulative Update 6 installed to apply this hotfix.

Restart information

You may have to restart the computer after you apply this hotfix.

Replacement information

This hotfix does not replace any previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

For all supported x86-based versions of Host Integration Server 2009

File name

File version

File size

Date

Time

Platform

Microsoft.biztalk.adapter.mqsc.imqwrapper.dll

8.0.4101.2

165,088

31-Jan-2014

19:42

x86

Microsoft.biztalk.adapter.mqsc.imqwrappertxn.dll

8.0.4101.2

164,072

31-Jan-2014

19:42

x86

For all supported x64-based versions Host Integration Server 2009

File name

File version

File size

Date

Time

Platform

Microsoft.biztalk.adapter.mqsc.imqwrapper.dll

8.0.4101.2

165,088

31-Jan-2014

19:42

x86

Microsoft.biztalk.adapter.mqsc.imqwrappertxn.dll

8.0.4101.2

164,072

31-Jan-2014

19:42

x86

Microsoft.biztalk.adapter.mqsc.imqwrapper.dll

8.0.4101.2

198,368

31-Jan-2014

19:46

x64

Microsoft.biztalk.adapter.mqsc.imqwrappertxn.dll

8.0.4101.2

195,816

31-Jan-2014

19:46

x64



Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.



Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

The problem described here is related to the problem described in the following Microsoft Knowledge Base article:

2883141 FIX: "Failure encountered while attempting to get message from queue" error when a message larger than 1 MB is received in BizTalk Server 2010 After this update is applied, the MQSC Adapter uses additional MQ Get options (MQGMO_ACCEPT_TRUNCATED_MSG and MQGMO_CONVERT) when it receives messages. These options enable IBM WebSphere MQ to send back the actual length in bytes of the message to be converted.

In addition, the Maximum Message Length settings should be configured to match the specific message size requirements of the environment to make sure that all messages are received successfully. The Maximum Message Length settings can be specified in the MQSC Adapter parameters and in IBM WebSphere MQ settings. Therefore, you should make sure that the settings agree.

This update in Host Integration Server 2010 Cumulative Update 9 supersedes the related update that was included in Host Integration Server 2010 Cumulative Update 8 and should be used in environments that implement the MQSC Adapter to integrate with IBM WebSphere MQ.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×