Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 952556 - Last Review: May 28, 2009 - Revision: 2.0
File receive locations are disabled or shut down on a computer that is running BizTalk Server
Consider the following scenario. On a computer that is running Microsoft BizTalk Server, File receive locations are used with Universal Naming Convention (UNC) shares. You have many File receive locations. For example, you have 100 File receive locations.
In this scenario, you may notice that the File receive locations are disabled or shut down. One of the following error messages may also be logged in the Application log:
BizTalk Server 2004
Event Type: Error
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5649
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
The receive location "\\ServerName\FileDrop\FileName.FileNameExtension" is shutting down. Details:"The FILE receive location \\ServerName\FileDrop\FileName.FileNameExtension exhausted the network retry attempts. ".
BizTalk Server 2006
Event Type: Error
Event Source: BizTalk Server 2006
Event Category: (1)
Event ID: 5649
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
The receive location "FileReceive" with URL "\\ServerName\FileDrop\FileName.FileNameExtension" is shutting down. Details:"The FILE receive location \\ServerName\FileDrop\FileName.FileNameExtension exhausted the network retry attempts. ".
This problem occurs because BizTalk Server uses persistent connections to the UNC share so that BizTalk Server can enlist in file change notifications. This problem can occur if multiple persistent connections exist.
To resolve this problem, increase the MaxCmds and MaxMpxCt registry values on the BizTalk Server computer and on the remote UNC Share computer. To do this, follow the steps that are described in Microsoft Knowledge Base article 810886.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
810886Â
(http://kbalertz.com/Feedback.aspx?kbNumber=810886/
)
"The network BIOS command limit has been reached" error message in Windows Server 2003, in Windows XP, and in Windows 2000 Server
Note You can also increase the retry count for the File adapter. The default value for the retry count is 5. The maximum value for the retry count can be 2147483647.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
APPLIES TO
- Microsoft BizTalk Server 2006 R2 Enterprise Edition
- Microsoft BizTalk Server 2006 R2 Developer Edition
- Microsoft BizTalk Server 2006 R2 Standard Edition
- Microsoft BizTalk Server 2006 R2 Branch Edition
- Microsoft BizTalk Server 2006 Enterprise Edition
- Microsoft BizTalk Server 2006 Developer Edition
- Microsoft BizTalk Server 2006 Standard Edition
- Microsoft BizTalk Server 2004 Enterprise Edition
- Microsoft BizTalk Server 2004 Developer Edition
- Microsoft BizTalk Server 2004 Standard Edition
- Microsoft BizTalk Server 2009 Branch
- Microsoft BizTalk Server 2009 Developer
- Microsoft BizTalk Server 2009 Enterprise
- Microsoft BizTalk Server 2009 Standard
| kbtshoot kbpubtypekc kberrmsg kbprb KB952556 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate