Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: A file receive location that points to a remote UNC path is disabled unexpectedly when you use BizTalk Server 2009 in Windows Vista or in Windows Server 2008


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You install Microsoft BizTalk Server 2009 on two nodes of a Windows Server 2008 failover cluster.
  • You configure the two BizTalk Server 2009 servers to be in the same BizTalk group.
  • In this BizTalk group, you create a file receive location that points to a remote Universal Naming Convention (UNC) path. Then, you enable the file receive location.
  • One node of the failover cluster is shut down.
In this scenario, the file receive location is disabled unexpectedly even though the remote UNC path can be accessed. When this issue occurs, you must manually re-enable the file receive location.

Notes
  • This issue does not occur if you use BizTalk Server 2009 in Windows XP or in Windows Server 2003.
  • A similar issue may occur if you use BizTalk Server 2009 on a single computer that is running Windows Vista or Windows Server 2008. You create a file receive location that points to a remote UNC path, enable the file receive location, and then restart the computer. However, the file receive location is disabled.

↑ Back to the top


Resolution

Cumulative update information

For BizTalk Server 2009, the hotfix that resolves this issue is included in Cumulative Update 1 for BizTalk Server 2009. 

For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 

2429050 Cumulative update package 1 for BizTalk 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 this specific problem.

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, submit a request to 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 website: 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

To apply this hotfix, you must have BizTalk Server 2009 installed.

Restart information

You must restart the BizTalk host instance or instances after you apply this hotfix.

Registry information

You do not have to change the registry after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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.
BizTalk Server 2009, 32 bit version
File nameFile versionFile sizeDateTimePlatform
Btsmsgcore.dll3.8.432.21,247,57630-Jun-201016:14x86
BizTalk Server 2009, 64 bit version
File nameFile versionFile sizeDateTimePlatform
Btsmsgcore.dll3.8.432.21,976,66405-Jul-201023:09x64

↑ Back to the top


Workaround

To work around the issue, stop the BizTalk host instance before the failover cluster node is shut down.

↑ Back to the top


More Information

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 Server hotfixes

↑ Back to the top


Status

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

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbbiztalk2009presp1fix

↑ Back to the top

Article Info
Article ID : 2125511
Revision : 1
Created on : 1/7/2017
Published on : 12/29/2010
Exists online : False
Views : 354