FIX: File receive locations with alternate credentials get stuck in a tight loop after network failure

Gilt für: BizTalk Server 2013 R2 BranchBizTalk Server 2013 R2 DeveloperBizTalk Server 2013 R2 Enterprise

Symptoms


Consider the following scenario:

  • You are using Microsoft BizTalk Server.
  • You have multiple file receive locations (RL) that are pointing to different folders on the same Distributed File System (DFS) share.
  • In order to access the share, the file receive locations have alternate credentials that are supplied in Authentication tab.
  • In this scenario, if there is a temporary network issue that causes the RL to get disabled, BizTalk file receive host gets stuck in a tight loop where a single thread consumes the CPU.
  • This may result in the application event logs receiving a high volume of errors like the following until the user manually stops the host instance:

The receive location "ReceiveLocation" with URL "\\dfsserver\share\folder\file*.xml" is shutting down.
Details:"The Messaging Engine failed while notifying an adapter of its configuration.

The Messaging Engine failed to remove the receive location "ReceiveLocation" with URL "\\dfsserver\share\folder\file*.xml" from the adapter "FILE". Reason: "80070057".

Resolution


This issue is fixed in the following cumulative updates for BizTalk Server:

Cumulative Update 2 for BizTalk Server 2016

Cumulative Update 6 for BizTalk Server 2013 R2

Status


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

References


For information about the service packs and cumulative update list for BizTalk Server, click the following article number to view the article in the Microsoft Knowledge Base:

2555976 Service pack and cumulative update list for BizTalk Server

For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

2003907 Information about BizTalk hotfixes and Service Pack support