Geek Answers Handbook

Error in Microsoft.NET \ Framework \ v4.0.30319 \ clr.dll

 Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7a5f8 Faulting module name: clr.dll, version: 4.0.30319.18063, time stamp: 0x526767c6 Exception code: 0xc00000fd Fault offset: 0x0007717d Faulting process id: 0x1728 Finging process application start time: 0x01cf972772f04132 Faulting application path: C: \ Windows \ SysWOW64 \ inetsrv \ w3wp.exe Faulting module path: C: \ Windows \ Microsoft.NET \ Framework \ v4.0.30319 \ clr.dll Report Id: b4d0c430-031a- 11e4-a40f-0050569e40da

Keep getting this error when the MSM loader service fails? We downloaded the patch that comes with the Windows updates and no improvements.

Any ideas as to why?

+7
dll
source share
1 answer

TL; DR:

I encountered the same error. This is because the client repeatedly called the WCF service, where the method called itself recursively, thereby throwing a StackOverflowException .

Long answer:

This happened in the WCF application using .Net 4.5 . All of our services ( .svc s) started crashing one by one until the entire application pool started reporting HTTP 503 error. The application pool was dead.

Digging through the application logs and then the EventViewer logs, we found the same message as the OP.

For some time, we continued to restart the application pool, but after a while it will work again.

The application pool suddenly stabilized at 2 p.m., and we have some kind of system operation that starts noon until 2 p.m. ... We figured that this should be connected with this. We were able to discover that this was due to a merge error when a method that retains a call to itself recursively had no parameters or return type. This probably threw a StackOverflowException so that the application pool failed.

+1
source share

More articles:


All Articles