I'm having migration issues with a site that used to run on 2003 server 32bit to a windows 2008 r2 server 64 bit. and ASP version 1.1. Iv'e taken all the steps needed (I hope) to ensure it functions correctly. Such as,
downloaded ASP.NET V1.1 onto the server
selected the app pool to run this ASP version and set it to classic mode
ensured that CGI is Allowed on the .NET version
application is running in 32bit mode
But I'm getting the "This Page cannot be displayed" message when navigating to it with the browser. I noticed this error in the event logs -
Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7a5f8
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00db8960
Faulting process id: 0xcb4
Faulting application start time: 0x01d0b40cf800bfca
Faulting application path: C:\Windows\SysWOW64\inetsrv\w3wp.exe
Faulting module path: unknown
Report Id: 35c785b2-2000-11e5-be06-005056b20078
Anyone have ideas on how to rectify this issue?
Thank you.
In IIS, find the ApplicationPool that is executing your web application
Advanced settings
Set "Enable 32 bit application" to true
IISReset
Related
On a Windows instance a specific application pool stops every 15 days and we have to manually restart that Under the event logs we are getting dotnet clr.dll error given below.
Faulting application name: w3wp.exe, version: 10.0.17763.1, time
stamp: 0xcfdb13d8 Faulting module name: clr.dll, version: 4.7.3610.0,
time stamp: 0x5e13fa89 Exception code: 0xc00000fd Fault offset:
0x000000000012ebdc Faulting process id: 0x2678 Faulting application
start time: 0x01d7069cd23d6f15 Faulting application path:
c:\windows\system32\inetsrv\w3wp.exe Faulting module path:
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Report Id:
b44401f0-97b2-4b8c-8fba-703227faec12 Faulting package full name:
Faulting package-relative application ID:
What should be the process for debugging this issue to get the root cause?
I am new to server management and processes so please bear with me.
Thanks in advance.
It looks like you have a StackOverflow Exception, which is caused by unbounded recursion (a function repeatedly calling itself, etc). You can track the problem down using DebugDiag and WinDbg.
DebugDiag can be configured to generate a crash dump when the StackOverflowException occurs.
Download at Debug Diagnostic Tool.
About how to use the Debug Diagnostics tool to troubleshoot a process that has stopped responding in IIS you can refer to this link: How to use the Debug Diagnostics tool.
Debugging tools for Windows is part of the Windows SDK and can be downloaded at Download the Windows Driver Kit (WDK). To use WinDbg, you'll need to get the symbols files. Download the symbol files and put them in a local folder. Getting Started with WinDbg.
In the results, it should be clear what the problem is.
I've just updated a web app to ASP.NET Core 2.0 running on IIS 7.5 on Windows Server 2008 R2. Since upgrading the app randomly crashes and leaves it with a 503 Service Unavailable response. It can run for several hours before crashing.
Before crashing I get a couple of warnings in event viewer and then a error.
Example of warning:
A process serving application pool '<My app pool>' terminated unexpectedly. The process id was '14896'. The process exit code was '0x0'.
Another example of warning:
A process serving application pool '<My app pool>' suffered a fatal communication error with the Windows Process Activation Service. The process id was '18252'. The data field contains the error number.
Example of error:
Application pool '<My app pool>' is being automatically disabled due to a series of failures in the process(es) serving that application pool.
I guess the crash/error comes from rapid failure feature in IIS, but I can't pinpoint the cause of the original warnings.
I have a few runtime errors like the ones below too, but I'm sure how related they are:
{
"#t": "2017-11-20T15:24:24.3190000Z",
"#m": "Request timed out.",
"#i": "0307d0fb",
"#l": "Error",
"#x": "Microsoft.AspNetCore.Server.Kestrel.Core.BadHttpRequestException: Request timed out.\r\n at Microsoft.AspNetCore.Server.Kestrel.Internal.System.IO.Pipelines.PipeCompletion.ThrowFailed()\r\n at Microsoft.AspNetCore.Server.Kestrel.Internal.System.IO.Pipelines.Pipe.GetResult(ReadResult& result)\r\n at Microsoft.AspNetCore.Server.Kestrel.Internal.System.IO.Pipelines.Pipe.Microsoft.AspNetCore.Server.Kestrel.Internal.System.IO.Pipelines.IReadableBufferAwaiter.GetResult()\r\n at Microsoft.AspNetCore.Server.Kestrel.Internal.System.IO.Pipelines.ReadableBufferAwaitable.GetResult()\r\n at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.MessageBody.<ConsumeAsync>d__24.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.Frame`1.<ProcessRequestsAsync>d__2.MoveNext()",
"SourceContext": "xxxx.Extensions.GlobalExceptionFilter",
"ActionId": "97118189-7c25-427b-82c7-10b3d885a146",
"ActionName": "xxxx.Controllers.FileController.Upload (xxxx)",
"RequestId": "0HL9G4JA0VTIJ:00000073",
"RequestPath": "/api/file"
}
Event viewer also reports errors like these for the app pool in question:
An unhandled win32 exception occurred in w3wp.exe [18244]. Just-In-Time debugging this exception failed with the following error: Debugger could not be started because no user is logged on.
Check the documentation index for 'Just-in-time debugging, errors' for more information.
And...
Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: aspnetcore.dll, version: 7.1.1982.0, time stamp: 0x594ab904
Exception code: 0xc0000005
Fault offset: 0x000000000000fe3b
Faulting process id: 0x1ef0
Faulting application start time: 0x01d3622d8eb0e8c0
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\system32\inetsrv\aspnetcore.dll
Report Id: ce37e890-ce20-11e7-9f93-00155dc82c03
I could really use some help trying to find the source of these crashes.
Microsoft has updated the IIS module for ASP.NET Core now and that solves the problem.
I have recently set up a Windows 2016 Server. I set up my .net application on the server. However, the moment I access the application, the w3wp crashes and shuts down the application pool by itself.
Event Viewer gives out 2 errors.
1) Application: w3wp.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FF8FEDDE899 (00007FF8FEC60000) with exit code 80131506.
2) Faulting application name: w3wp.exe, version: 10.0.14393.0, time stamp: 0x57899b8a
Faulting module name: clr.dll, version: 4.6.1637.0, time stamp: 0x586fe714
Exception code: 0xc0000005
Fault offset: 0x000000000017e899
Faulting process id: 0x1bec
Faulting application start time: 0x01d29cca82c75315
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 99612f7d-0679-40b3-aa26-d44ca19c44b8
Faulting package full name:
Faulting package-relative application ID:
Event ID = 1000
the application is built on .net framework 4.6.1. Since the server is Win 2016 it is shipped with framework 4.6.2. I have installed a test application with .net 4.6.2 framework and an application with 4.6.1 framework (Visual Studio) and they run fine. But my main application gives out the above errors.
I have executed svc /SCANNOW which has found some corrupt files and successfully repaired them. But this has not helped. IIS version of the server is 10.0.14393.0.
Any help would be appreciated. Thanks
There could be a hotfix for this RAnand - check out the link to Microsoft support link
Some ASP.NET 4.5 websites throw the following error continuously on every request after the latest windows updates (August 12th 2015).
Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18933, time stamp: 0x55a6a16f
Exception code: 0xe0434352
Fault offset: 0x000000000000b3dd
Faulting process id: 0x2bb8
Faulting application start time: 0x01d0d5ac15c25873
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 58cdc89d-419f-11e5-8650-782bcbaf10f4
I confirmed on other PC's that the windows update is to blame, both for windows 7 and 8.1.
To try and fix it, I tried updating nuget packages, switching the .NET framework to 4.5.2, reconfiguring IIS, etc
The solution is to uninstall .NET 4.6 RC and install the regular .NET 4.6.
I had mine fixed by uninstalling Security Update for Microsoft .Net Framework 4.6 RC KB3083186. Microsoft should correct this soon for MVS 2013 and MVS 2015
I´m working on the migration for a CRM 4.0 on-premise system to CRM 2013 in which one of the most used features is the campaign module.Now I´m facing a problem with mail merge, when I try to distribute a campaign activity:
The process starts, the mails are generated and sent, but the window for tracking the campaign activities is not presented and the process crashes in background. I already un- and resintalled the Outlook client, but this didn´t resolve tghe problem.
In the event log I find the following entry:
Faulting application name: Microsoft.Crm.Application.Outlook.WebFormsHost.exe, version: 6.0.0.809, time stamp: 0x523d509d
Faulting module name: crmaddin.dll, version: 6.0.0.809, time stamp: 0x523d5152
Exception code: 0xc0000005
Fault offset: 0x0000a75a
Faulting process id: 0x748
Faulting application start time: 0x01cf2bcd4fa6bcd8
Faulting application path: C:\Program Files (x86)\Microsoft Dynamics CRM\Client\res\web\bin\Microsoft.Crm.Application.Outlook.WebFormsHost.exe
Faulting module path: C:\Program Files (x86)\Microsoft Dynamics CRM\Client\bin\crmaddin.dll
Report Id: b9413ac9-97c0-11e3-80d3-000c2982ff89
Faulting package full name:
Faulting package-relative application ID:
The CRM System is Version 6.0.0.809
and I´m using Office 2010.
Has anyone faced this problem before?
The Possible cause could be the corruption of file - Microsoft.Crm.Application.Outlook.WebFormsHost.exe located here - C:\Program Files (x86)\Microsoft Dynamics CRM\Client\res\web\bin\
Do a clean uninstall by deleting the Microsoft Dynamics CRM folder from programs file and reinstall CRM client later. You can also try to repair it using suggestion here - http://community.dynamics.com/crm/b/xrminadynamicsbox/archive/2014/02/09/solution-crm-2013-outlook-client-407-proxy-authentication-required-exception.aspx
However, I would recommend a clean uninstall and reinstall.
Thanks,
Aasif