I was wondering if anyone knew what caused the following errors, on a site that gets regular 24-hour traffic: - 1) Occurs infrequently, about two or three times per month. Page location: http://f1teamwear.com/WebResource.axd?AspxAutoDetectCookieSupport=1 Exception Report: Message:This is an invalid webresource request. Source: System.Web Method: Void System.Web.IHttpHandler.ProcessRequest(System.Web.HttpContext) 2) Occurred twice earlier today, an hour apart. Message:A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) Source: .Net SqlClient Data Provider Method: Void OnError(System.Data.SqlClient.SqlException, Boolean) Stack Trace: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error) at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected) at System.Data.SqlClient.TdsParserStateObject.ReadBuffer() at System.Data.SqlClient.TdsParserStateObject.ReadByte() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) at System.Data.Common.DbCommand.ExecuteReader() at GenericDataAccess.ExecuteSelectCommand(DbCommand command, Boolean openCloseConnection)
I get the WebResource error every now and then also. I haven't found any good explanation of why it happens, though I have a theory. Certain things in the .NET framework require some JavaScript or some other resource to be loaded, and they useWebResource.axd to do it. A request for that signals the framework to provide some kind of predetermined resource such as JavaScript or CSS.If you check the actual URL, there is usually some kind ofgarbled mess of a querystring behind the WebResource.axd part.That's a unique identifier letting the runtime know which resource to send. My guess is that theidentifier is built dynamically based onthe resource, session, and who knows what else and thatwhenwe get that error it's because in the split second of time between when id was generated and sent to the browser and the time when the browser actually requested the resource, the application got recycled and no longer remembers what that ID means. One goodtest of this theory would be to throw some code in the application end event that logs when the app recycles, then check your log to see if there's always anapp recycleright before you get that error.
