"The transaction has aborted" exception on disposing the transaction scope

Question

0.00/5 (No votes)

See more:

The code shown here worked fine without any error on quality site, but the same code is causing an error

The Transaction has aborted

on the production site.

The error occurs on dispose of the scope. Please help me resolve this issue.

I did check:

Network DTC Setting on server and database server
Both sites (Quality and Production) are on same Server (Server A) and database also on same server (Server B)
Code:

option.IsolationLevel = System.Transactions.IsolationLevel.ReadUncommitted;
option.Timeout = TimeSpan.FromMinutes(5);

using (_objTransactionScope = new TransactionScope(TransactionScopeOption.Required, option))
{
    //..Open Connection
    //..Process the Document
    //..Update Additional information in Table2 about document(Delete/Insert)   
    //..Update Location Information in Table3 about document(Delete/Insert)
    //..Delete the Document in Table4 in Differant Database on Differant Server(WCF Service)
    //..Update the Checksum of the Document and Metadata in Table1
    //..Delete Lock Entry From Table5   
    //..Close Connection
    //..Commit Transaction Scope
}

What I have tried:

I did check:

Network DTC Setting on server and database server
Both sites (Quality and Production) are on same Server (Server A) and database also on same server (Server B)

Posted 14-Nov-21 4:51am

kedar001

Updated 14-Nov-21 5:09am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2021-11-14T05:09:00

Quote:
Both sites (Quality and Production) are on same Server (Server A) and database also on same server (Server B)

First off, that worries me: development should never have any access to production servers, and especially not production DB servers.
You should always develop and test against a separate dev DB server (often SQL Server Express) as a tiny error can easily damage or destroy the production DB.

Your ordering is wrong: you cannot commit the transaction after you close the connection, and that will probably cause the problem you have noticed.

Instead, make the connection outside (with a using block) so it the tha last thing to be terminated, and commit as the last thing you do inside it. That way, any failure in other code will always close your transaction - aborting all updates - before the connection is closed.