Something supernatural is happening here.
I just added a transaction area around some legacy code that I was debugging to ensure that the driving I was doing was not fixed.
This worked twice, then said:
"The transaction manager has disabled its support for remote/network transactions."
without any code changes or changes between working / inoperative (literally 3 F5 per line [web application]). This was local code connecting the remote database server.
Since this is completely separate code in another project, this is the time. If I remove the Scopes transactions from this code, it works fine, but itβs time with them in place. I tried my local SQL server and remote, both timeouts inside a Scope transaction.
What the hell is going on?
Edit: I found that I changed TransactionScopes to:
using (var scope = new TransactionScope(TransactionScopeOption.RequiresNew))
to
using (var scope = new TransactionScope())
prevents the problem: s
What does it mean?
source
share