Application Error

Question

User-218479044 posted

Hi All,

I got an issue with ASP.Net Web application, SQL Server 2008, IIS 6,  on windows 2003 server. In the very peak time (morning to 15 o'clock), the application error are often, almost every 10 minutes. I see also the CPU and memory usage are very low.

How to trace and find the problem? I had tried to use loadby sos mscorwks and clrstack (can be seen below).

Thanks,

Andy

The error message as followed :

Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c8f9
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0xe2c
Faulting application start time: 0x01d1396c20f07c1c
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: deee34c2-a55f-11e5-8495-984be160104d

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: w3wp.exe
P2: 7.5.7601.17514
P3: 4ce7afa2
P4: StackHash_ed11
P5: 6.1.7601.17514
P6: 4ce7c8f9
P7: c0000374
P8: 00000000000c40f2
P9:
P10:

Attached files:
C:\Windows\Temp\WER35E.tmp.appcompat.txt
C:\Windows\Temp\WER38E.tmp.WERInternalMetadata.xml
C:\Windows\Temp\WER39F.tmp.hdmp
C:\Windows\Temp\WERBCA.tmp.mdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_w3wp.exe_ebabc46b14ebec32d227c7ae37ae138cad45dd_cab_09da0d9b

Analysis symbol:
Rechecking for solution: 0
Report Id: deee34c2-a55f-11e5-8495-984be160104d
Report Status: 4

Clrstack

=====

000000000557d680 000007fef3735a49 DomainNeutralILStubClass.IL_STUB(IntPtr, System.Guid ByRef, System.Data.OleDb.tagDBPARAMS, IntPtr ByRef, System.Object ByRef)
000000000557d7e0 000007fef37333f4 System.Data.OleDb.OleDbCommand.ExecuteCommandTextForMultpleResults(System.Data.OleDb.tagDBPARAMS, System.Object ByRef)
000000000557d850 000007fef3732e7f System.Data.OleDb.OleDbCommand.ExecuteCommandText(System.Object ByRef)
000000000557d8d0 000007fef3732d60 System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(System.Data.CommandBehavior, System.String)
000000000557d980 000007fef3732d99 System.Data.OleDb.OleDbCommand.ExecuteReader(System.Data.CommandBehavior)
000000000557d9e0 000007fef32cb5cd System.Data.OleDb.OleDbCommand.System.Data.IDbCommand.ExecuteReader(System.Data.CommandBehavior)
000000000557da10 000007fef32cb4bd System.Data.Common.DbDataAdapter.FillInternal(System.Data.DataSet, System.Data.DataTable[], Int32, Int32, System.String, System.Data.IDbCommand, System.Data.CommandBehavior)
000000000557dad0 000007fef36bf221 System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet, Int32, Int32, System.String, System.Data.IDbCommand, System.Data.CommandBehavior)
000000000557db80 000007ff001d31e2 System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet, System.String)
000000000557dc20 000007ff001de1eb Utils.Data.DB.GetDBData(System.Data.OleDb.OleDbCommand, System.String, Boolean)
000000000557dc90 000007ff001dde0d Utils.Data.DB.GetDBData(System.String, System.Object[,], System.String)
000000000557dce0 000007ff001db9af Utils.ProjectLogin+LoginTemplate.ResetDdlCompanyList(Boolean, System.String)
000000000557de10 000007fef2b5baf0 Utils.ProjectLogin+LoginTemplate.InstantiateIn(System.Web.UI.Control)
000000000557df60 000007fef22b0082 System.Web.UI.WebControls.Login.CreateChildControls()
000000000557dfb0 000007fef22afd6f System.Web.UI.Control.EnsureChildControls()
000000000557e010 000007fef22a9c10 System.Web.UI.Control.FindControl(System.String, Int32)
000000000557e060 000007fef22ab312 System.Web.UI.Page.ProcessPostData(System.Collections.Specialized.NameValueCollection, Boolean)
000000000557e100 000007fef22aa750 System.Web.UI.Page.ProcessRequestMain(Boolean, Boolean)
000000000557e1d0 000007fef22aa67b System.Web.UI.Page.ProcessRequest(Boolean, Boolean)
000000000557e230 000007fef22aa610 System.Web.UI.Page.ProcessRequest()
000000000557e290 000007ff001d7929 System.Web.UI.Page.ProcessRequest(System.Web.HttpContext)
000000000557e2f0 000007fef22b1ab7 ASP.util_webforms_login_aspx.ProcessRequest(System.Web.HttpContext)
000000000557e320 000007fef227571b System.Web.HttpApplication+CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
000000000557e3d0 000007fef2960561 System.Web.HttpApplication.ExecuteStep(IExecutionStep, Boolean ByRef)
000000000557e470 000007fef29511c2 System.Web.HttpApplication+PipelineStepManager.ResumeSteps(System.Exception)
000000000557e600 000007fef2932df9 System.Web.HttpApplication.BeginProcessRequestNotification(System.Web.HttpContext, System.AsyncCallback)
000000000557e650 000007fef2a59931 System.Web.HttpRuntime.ProcessRequestNotificationPrivate(System.Web.Hosting.IIS7WorkerRequest, System.Web.HttpContext)
000000000557e770 000007fef2a59d8b System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr, IntPtr, IntPtr, Int32)
000000000557e8f0 000007fef2a59294 System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr, IntPtr, IntPtr, Int32)
000000000557e950 000007fef9d9f18a DomainNeutralILStubClass.IL_STUB(Int64, Int64, Int64, Int32)
000000000557f180 000007fef2a59a60 DomainNeutralILStubClass.IL_STUB(IntPtr, System.Web.RequestNotificationStatus ByRef)
000000000557f260 000007fef2a59d8b System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr, IntPtr, IntPtr, Int32)
000000000557f3e0 000007fef2a59294 System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr, IntPtr, IntPtr, Int32)
000000000557f440 000007fef9d9f3db DomainNeutralILStubClass.IL_STUB(Int64, Int64, Int64, Int32)

