[BTS]The join order has been enforced because a local join hint is used.;Duplicate key was ignored.".

在一个客户的BizTalk Server 2013 R2环境中会报如下的ERROR，查找相关资料后，先试试停掉所有Trace。

Log Name: Application
Source: BizTalk Server
Date: 3/3/2015 7:59:12 AM
Event ID: 6912
Task Category: BizTalk Server
Level: Error
Keywords: Classic
User: N/A
Computer: BizTalk_PRD_Server
Description:
The following stored procedure call failed: " { call [dbo].[bts_UpdateMsgbox_XXXXXXXXX]( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}". SQL Server returned error string: "Warning: The join order has been enforced because a local join hint is used.;Warning: The join order has been enforced because a local join hint is used.;Duplicate key was ignored.".
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="BizTalk Server" />
<EventID Qualifiers="49344">6912</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-03-02T23:59:12.000000000Z" />
<EventRecordID>79877</EventRecordID>
<Channel>Application</Channel>
<Computer>BizTalk_PRD_Server</Computer>
<Security />
</System>
<EventData>
<Data> { call [dbo].[bts_UpdateMsgbox_XXXXXXXXXXXXX]( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}</Data>
<Data>Warning: The join order has been enforced because a local join hint is used.;Warning: The join order has been enforced because a local join hint is used.;Duplicate key was ignored.</Data>
</EventData>
</Event>

Reference

https://social.msdn.microsoft.com/Forums/en-US/2b07de27-7e70-462d-af66-a6d535cdc886/biztalk-2009-sql-msgbox-error?forum=biztalkgeneral

1.sometimes we get this error when sql server is too busy to execute this stored proc, so better keep an eye on sql server performance.

2.There could be temporory network glitch, are you getting this error regularly?

3.I increased the VM memory to 2Gb and reduced the amount of BizTalk tracking - if I set tracking of properties & message bodies on receive, the problem seemed to occur more often.

4.The Problem Doesn't Seem to Occur if the tracking message bodies on receive Port is not been Set.

5. It was fixed by unchecking tracking.