Hello,
I'm running SQL 2005 on Win 2003 Ent SP2 box. Intermitently I get the
following messages in the application log. When the warning occurs system
resources cpu, memory, and disk IO increase substantially and after about
5-10 mintues things return to normal. This causes the website to run
extremley slow.
I'm more of a AD & Exchange guy, but have been given the task to make this
problem go away. Any assistance interpretting this message in an attempt to
find the cause of this problem will be greatly appreciated.
Thanks in advance!
Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 3/19/2008
Time: 2:36:54 PM
User: N/A
Computer: MARS
Description:
Event code: 3005 Event message: An unhandled exception has occurred. Event
time: 3/19/2008 2:36:54 PM Event time (UTC): 3/19/2008 9:36:54 PM Event ID:
66f0000f3b8b4a3e9e44c30e817150ee Event sequence: 5657 Event occurrence: 22
Event detail code: 0 Application information: Application domain:
/LM/W3SVC/868876347/Root-1-128503965846977271 Trust level: Full
Application Virtual Path: / Application Path: D:\Inetpub\saturn\www\
Machine name: MARS Process information: Process ID: 2200
Process name: w3wp.exe Account name: NT AUTHORITY\NETWORK SERVICE
Exception information: Exception type: SqlException Exception
message: Timeout expired. The timeout period elapsed prior to completion of
the operation or the server is not responding. Request information:
Request URL:
http://saturn/student/StudentRefund.aspx?StudentID=73748&tab=4&ReturnUrl=22eAn
unhandled exception has occurred.fstudentAn unhandled exception has
occurred.fstudentdetails.aspx3/19/2008 2:36:54 PMfStudentID3/19/2008 2:36:54
PMd73748HEADQUARTERS\marssaturntab3/19/2008 2:36:54 PMd4 Request path:
/student/StudentRefund.aspx User host address: 192.168.1.153 User:
611590349 Is authenticated: True Authentication Type: Forms
Thread account name: HEADQUARTERS\marssaturn Thread information:
Thread ID: 11 Thread account name: HEADQUARTERS\marssaturn Is
impersonating: False 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.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.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset,
DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable,
IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32
startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
at Keltex.SqlQueryBuilder.GetTable(SqlConnection cnn, SqlTransaction trans)
at Jupiter.Accounting.StudentClass.UpdateBalanceAll(Int32 StudentID,
SqlConnection cnn, SqlTransaction trans)
at Jupiter.Student.General.UpdateBalance(Int32 StudentID, SqlConnection
cnn, SqlTransaction trans)
at Jupiter.Transaction.NewCCCharge(Int32 StudentID, DateTime dtmCharge,
Decimal Amount, String Memo, String CCType, String Number, DateTime
dtmExpire, String NameOnCard, String Confirm, Int32 InstructorID, Boolean
IsCharge, Boolean IsOnline, SqlConnection cnn)
at Student_StudentRefund.ProcessTab(SqlConnection cnn)
at Student_StudentRefund.butOK_Click(Object sender, EventArgs e)
at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
at System.Web.UI.WebControls.Button.RaisePostBackEvent(String
eventArgument)
at
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
sourceControl, String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Signature
RAJ
bass_player - 20 Mar 2008 10:06 GMT
Looks like your ASP.NET web application is causing this problem. You need to
work with your application developer to check this further
> Hello,
>
[quoted text clipped - 109 lines]
> at System.Web.UI.Page.ProcessRequestMain(Boolean
> includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Sean - 20 Mar 2008 15:27 GMT
I would run a profiler on the system to see *why* it's timing out in
what seems to be a SQL statement (I'm not an ASP.NET guru, but it
looks like from the base sqlcommand object is what's getting the
timeout - so I would assume some type of sql statement is trying to
complete). This may give you some indication of why it's timing out or
perhaps let you see into approximately how long these queries should
take to execute normally and then how long they take to execute under
this odd timeout condition. I would also check to see if the vendor/in
house developer of this application has manually set a timeout time
(say of 30 seconds) and the query under this odd condition (say 45
seconds) time to execute. If that's the case I'd check to see why it's
taking so long and possibly tuning the queries/tables and staying away
from the application (unless of course it's the application, like I
said I'm no asp.net guru).
I would start Here: http://msdn2.microsoft.com/en-us/library/ms173757.aspx
-Sean
> Looks like your ASP.NET web application is causing this problem. You need to
> work with your application developer to check this further
[quoted text clipped - 117 lines]
>
> - Show quoted text -