We have a Windows net service. It was working fine more than three years.
But two months ago, we installed a new machine and new last version of the .NET Framework (v4.7). Also we updated the .NET Framework in the service because we need new features.
After that, the service started crashing every week, once time in a week.
Faulting application name: Service.exe, version: 0.0.0.0, time stamp: 0x5a2e8f7a
Faulting module name: clr.dll, version: 4.7.2053.0, time stamp: 0x58fa6d2a
Exception code: 0xc0000005
Fault offset: 0x0000000000057947
Faulting process id: 0x704
Faulting application start time: 0x01d38529f1ad4283
Faulting application path: C:\Octopus\Applications\Service\1.0.315\Service.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 8b138308-f165-11e7-8e89-1458d0b5ac3c
Application: Service.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FEF9F87947 (000007FEF9F30000) with exit code 80131506.
Application: Service.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FEF9F87947 (000007FEF9F30000) with exit code 80131506
Faulting application name: Service.exe, version: 0.0.0.0, time stamp: 0x5a2e8f7a
Faulting module name: clr.dll, version: 4.7.2053.0, time stamp: 0x58fa6d2a
Exception code: 0xc0000005
Fault offset: 0x00000000001bae0b
Faulting process id: 0xea4
Faulting application start time: 0x01d37e14ddc4b59a
Faulting application path: C:\Octopus\Applications\Service\1.0.315\Service.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 8e3458e1-ecae-11e7-8e89-1458d0b5ac3c
Application: Service.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FEFA0EAE0B (000007FEF9F30000) with exit code 80131506.
Do you have any clue why this can happen? In any case, I am strongly thinking about downgrading.
I had to uninstall DynaTrace
Just in case you have this installed...
https://answers.dynatrace.com/questions/190584/why-does-my-net-application-malfunction-after-upgr.html
https://answers.dynatrace.com/questions/190584/why-does-my-net-application-malfunction-after-upgr.html
Related
After a user closed the application. If the user have not had a reboot.
Next time when this user try to open the application will have an error :
The * application cannot start due to error: Another instance of the * application running
Investigate the windows event logs we found the following 2 events straight after user closed the application
Application: *.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.CannotUnloadAppDomainException
at System.AppDomain.Unload(System.AppDomain)
at Microsoft.ReportingServices.RefCountedAppDomain.Dispose()
at Microsoft.Reporting.WinForms.LocalReport+ReportRuntimeSetupHandler.ReleaseSandboxAppDomain()
at Microsoft.Reporting.WinForms.LocalReport.Dispose()
at Microsoft.Reporting.WinForms.ReportInfo.Dispose()
at Microsoft.Reporting.WinForms.ReportHierarchy.Clear()
at Microsoft.Reporting.WinForms.ReportViewer.Dispose(Boolean)
at System.ComponentModel.Component.Finalize()
&
Faulting application name: *.exe, version: *, time stamp: 0x62689e99
Faulting module name: KERNELBASE.dll, version: 10.0.18362.997, time stamp: 0x91b9349a
Exception code: 0xe0434352
Fault offset: 0x000000000003a719
Faulting process id: 0x2680
Faulting application start time: 0x01d865c193ffbd40
Faulting application path: exe file location
Faulting module path: C:\\Windows\\System32\\KERNELBASE.dll
Report Id: 723d10d5-0b8a-416a-8f68-92588e274303
Faulting package full name:
Faulting package-relative application ID:
Pretty struggling at the moment, and any ideas appreciated, thank you
I have a weird issue that I cannot solve.
I am using the following code to change my app language:
Windows.Globalization.ApplicationLanguages.PrimaryLanguageOverride = codeOfLanguage;
The codeOfLanguage variable is string and the error occurres when I am trying to change the language to "bg-BG" (same if I try "bg"). What happens is I get a Just-in-time debugger window in my face (despite I am currently debugging from VS2015) and the app crashes. I cannot catch the Exception from Studio.
I only found the following clue in the Application eventlog:
Faulting application name: {myAppName}, version: 1.0.0.0, time stamp: 0x5a3d1876
Faulting module name: KERNELBASE.dll, version: 10.0.14393.1770, time stamp: 0x59bf2bcf
Exception code: 0xc0000002
Fault offset: 0x000daa12
Faulting process id: 0x3ca4
Faulting application start time: 0x01d37b3249d8cc91
Faulting application path: {myAppPath}
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 56827555-577b-4276-8ef0-217065912b46
Faulting package full name: {myPackageName}
Faulting package-relative application ID: App
After restarting the app the language is changed to "bg-BG" and resources are loaded accordingly.
When I am changing the language back to English ("en-GB") the issue does not occur.
Does anybody have any idea how to move forward with this? Where could I find more info on the issue and the solution?
Thanks,
Gabor
My application crashed after running for some time.
I'm using .NET 4.6 on Windows Server 2012-R2.
Application is 64-bit.
I cannot find more detail about this bug code. I think I have all relevant updates installed.
This application has run cumulatively for thousands of hours before and this is the first time this particular bug happened.
Event viewer errors:
Faulting application name:ApplicationName, version: 1.0.0.0, time stamp: 0x561c9fd7
Faulting module name: clr.dll, version: 4.6.96.0, time stamp: 0x55b96716
Exception code: 0xe0004743
Fault offset: 0x00000000003ccf84
Faulting process id: 0xef4
Faulting application start time: 0x01d1058c3f5834e6
Faulting application path: ApplicationName
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 9765e800-7185-11e5-8177-0ae6116ba893
Second entry in the event viewer:
Application: ApplicationName
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FF837C2CF84 (00007FF837860000) with exit code e0004743.
The only similar issue reported in SO is The process was terminated due to an internal error in the .NET Runtime where GC issue / heap corruption was suggested.
I have created an installer project in WPF. when I run the application on my computer, it works fine. I set a minimum requirement for the .net framework 4.5. But if I run the application on another machine (with newly installed windows 7), the application crashes.
Below is event viewer log:
Installer exception
Faulting application name: MyInstaller.exe, version: 1.0.0.0, time stamp: 0x55572605
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17514, time stamp: 0x4ce7bafa
Exception code: 0xe0434352
Fault offset: 0x0000b727
Faulting process id: 0x398
Faulting application start time: 0x01d08fca117f3e62
Faulting application path: C:\Users\self\Downloads\MyInstaller.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 517dc0dd-fbbd-11e4-a332-b083fe4d72a6
Application: MyInstaller.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
Stack:
at MyInstaller.App.Main(System.String[])
I tried to create "Window event log" inside Main() try-catch method, but the application was not able to reach to that point.
When I send myinstaller.config.exe file with project exe file in the new installed machine, then it shows error. That the application does not meet requirement.
In my machine myinstaller.config.exe is not requirement, even after I uninstall framework 4.5 and 4.0.
I have a Windows Service running in "Local System account" context.
I can start the service successfully, but after a few minutes it crashes. I get following error in the event log
What could be the possible reason, and how to fix this issue?
Faulting application name: MyWindowsService.exe, version: 1.0.0.2993, time stamp: 0x554085eb
Faulting module name: SHLWAPI.dll, version: 6.3.9600.16384, time stamp: 0x521574db
Exception code: 0xc00000fd
Fault offset: 0x00005d66
Faulting process id: 0x14d4
Faulting application start time: 0x01d0830a94202cb3
Faulting application path: C:\Program Files\MyProject\Etswap Workflow Polling Service\MyWindowsService.exe
Faulting module path: C:\Windows\SYSTEM32\SHLWAPI.dll
Report Id: ff232358-eefe-11e4-94ea-08002787efe4
Faulting package full name:
Faulting package-relative application ID:
yes, it was a bug in the application only.
it was a rare scenario which was going into a deadlock situation.
Fixed