Thread was being aborted

Question

Hi all, i would like to know why i am getting error in catch method this error. in try catch inserting data after inserting redirecting to success page, after redirecting, noticed error in catche method try{ //Peice of code to insert data cmd.ExecuteNonQuery(); Response.Redirect("RegistrationsuccessPage.aspx"); } Catch (Exception ex) { Response.Write("Error:" + ex.Message);//Thread was being aborted } can some one help me how to solve this error.

Rajanikant Hawaldar · Answer

Hi Murali To work around this problem, use one of the following methods: For Response.End, call the HttpContext.Current.ApplicationInstance.CompleteRequest method instead of Response.End to bypass the code execution to the Application_EndRequest event. For Response.Redirect, use an overload, Response.Redirect(String url, bool endResponse) that passes false for the endResponse parameter to suppress the internal call to Response.End. For example: Response.Redirect ("nextpage.aspx", false); If you use this workaround, the code that follows Response.Redirect is executed. For Server.Transfer, use the Server.Execute method instead. https://support.microsoft.com/en-us/help/312629/prb-threadabortexception-occurs-if-you-use-response-end-response-redir https://stackoverflow.com/questions/1014439/asp-net-exception-thread-was-being-aborted-causes-method-to-exit

Spice Agent · Answer

For Response.Redirect, use an overload, Response.Redirect(String url, bool endResponse) that passes false for the endResponse parameter to suppress the internal call to Response.End. https://vidmateapp.win

Subbarao A · Answer

Hi Murali, you can use the below way. Response.Redirect(URL, false); Context.ApplicationInstance.CompleteRequest();

Murali Kris · Answer

Hi Rajanikant, thank you for prompt reply. Followed with second option. "For Response.Redirect, use an overload, Response.Redirect(String url, bool endResponse) that passes false for the endResponse parameter to suppress the internal call to Response.End. For example: Response.Redirect ("nextpage.aspx", false);" it works good now.