BizTalk Server 2006: FIX: A warning is logged when you use the MQSeries adapter in a dynamic receive scenario in Microsoft BizTalk Server: “The remote procedure call failed and did not execute. (Exception from HRESULT: 0×800706BF)”

SUPPORT SOLUTION:
In Microsoft
BizTalk Server 2006, you use the
MQSeries
adapter to receive and process messages. You configure the receive ports so that they can dynamically receive messages.
Occasionally, a warning that resembles the following is logged in the
Application log:Event Type: Warning Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006 Event ID: 5743 Description:
The adapter failed to transmit message going to send port
“<Send Port Name>” with URL
“<URI>”. It will be retransmitted after the
retry interval specified for this Send Port. Details:”Unable to cast COM
object of type ‘System.__ComObject’ to interface type
‘Microsoft.BizTalk.Adapter.MQS.Agent.MQSBroker’. This operation failed because
the QueryInterface call on the COM component for the interface with IID
‘{<ID>}’ failed due to the following error:
The remote procedure call failed and did not execute. (Exception from HRESULT:
0×800706BF).” When this problem occurs, the
message
instances change
to the Dehydrated state.
To complete the
processing
of these messages, the BizTalk default host instance must be restarted.Note A dynamic receive configuration
enables the application to select a source address (URI) at run time. The
application can do this by setting the MQSeries.DynamicReceive context property to Yes,
and
then specifying the dynamic receive address.
For more information, refer to the “More Information” section..This problem occurs because the dynamic receive
port in
the MQSeries adapter does not handle failures correctly.
When failures occur, the adapter logs
a warning
in the Application

log. However, the adapter does
not then perform the steps that are required to process the failed messages. These
steps that are required are as follows:Resubmit the messages.When all transport operation retries
are exhausted, move the messages to a backup transport.Suspend the messages..Hotfix information
2, ‘resolution’);
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, visit the
following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note 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
3, ‘resolution’);
You must have BizTalk
Server 2006 installed to apply this hotfix.Restart requirement
3, ‘resolution’);
You do not have to restart the computer after you apply this
hotfix. However, you must restart the BizTalk host instance service after you
apply this hotfix.Hotfix replacement information
3, ‘resolution’);
This hotfix does not replace other hotfixes. File information
3, ‘resolution’);
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.32-bit versions of BizTalk Server 2006
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile
sizeDateTimePlatformMicrosoft.biztalk.adapter.mqs.dll3.5.1763.0107,56829-May-200821:16×86Microsoft.biztalk.adapter.mqsadmin.dll3.5.1763.095,28829-May-200821:16×86Mqsagent.dll3.5.1763.0183,29629-May-200821:17×8664-bit versions of BizTalk Server 2006
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile
sizeDateTimePlatformMicrosoft.biztalk.adapter.mqs.dll3.5.1763.0107,56829-May-200821:16×86Microsoft.biztalk.adapter.mqsadmin.dll3.5.1763.095,28829-May-200821:16×86Mqsagent.dll3.5.1763.0183,29629-May-200821:17×86Mqsagent.dll3.5.1763.098,81629-May-200821:18×64.To work around this problem, restart
the BizTalk default host instances..Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the “Applies to” section..For more information about the MQSeries adapter, visit the
following Microsoft Developer Network (MSDN) Web site: http://msdn.microsoft.com/en-us/library/aa562123(BTS.20).aspx
(http://msdn.microsoft.com/en-us/library/aa562123(BTS.20).aspx)
For more information about how to configure
the
MQSeries adapter in a dynamic receive scenario, visit the following MSDN Web sites:http://msdn.microsoft.com/en-us/library/bb743349(BTS.20).aspx
(http://msdn.microsoft.com/en-us/library/bb743349(BTS.20).aspx)
http://msdn.microsoft.com/en-us/library/aa577974(BTS.20).aspx
(http://msdn.microsoft.com/en-us/library/aa577974(BTS.20).aspx)
For more information about BizTalk Server hotfixes, click
the following article number to view the article in the Microsoft Knowledge
Base: 2003907 

(http://support.microsoft.com/kb/2003907/
)

Information on BizTalk Server hot fixes

.

For File Repair and Data Recovery, visit File Repair / Data Recovery