Answer 1

User-218479044 posted

After upgrading to IIS7, the issue still arise. Please help.

Answer 2

User-166373564 posted

Hi Andy,

According those error messages that you provided, it’s a crashing issue for w3wp.exe.

Please refer to the following article and troubleshoot the w3wp.exe crash.

Debugging Faulting Application w3wp.exe Crashes

http://blog.whitesites.com/Debugging-Faulting-Application-w3wp-exe-Crashes__634424707278896484_blog.htm

Best regards,

Angie

Answer 3

User-218479044 posted

Hi Angie,

Thanks for your info. I had did as on article and the result you can refer to my first post. I can't find any loop sequence. Don't know whether it has something to do with SQLOleDB or not.

Thanks,

Andy

Answer 4

User-166373564 posted

Hi Andy,

In Microsoft SQL Server 2005, Microsoft SQL Server 2008 or SQL Server 2008 R2,

you configure a merge replication that uses Web synchronization on a database.

When the Web synchronization occurs, the W3WP.exe process of Internet Information Services (IIS) stops unexpectedly.

You could upgrade SQL Server 2008.

https://support.microsoft.com/en-us/kb/942712

Angie

Answer 5

User-218479044 posted

Hi Angie,

Thanks for the information. How do I check if the web synchronization of merge replication is turned on?

I had turned on windows update that include application update also. do i need to download the sql server service pack again?

Thanks,

Andy

Answer 6

User-166373564 posted

Hi,

For information about how to configure the components that are required for Web synchronization,please see

Web Synchronization for Merge Replication

https://msdn.microsoft.com/en-us/library/ms151763.aspx

You could download the sql server service pack again.

Regards,

Angie

Answer 7

User-218479044 posted

Hi Angie,

I had just downloaded and installed SQL Server R2 SP 3, however the error is still there.

I am still afraid to implement your suggestion to update hotfix as it gave me warning as per email from them (attached below). Any idea for me to still go ahead?

Thanks,

Andy

IMPORTANT INFORMATION

For your convenience, we put the hotfix that you requested on an HTTP site. You can download the hotfix from this site without us filling up your e-mail inbox.

WARNING   This hotfix has not undergone full testing. Therefore, it is intended only for systems or computers that are experiencing the exact problem that is described in the one or more Microsoft Knowledge Base articles that are listed in "KB Article Numbers" field in the table at the end of this e-mail message. If you are not sure whether any special compatibility or installation issues are associated with this hotfix, we encourage you to wait for the next service pack release. The service pack will include a fully tested version of this fix. We understand that it can be difficult to determine whether any compatibility or installation issues are associated with a hotfix. If you want confirmation that this hotfix addresses your specific problem, or if you want to confirm whether any special compatibility or installation issues are associated with this hotfix, support professionals in Customer Support Services can help you with that. For information about how to contact support, copy the following link and then paste it into your Web browser:

   http://support.microsoft.com/contactus/

For additional support options, please copy the following link and then paste it into your Web browser:

   http://support.microsoft.com/

Before you install this hotfix
------------------------------

If you decide to install this hotfix, please note the following items:

Do not deploy a hotfix in a production environment without first testing the hotfix.

Back up the system or the computer that will receive the hotfix before you install the hotfix.

Additional hotfix information
-----------------------------

NOTE   For your convenience, we send the hotfix location to you in a hyperlink. To connect to this hotfix location, you can click the hyperlink in the "Location" field that is listed in the table at the end of this e-mail message to have your Web browser open that location. However, sometimes e-mail program settings disable hyperlinks. If the hyperlink in this e-mail message is disabled, please copy the hyperlink in the "Location" field and then pastes it into the address box of your Web browser. Make sure that you include the exact text (without spaces) between the parentheses in the http:// address.


Package:
-----------------------------------------------------------
-----------------------------------------------------------
KB Article Number(s): 2089486, 2214666, 2222267, 2256829, 2260502, 2287990, 2288638, 2292725, 2295460, 2295878, 2296070, 2297709, 2306162, 2344600, 2352413, 2379466, 2380361, 2404865, 2407172, 2412203, 2413430, 2422010, 2428310, 2428916, 2430162, 2431178, 2431212, 2432235, 2438347, 2444085, 2444150, 2445751, 2445896, 2446036, 2448991, 2452564, 2455614, 2456499, 2458438, 2459027, 2462084, 2463203, 2465349, 2475741, 2476357, 2496375, 942712, 975752, 982564, 982808
Language: All (Global)
Platform: x64
Location: (http://hotfixv4.microsoft.com/SQL%20Server%202008%20R2/nosp/SQLServer2008R2_RTM_CU5_2438347_10_50_17/10.50.1753.0/free/424969_intl_x64_zip.exe)


NOTE   Make sure that you include all the text between "(" and ")" when you visit this hotfix location.

[e-mail]	Jan 5 (3 days ago)
to me