ASP.net + Error Message + Thread was being aborted

This miffing error is actually by design. The Response.Redirect(string) is the same as Response.Redirect(string, true) which internally calls the Response.End() which will then throws the ThreadAbortException exception to unwind the stack and terminate the current page execution. One way is to use Response.Redirect(string, false) to prevent Redirect from calling Response.End and throwing the exception. You can also explicitly handle the exception, e.g.

Try
    Response.Redirect(targetURL)
Catch ex As Exception
   ' do something...
Catch ex As ThreadAbortException
   ' do nothing to suppress this exception
Finally
   ' clean up
End Try

TheMehrdad's suggestion is also one possible way to solve the problem.

Some good reading.
http://support.microsoft.com/default.aspx?scid=kb;en-us;312629


Henry

This will also occur if you use Server.Transfer instead of Response.Redirect. In both cases, it's pretty harmless.

Server.Transfer can save you round trips compared to Response.Redirect, and you can also use HttpContext.Current to transfer information between the pages.

I don't have a respone.redirect in the try statement, i am just running a query.  here is the try/catch statement

            Try
                objConn.Open()
                With objCmd
                    .Parameters.Clear()
                    .CommandText = strQuery
                    .Parameters.Add("@CUSTOMERID", SqlDbType.Char, 4).Value = Trim(CustomerID)
                    .Connection = objConn
                    .CommandTimeout = 90
                    .CommandType = CommandType.Text
                    .ExecuteNonQuery()
                End With

            Catch e As Exception
                Dim strErrorMessage As String

                strErrorMessage = "<strong>Application Error: </strong> " & _strClassname & vbCrLf & vbCrLf
                strErrorMessage &= "<strong>Running function: </strong> " & strFunctionName & vbCrLf & vbCrLf
                strErrorMessage &= "<strong>Query:</strong>" & vbCrLf
                strErrorMessage &= "    " & strQuery & vbCrLf & vbCrLf
                strErrorMessage &= "<strong>Error Message:</strong>" & vbCrLf
                strErrorMessage &= "    " & e.Message & vbCrLf & vbCrLf
                strErrorMessage &= "<strong>Stack Trace:</strong>" & vbCrLf
                strErrorMessage &= "    " & e.StackTrace & vbCrLf & vbCrLf

            Finally
                objCmd.Dispose()
                objConn.Close()
            End Try

Are you using the same connection to update? If you are using the same connection, and two threads are trying to
update at the same time another thread is updating using the same connection, the application/thread will crash.
This could be happening. Check the state of the connection for updating, make sure its not executing.

i have a query that selects an order number from a list of orders, if it successfully retrieves it then locks the order so no one else can retrieve it, this is done by updating the order.

so i have a select statement then an update in the same query string, is there a better way of doing this so i don't cause the error.

Taka a look at this article:
http://www.sql-server-performance.com/reducing_locks_hints.asp

i guess i didn't mean actual SQL locking, but rather locking the order with SQL I do it by changing (updating) value in a table, this is for reporting and other ways, so this is why the select statement then the update statement in the same query string.

I looked again at your .CommandTimeout = 90 line, that would fit with the default of the executionTimeout which is also 90. I think that is looking like a likely cause.

Andy

MSDN documentation:

The OLE DB .NET Provider does not support named parameters for passing parameters to a SQL Statement or a stored procedure called by an OleDbCommand when CommandType is set to Text. In this case, the question mark (?) placeholder must be used. For example:

SELECT * FROM Customers WHERE CustomerID = ?

As a result, the order in which OleDbParameter objects are added to the OleDbParameterCollection must directly correspond to the position of the question mark placeholder for the parameter.For more information, see Using Stored Procedures with a Command.

But from the error message dkilby is getting I think dkilby is using a SQL command, not an OleDbCommand, so @ is the way to do it?

Yes, you're right.

so until i can create a fast query can i just try increasing the .CommandTimeout = 90 in the code or do i have to add something to the web.config file?