Are you one of those rare birds whom, while running batches that involve distributed queries, have encountered any of the following errors?

3988 - New transaction is not allowed because there are other threads running in the session.

3930 - The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.


If so, I would appreciate you send me an email to telling me your story.

I’ve been recently investigating the reason of a series of problems with distributed queries which happen under very narrow circumstances and I’m working with SQL Dev right to try to find the best solution to the problem.

I’d like to know how often these have hit others without SQL Server Dev team being aware of those cases.

And please, spread this request as much as you can among your SQL Server fellows community whom you think could have seen these problems before.

Thanks in advance!

Skip to main content