September 19, 2006 at 2:59 pm
I am getting this error in our production environment "New request is not allowed to start because it should come with valid transaction descriptor" It seem to be related to MS DTC. The error is being triggered on a server where MSMQ is used to queue up "transactions". MSMQ calls a COM+ comp with interacts with SQL Server 2005. The COM+ comp connects and basically executes a stored procedure. I don't see the sp being started so it looks like the error is during the connection. Any ideas?
September 19, 2006 at 5:01 pm
try FIX:
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"
June 19, 2007 at 2:32 pm
I have the same error msg: New request is not allowed to start because it should come with valid transaction descriptor : "New request is not allowed to start because it should come with valid transaction descriptor" .
I tried the hotfix in http://support.microsoft.com/kb/916002 , but I still have the same problem.
Any ideas ?
PS I'm running sql 2005 SP2
June 19, 2007 at 2:44 pm
We still working on this. This problem did not occur in 2000 and started in SQL 2005. It appears to be related to long running queries and locking. By the time you see the error, the "long running" query is usally gone. Try to isolate and tune the big store procedures to see if it helps.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply