"New request is not allowed to start because it should come with valid transaction descript

Hi all,
We are getting "New request is not allowed to start because it should come with valid transaction descriptor" when using transactions against SQL 2005. As I understand it, it's a bug that occurs after some statement has terminated against the database; see http://lab.msdn.microsoft.com/productfeedback/ViewWorkaround.aspx?FeedbackID=FDBK46530#1

Now, I wonder if there is a hotfix coming soon on this?

/Daniel

I have the same error description but within a different setup. Running SQL Server 2005 on Windows Server 2003 R2. Connecting to database use SNAC from VC6 application. Application is written still with old ODBC technology. I have switched back to the SQL Server driver in the odbc connection. Anyone have any ideas surrounding this problem, I also get a lot of query timeouts and have done the usual checks. Ensure no deadlocks occurs. Set query timeout value higher. Doing a google revealed that everyone getting this error has a managed code app using sqlclient, I geuss that this is the same classes MS used within the sql native client driver and therefore the hotfix will sort out this problem?

|||http://support.microsoft.com/kb/916002|||If you contact customer support directly they should be able to provide you with more information about how to resolve this issue.