We came across this on one of my current projects. It didn’t prevent the application from working, but I didn’t want a bunch of instances of it in our error logs. One of the consultants who works for me found this Knowledge Base article that solved the problem.
The basic fixes are:
- Call Response.Redirect like this:
Response.Redirect ("nextpage.aspx", false); - Call Server.Execute instead of Server.Transfer