Article ID: 976172 - View products that this article applies to.
On a BizTalk Server 2009 system, the BizTalk tracking database (BizTalkDTADb) is hosted on a named SQL Server instance. In this scenario, when you right-click a completed service instance on the Group Hub page and then select Message Flow, you receive the following error message:
A network-related or instance-specfic error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server).
Cumulative update informationFor 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:
(http://support.microsoft.com/kb/[anySimpleType]/[anySimpleType]/ )Cumulative update package 1 for BizTalk Server 2009
Hotfix informationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft BizTalk Server 2009 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
PrerequisitesThere are no prerequisites for installing this hotfix package.
Restart requirementYou do not have to restart the computer after you apply this hotfix package.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix package.
File informationThe English (United States) version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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.
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
For more information about database structure and jobs, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn.microsoft.com/en-us/library/aa561960%28BTS.20%29.aspxFor more information about viewing tracked message and instance data, visit the following MSDN Web site:
http://msdn.microsoft.com/en-us/library/aa561587%28BTS.10%29.aspxFor more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 976172 - Last Review: December 8, 2010 - Revision: 2.0