J
Jamie Schatte
We are running an ASP.NET 1.1 application that allows users to update data
in a SQL Server 2000 database. All of these updates follow the same general
flow as shown in the sample code below. This usually works great, but every
now and then the following exception is thrown when calling the Rollback
method:
"The SqlCommand is currently busy Open, Fetching"
I am not sure what is causing this exception. It seems like this is a
secondary exception that occurs during the Rollback, which means I am losing
the original exception that caused the Rollback to get called in the first
place.
Thanks in advance for any help.
Jamie Schatte
Fidelis Software
--------------------------------------- SAMPLE CODE
BELOW ----------------------------------------------
objSqlConnection.Open()
Try
objSqlTransaction = objSqlConnection.BeginTransaction
' ***** DO SOME SORT OF UPDATES HERE *****
objSqlTransaction.Commit()
Catch objException As Exception
objSqlTransaction.Rollback()
Throw objException
Finally
objSqlConnection.Close()
End Try
in a SQL Server 2000 database. All of these updates follow the same general
flow as shown in the sample code below. This usually works great, but every
now and then the following exception is thrown when calling the Rollback
method:
"The SqlCommand is currently busy Open, Fetching"
I am not sure what is causing this exception. It seems like this is a
secondary exception that occurs during the Rollback, which means I am losing
the original exception that caused the Rollback to get called in the first
place.
Thanks in advance for any help.
Jamie Schatte
Fidelis Software
--------------------------------------- SAMPLE CODE
BELOW ----------------------------------------------
objSqlConnection.Open()
Try
objSqlTransaction = objSqlConnection.BeginTransaction
' ***** DO SOME SORT OF UPDATES HERE *****
objSqlTransaction.Commit()
Catch objException As Exception
objSqlTransaction.Rollback()
Throw objException
Finally
objSqlConnection.Close()
End Try