The transaction is either not associated with the current connection or has been completed

Question

0.00/5 (No votes)

See more:

VB

If GlbSQLCOnn.State = ConnectionState.Closed Then
    GlbSQLCOnn.Open()
End If
'===========
SqlTrans = GlbSQLCOnn.BeginTransaction
Cmd.Transaction = SqlTrans
Cmd.CommandType = CommandType.Text
Cmd.CommandText = StrSQlDelete
Cmd.UpdatedRowSource = UpdateRowSource.None
Cmd.CommandTimeout = 10000

Cmd.ExecuteNonQuery()

Cmd.CommandText = StrSQlInsert & " OPTION (MAXDOP 2)"

Cmd.ExecuteNonQuery()


SqlTrans.Commit()

Posted 24-Apr-15 21:42pm

Virensharma

Updated 24-Apr-15 22:15pm

Richard MacCutchan

v2

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)

Sascha Lefèvre · Answer 1 · 2015-04-25T05:53:00

From what is to see of your code, the only explanation I can think of is that your SqlCommand Cmd isn't associated with the SqlConnection GlbSQLCOnn on which you started the transaction.

The name of your connection, GlbSQLCOnn, seems to indicate that it's a "global" connection object. There's no reason to do something like that. Connections to Sql-Server are pooled by default - so you gain nothing by re-using the same connection-object throughout the lifetime of your application. Instead it can become messy quickly (your problem here seems to be a case of that). That's why I suggest you to use any SqlClient-objects only locally.

Pseudo-code:

someMethod()
   using connection = new SqlConnection(connectionString)
   using transaction = connection.BeginTransaction
   using command = new SqlCommand(connection, transaction)

      connection.Open

      // do something here

      transaction.Commit

   end using
end method

Even if my assumption from the first paragraph isn't correct, you will solve your problem by sticking to the above "pattern".