So I've developed a program in C# in VS2013 that utilizes TAPI to make a phone call on 1 button. Originally I used the TAPI3 library, but after discovering its not in a working state I switched to JulMar's TAPI 2 wrapper. I'm using Windows 8 64 bit, and although the program is used elsewhere only on Win8 64 bit machines does this issue occur.
Whenever I make a phone call from my program, nothing abnormal happens and the phone call is made. Code runs and everything is OK. But when I close the form where TAPI is used (i.e terminating tapisrv.exe) the service shuts down, and then drags other processes with it every time. This is interfering with drive mappings, cryptography services and other services depending on the PC. The error log in event viewer is below;
Faulting application name: svchost.exe_TapiSrv, version: 6.3.9600.17415, time stamp: 0x54504177
Faulting module name: ntdll.dll, version: 6.3.9600.18007, time stamp: 0x55c4c16b
Exception code: 0xc0000008
Fault offset: 0x000000000009311a
Faulting process ID: 0xd4
Faulting application start time: 0x01d0f45613fffb86
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report ID: 41b6967a-604a-11e5-829f-f8b156d8c3e7
Faulting package full name:
Faulting package-relative application ID:
I also get an information bubble following it with the following information:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: svchost.exe_TapiSrv
P2: 6.3.9600.17415
P3: 54504177
P4: ntdll.dll
P5: 6.3.9600.18007
P6: 55c4c16b
P7: c0000008
P8: 000000000009311a
P9:
P10:
Attached files:
C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\WERE5B1.tmp.appcompat.txt
C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\WERE5D1.tmp.WERInternalMetadata.xml
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_svchost.exe_Tapi_881875fa9eb711f34fe5d53182d2b0c47578647_f1915213_cab_053de5df\memory.hdmp
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_svchost.exe_Tapi_881875fa9eb711f34fe5d53182d2b0c47578647_f1915213_cab_053de5df\triagedump.dmp
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_svchost.exe_Tapi_881875fa9eb711f34fe5d53182d2b0c47578647_f1915213_cab_053de5df
Analysis symbol:
Rechecking for solution: 0
Report ID: 41b6967a-604a-11e5-829f-f8b156d8c3e7
Report Status: 4
Hashed bucket:
Has anybody seen this before? Am I doing something wrong? I know other issues exist regarding TAPI on win8 64 bit but I cant seem to find this specific problem.
Thanks in advance.
My guess: You have a buggy TSP that crashes your service when the TAPI is uninitialized.
I know no such crashes just from the TAPI. If the crash happens inside the service there is always a TSP involved in such problems.
Try to run the TAPI service isolated in its own service host. This will prevent troubles when the service crashes.
Open the created DMP files with your VS you received and check what DLL / code causes the crash.
I found running TapiSrv in its own group at least isolates the crash to itself. Run the following in an elevated command prompt:
sc config Tapisrv type= own
Related
I've been re-writing an app and run into (again :-( ) that it's working in both Debug and Release modes, but the packaged app crashes on launch. i.e. never even gets to the app's home screen. I had this happen first time around, but eventually solved it from Googled results, however this time I've reached a dead-end and not sure what else I can do. Things I tried previously and worked but no effect this time...
deleted all .vs folders, clean, build.
tick "compile with .net native tool chain" (in fact that is now ticked by default I found. So I tried turning it off, and the packaging then failed with some error about the manifest not matching something now)
3 I may be able to adapt, but not sure how yet. Last time I had ZXing in the app, and that ended up being the problem. It was solved by adding
List<Assembly> assembliesToInclude=new List<Assembly>();
assembliesToInclude.Add(typeof(ZXing.Net.Mobile.Forms.WindowsUniversal.ZXingScannerViewRenderer).GetTypeInfo().Assembly);
Xamarin.Forms.Forms.Init(e,assembliesToInclude);
I don't have ZXing in the new app yet, BUT one package I've added that I had before is CsvHelper, so I suspect that may be the cause. Note that my previous version of the packaged app was working before I added it, so that adds to the suspicion.
But I can't find anyone who has run into this, so I'm not sure how I can find what assemblies would need to be added? (when it happened with ZXing, I just copied what someone else had said. They in fact had listed a whle bunch of ZXing assemblies, but I ended up being able to narrow it down to one by adding all and then taking away one at a time)
So...
any ideas on how to find what CsvHelper assemblies might need to be added? i.e. how do I even find what assemblies it has in it to begin with?
any other suggestions? This is the error I'm getting from the Windows Event Viewer - not sure if any of these numbers actually tell me anything useful, and if so which ones and how?
Faulting application name: Myappname.UWP.exe, version: 1.0.0.0, time stamp: 0x62158bed
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1503, time stamp: 0xb2acaea9
Exception code: 0xc000027b
Fault offset: 0x000000000010b382
Faulting process ID: 0x5660
Faulting application start time: 0x01d82857d5105201
Faulting application path: C:\Program Files\WindowsApps\00bf2865-c554-4952-9142-753983df67d5_0.3.0.0_x64__b71kk8c7kdz5g\Myappname.UWP.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: fb10dc41-a7f1-4d74-ad8e-befa62556dcc
Faulting package full name: 00bf2865-c554-4952-9142-753983df67d5_0.3.0.0_x64__b71kk8c7kdz5g
Faulting package-relative application ID: App
Thanks,
Donald.
I have an application that I've written that crashes intermittently, but I'm unable to capture an exception at the application layer. I always get an entry in the event log but doesn't give me much info:
Faulting application name: BCS-UI.exe, version: 1.0.11.0, time stamp: 0x5c0edcbd
Faulting module name: ntdll.dll, version: 10.0.17134.376, time stamp: 0x4358e406
Exception code: 0xc0000374
Fault offset: 0x000d8829
Faulting process id: 0x39b0
Faulting application start time: 0x01d49161c80079a0
Faulting application path: C:\Gogs Local\SMR_Windows_UI\BCS-UI\BCS-UI\bin\Release\BCS-UI.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 1fbc4761-d256-44b0-99b0-4d9d758e4fe0
Faulting package full name:
Faulting package-relative application ID:
- System
- Provider
[ Name] Application Error
- EventID 1000
[ Qualifiers] 0
Level 2
Task 100
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2018-12-11T15:12:28.109191000Z
EventRecordID 23318
Channel Application
Computer Leviathan
Security
- EventData
BCS-UI.exe
1.0.11.0
5c0edcbd
ntdll.dll
10.0.17134.376
4358e406
c0000374
000d8829
39b0
01d49161c80079a0
C:\Gogs Local\SMR_Windows_UI\BCS-UI\BCS-UI\bin\Release\BCS-UI.exe
C:\WINDOWS\SYSTEM32\ntdll.dll
1fbc4761-d256-44b0-99b0-4d9d758e4fe0
As you can see, I get this:
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll.
I'm not sure what that is or how it relates to the crashes, but I've been able to reproduce it on multiple machines and I'm at a loss on how to determine the cause or prevent it from happening.
Update: I've gotten to a point where the application crashes on startup with the above reason. It gets to the end of the MainWindow constructor (it is a WPF application), sits there for about 10 seconds on a white screen and then dies. I've rolled back to older versions of the software and reproduced this behavior. I have also moved it to another machine and did NOT see this behavior, so my current theory is in agreement with what was said in the comments - that something corrupted the heap and it only gets cleared up on a reboot.
Update 2: I'm able to produce this error message when running outside of the debugger, although when running in the debugger, I'm not able to get it to stop on an exception:
a generic error occurred in GDI+
So that's what I'll be hunting today. Interestingly and disturbingly enough, the app crashes every time on startup, even after rebooting. The same behavior does not occur on other machines at this time.
To debug these kind of system internal issues, I suggest you try Process Monitor.
Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, Registry and process/thread activity.
Basically you need to look out for the "NAME NOT FOUND" errors, which means missing dlls or registry keys, or any other suspisious errors in the monitor screen.
The last time I had a similar crash in my app that pointed to ntdll.dll as the faulting module, the reality was that my own code had a memory leak. I did a strcpy on a string that was not allocated memory. Something like,
char * str;
strcpy(str, "Hello");
I found this after a strenuous walkthrough of my code.
Check your code for leaks.
For those having a similar issue and only get this error but nothing else:
A breakpoint instruction (__debugbreak() statement or a similar call) was executed
Try update the NuGet packages in your solution.
As soon as I updated a handful of Microsoft packages, that mysterious error stopped occurring.
My programm is running without any problems, on my current laptop (x64). But when I try to run it on an other PC (x86) it crashes before starting. I also tried to change the platformtarget, as described in this answer:
XMLParseException occurs
I also catched all unhandled exceptions. That delivers me two exceptions:
I also got that from reliability history:
Faulting application name: LoginDemo.exe, version: 1.0.0.0, time
stamp: 0x56c19003 Faulting module name: KERNELBASE.dll, version:
6.1.7601.17651, time stamp: 0x4e2111c0 Exception code: 0xe0434352 Fault offset: 0x0000d36f Faulting process id: 0x4b0 Faulting
application start time: 0x01d167cd96535e01 Faulting application path:
C:\Users\hgservice\Desktop\Temp\LoginTool2\LoginDemo\bin\Release\LoginDemo.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll Report Id:
d6435b26-d3c0-11e5-b9a7-001999d6cbe5
I also read that the problem could occure because the programm tries to import a DLL while running, but all DLLs that I need for the exe are in the same folder. And as I said on my laptop it is working fine. Has anyone an idea what the problem could be?
This problem has nothing in common with WPF as such. If we analyse the stacktrace we can see that it is thrown by pcsc-sharp library. The more careful analysis will show that NoServiceException exception was thrown because the following native method returned an error:
[DllImport(WINSCARD_DLL, CharSet = CharSet.Auto)]
private static extern int SCardEstablishContext(...)
More precisely NoServiceException is mapped to the SCARD_E_NO_SERVICE (0x8010001D) error. It means that probably SmartCard service on your laptop is not running. To fix it: press Win+R, type services.msc and start SmartCard service.
This problem can be also caused by differences between various versions of Windows (for details see this question).
Another cause of this problem might be the lack of sufficient permissions (see this article).
Okay guys I fixed it. As Michał Komorowski and Jon Skeet already answered, the problem was that the Smard Card sevice was not running. The answer of Michał Komorowski is almost correct. The only thing I had to do furthermore, was to set the startup type on "manual". After that I could start the Smart Card service and now everything is working.
I'm currently writing a file scanning utility and am using IFilters in a WinForms application.
I moved the code that scans the files to a Backgroundworker and since I have done that the PDF IFilter application is throwing errors.
This is the error I'm getting in the event log:
Faulting application name: Scanner.vshost.exe, version: 11.0.50727.1, time stamp: 0x5011d445
Faulting module name: PDFL60.dll, version: 6.1.0.0, time stamp: 0x40bcc106
Exception code: 0xc0000005
Fault offset: 0x0000a3c5
Faulting process id: 0x1e8
Faulting application start time: 0x01ce9f4fc83fac44
Faulting application path: C:\Development\Scanner\Scanner\bin\Debug\Scanner.vshost.exe
Faulting module path: C:\Program Files\Adobe\PDF IFilter 6.0\PDFL60.dll
Report Id: 6a4c3638-0b44-11e3-bb16-082e5f03ae88
The worrying thing is that it is taking VSHost out and doesn't happen on every PDF. Some of the them are fine.
Has anyone else had this error or can anyone shed any light on what might be causing it ?
It seems that the latest IFilters in Adobe 8 onwards only support the stream interface used by the Search indexer in Windows. This explains why I was getting 'no interface supported' using the latest versions.
V6.0 of the IFilter becomes flaky when not used in a single threaded application as can be seen here
The first solution I came across was to use Foxit PDF IFilter which works like a charm and if I could squeeze $600 out of my client would certainly buy. I had no problems running using this IFilter.
The second and free solution was to use the Adbobe IFilter 5.0. Nearly 10 years old but implements the file interface and is stable.
Another solution might be to switch to 64 bit. V9.0 of the 64 bit filter from Adobe is working and is stable.
I created a pretty simple c# application using visual studio 2010 on windows xp. It compiles, runs and debugs fine on my machine. I even built it for release and ran the .exe on my machine and another windows xp machine perfectly fine. When I send the release folder with the .exe file and they open it, nothing happens! No errors or anything, just blank!
.NET version 4 framework installed
It is a windows form application.
UPDATE: Details from OP's comments given to one of the answers below:
Hey everyone, thanks for the ideas. I
copied what I found on my friends
windows 7 machine event log and this
is what it said:
Application: ePrescribing.exe Framework Version: v4.0.30319
Description: The process was
terminated due to an unhandled
exception. Exception Info:
System.IO.FileNotFoundException Stack:
at
ePrescribing.frmApp.InitializeComponent()
at ePrescribing.frmApp..ctor() at
ePrescribing.Program.Main()
Faulting application name: ePrescribing.exe, version: 1.0.0.0,
time stamp: 0x4d61e693 Faulting module
name: KERNELBASE.dll, version:
6.1.7600.16385, time stamp: 0x4a5bdbdf Exception code: 0xe0434352 Fault
offset: 0x0000b727 Faulting process
id: 0xb38 Faulting application start
time: 0x01cbe1dbe6d4ba2d Faulting
application path:
C:\Users\Duane\Downloads\ePrescribing.exe
Faulting module path:
C:\Windows\syswow64\KERNELBASE.dll
Report Id:
266adc61-4dcf-11e0-8438-e0cb4e197cde –
Fault bucket , type 0 Event Name: CLR20r3 Response: Not available
Cab Id: 0 Problem signature: P1:
eprescribing.exe P2: 1.0.0.0 P3:
4d61e693 P4: ePrescribing P5: 1.0.0.0
P6: 4d61e693 P7: 28 P8: e P9:
System.IO.FileNotFoundException P10: –
I removed the only area where I
thought there would be a file load
(for the picturebox loading
profile.jpg) and still got the same
error. Any ideas?
First, you might try checking the Event Viewer for any relevant errors messages (as stated above).
Next, make sure they have .NET installed (as stated above).
Then, try adding an UnhandledExceptionEventHandler to your application and in that handler, try to at least write a simple log/text file containing the exception that caused your application to exit.
Make sure the latest .NET framework is installed.
Check .NET framework installed on win7 computer equal your application framework target.
Check in the process explorer that it's running but didn't show you anything.
Check event log for crash reports.
Try to add logging to your application in different places and add unhandled error handlers.
Additionly to other answers I would also check whether your app compiled against x86/x64 runtime
Have you included a manifest file?
Take a look at this.
Or this...
Are you accessing any folders via static paths instead of environment variables? That could cause issues between these versions of Windows.
You should check if all other third party assemblies can be found either in GAC or app folder
Referenced assembly may be missing from target computer. Please set Copy Local=True for all referenced library. This may solve your issue.