<%@ Application Language="VB" %> <object id="LXFramework" runat="server" class="Framework.Framework.App" scope="Application" /> <script runat=server> Sub Application_Start(ByVal sender As Object, ByVal e As EventArgs) LXFramework.nApplicationMode = 3 LXFramework.oServer = Server LXFramework.Initialize() End Sub Sub Application_BeginRequest(ByVal sender As Object, ByVal e As EventArgs) LXFramework.oRequest = Request LXFramework.oResponse = Response LXFramework.oServer = Server LXFramework.BeginRequest() End Sub Sub Application_EndRequest(ByVal sender As Object, ByVal e As EventArgs) LXFramework.EndRequest() LXFramework.oResponse.Write(LXFramework.GetJavascriptMessage) End Sub Sub Application_Error(ByVal sender As Object, ByVal e As EventArgs) LXFramework.ErrorSetup() End Sub Sub Application_PreRequestHandlerExecute(ByVal sender As Object, ByVal e As EventArgs) Dim loContext As Object = Context.Handler Dim loType As Object = loContext.GetType() Dim lcType As String = loType.ToString ' .vb and .config not accepted If lcType = "System.Web.HttpForbiddenHandler" Then Response.Redirect("Default.aspx") End If Dim loPage As System.Web.UI.Page = Context.Handler LXFramework.oPage = loPage End Sub </script>So, basically, as it is the case presently, I have no guarantee of receiving my own page result as it could be coming from someone else page result doing a hit at the same time. Where should I look for to verify for that? I thought that this was bullet proof in ASP.NET. But, I have to say it is kind of scary. Basically, we have to stop the production phase until this is resolved. If someone could suggest things to look for in an attempt to resolve the issue, that would be greatly appreciated.