FIX: Error message when you try to use the SqlClient class in an ADO.NET 2.0-based application to connect to an instance of SQL Server 2005: "New request is not allowed to start because it should come with valid transaction descriptor"

In Microsoft Visual Studio 2005, you try to use the SqlClient class in a Microsoft ADO.NET 2.0-based application to connect to an instance of Microsoft SQL Server 2005. When you do this, you may receive the following error message:This problem occurs when the following conditions are true:

• The connection is reused from the connection pool in a distributed transaction.
• A local transaction is committed or rolled back before the connection.
• The local transaction ends before the connection.

To resolve this problem, download the appropriate file for the computer.

For an x86-based computer

The following file is available for download from the Microsoft Download Center:

Download the NDP20-KB916002-X86.exe package now. (http://download.microsoft.com/download/2/c/5/2c5bcdc9-3241-443a-9f96-4e0b0edfa727/ndp20-kb916002-x86.exe)

For an x64-based computer

The following file is available for download from the Microsoft Download Center:

Download the NDP20-KB916002-X64.exe package now. (http://download.microsoft.com/download/d/3/9/d39c79df-4158-45df-9031-92c52ab0ed19/ndp20-kb916002-x64.exe)

For an IA-64-based computer

The following file is available for download from the Microsoft Download Center:

Download the NDP20-KB916002-IA64.exe package now. (http://download.microsoft.com/download/0/0/3/00392dd3-5b4f-4d99-94e8-6827b8f8d7ef/ndp20-kb916002-ia64.exe)

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

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

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: