I am trying to debug my asp.net , which calls a api (which is a 3rd party wrapper). On calling the below method it crashes.
private void RegisterCallbacks()
{
_instance.Callbacks.RegisterCallbacks(LogCallback, StatusCallback, BusyCallback, ExceptionCallback);
}
Here _instance is of that API. It crashes IIS and no error.. Any ideas what could be wrong?
Getting below in eventvwr
Faulting application name: iisexpress.exe, version: 10.0.14358.1000, time stamp: 0x574fc56b
Faulting module name: HybirRelease32.dll, version: 0.0.0.0, time stamp: 0x597ec186
Exception code: 0xc00000fd
Fault offset: 0x001cffe7
Faulting process id: 0x814
Faulting application start time: 0x01d315fa7acca3f0
Faulting application path: C:\Program Files (x86)\IIS Express\iisexpress.exe
Faulting module path: C:\Test\xxx.dll
Report Id: 32057b9d-8f56-45c9-abc6-64771c99c4ba
Faulting package full name:
Faulting package-relative application ID:
Publish the hosted application as debug mode, then go to visual studio debug-> Attach to process -> w3wp.exe(find in 'user name' column your hosted name) select and attach. you can debug the application in IIS host
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 crashes without any application error logging, when I checked Event viewer I found below info. Can some explain why this would happen and how to prevent it?
Faulting application name: MyApplication.exe, version: 1.0.0.0, time
stamp: 0x5964fac7 Faulting module name: KERNELBASE.dll, version:
6.1.7601.23807, time stamp: 0x5915f98e Exception code: 0xe0434352 Fault offset: 0x0000c54f Faulting process id:
0x1494 Faulting application start time: 0x01d300cbc9034bc0
Faulting application path: Path of MyApplication.exe Faulting
module path: C:\Windows\syswow64\KERNELBASE.dll Report Id:
b1f21346-6cbf-11e7-bb68-005056ad2203
I was building a WPF application in C# and packaging it using the MSIX packager/installer. Everything was fine until I updated Visual Studio to 16.10.2. Then something strange started to happen. The code would run perfectly in Debug and Release configuration but when I installed the application from MSIX it failed to run.
There were no coding errors.
The Event Log gave this error..
Faulting application name: [app name here], version: [app version here], time stamp: 0x609308e7
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1023, time stamp: 0x924f9cdb
Exception code: 0xe0434352
Fault offset: 0x0000000000034b89
Faulting process ID: 0xf3c
Faulting application start time: 0x01d7659e116b2c8c
I tried almost everything but nothing seem to fix it. Then I noticed the the 'obj' folder had become huge, so I deleted it and low and behold that fixed the problem.
I know this is old, but thought I'd post Luke's advice as an answer since it solved my problem.
As Luke mentioned in a comment above, the issue for me was an unhandled exception that was happening on startup. Once I wrapped the startup code in a try catch, I found the problem which was totally a bug in my app, nothing to do with kernalbase.dll or any other external dependency or reference.
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