Microsoft KB Archive Search

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.

  1. Home
  2. FIX: Error message when you run a stored procedure that starts a transaction that contains a Transact-SQL statement in SQL Server 2005: "New request is not allowed to start because it should come with valid transaction descriptor"

FIX: Error message when you run a stored procedure that starts a transaction that contains a Transact-SQL statement in SQL Server 2005: "New request is not allowed to start because it should come with valid transaction descriptor"

View products that this article applies to.

Bug: #50001379 (SQL Hotfix)

↑ Back to the top

Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.

↑ Back to the top

Summary

This article describes the following about this hotfix release:
  • The problems that are fixed by the hotfix package
  • The prerequisites for installing the hotfix package
  • Whether you must restart the computer after you install the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes
  • The files that are contained in the hotfix package

↑ Back to the top

Symptoms

Consider the following scenario. You develop a Microsoft SQL Server 2005-based application that uses the SQL Native Client ODBC provider. In the application, you run a stored procedure by calling an ODBC function in synchronous mode. The stored procedure starts a transaction that contains a Transact-SQL statement. In this scenario, if the Transact-SQL statement times out, the successive statements contain the following error message:
Error Number: 3989 Error State: 1 Error Class: 16 Error Message:

New request is not allowed to start because it should come with valid transaction descriptor.

↑ Back to the top

Resolution

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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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 Web site:
http://support.microsoft.com/contactus/?ws=support
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

  • SQL Server 2005 Service Pack 2
    For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

    913089 How to obtain the latest service pack for SQL Server 2005

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only the files that are required to correct the problems that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build. 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.

SQL Server 2005 32-bit version

File nameFile versionFile sizeDateTimePlatform
Microsoft.analysisservices.dll9.0.3177.01,217,90425-19:28x86
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3177.0296,30425-19:28x86
Msmdlocal.dll9.0.3177.015,948,14425-19:28x86
Mssqlsystemresource.ldfNot Applicable524,28825-13:30Not Applicable
Mssqlsystemresource.mdfNot Applicable40,108,03225-13:30Not Applicable
Odsole70.dll2005.90.3177.059,24825-19:28x86
Rdistcom.dll2005.90.3177.0644,97625-19:28x86
Replmerg.exe2005.90.3177.0320,88025-19:28x86
Replrec.dll2005.90.3177.0784,75225-19:28x86
Sqlaccess.dll2005.90.3177.0350,57625-19:28x86
Sqlservr.exe2005.90.3177.029,193,07225-19:28x86
Sqlwep.dll2005.90.3177.090,99225-19:28x86
Sqsrvres.dll2005.90.3177.070,51225-19:28x86
Sysdbupg.sqlNot Applicable510,62210-16:40Not Applicable
Xpstar90.dll2005.90.3177.0295,79225-19:28x86

SQL Server 2005 x64-based version

File nameFile versionFile sizeDateTimePlatform
Microsoft.analysisservices.dll9.0.3177.01,217,90425-19:28x86
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3177.0296,30425-19:28x86
Msmdlocal.dll9.0.3177.015,948,14425-19:28x86
Mssqlsystemresource.ldfNot Applicable524,28825-13:30Not Applicable
Mssqlsystemresource.mdfNot Applicable40,108,03225-13:30Not Applicable
Odsole70.dll2005.90.3177.090,48025-19:38x64
Rdistcom.dll2005.90.3177.0828,78425-19:38x64
Replmerg.exe2005.90.3177.0417,64825-19:38x64
Replrec.dll2005.90.3177.01,011,56825-19:38x64
Sqlaccess.dll2005.90.3177.0357,74425-19:38x86
Sqlservr.exe2005.90.3177.039,697,26425-19:38x64
Sqlwep.dll2005.90.3177.090,99225-19:28x86
Sqlwep.dll2005.90.3177.0123,76025-19:38x64
Sqsrvres.dll2005.90.3177.083,31225-19:38x64
Sysdbupg.sqlNot Applicable510,62210-16:40Not Applicable
Xpstar90.dll2005.90.3177.0546,67225-19:38x64

↑ Back to the top

Workaround

To work around this problem, run the stored procedure in asynchronous mode.

↑ 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

More Information

For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages


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

824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: kb, kbautohotfix, kbsql2005engine, kbfix, kbexpertiseadvanced, kbpubtypekc, kbqfe, kbhotfixserver

↑ Back to the top

Article Info
Article ID : 939285
Revision : 1
Created on : 1/7/2017
Published on : 10/8/2011
Exists online : False
Views : 657