Develop Reference

tapisrv.exe hangs other processes when terminating from a developed program

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

System.IO.FileLoadException from WshShell.Exec in Classic ASP on IIS 7.5

I’m using the DidiSoft OpenPGP for .NET library to compile C# into an exe that gets executed by Classic ASP. The goal is to update the security on this legacy website to use PGP. It’s an old site so we can’t rewrite it without significant cost.
The reason I tried to use this library was that when we would call compiled C# EXE’s that referenced:
using System.Security.Cryptography;
I would get a blank output in ASP, and IIS would throw an error in Event Log similar to this:
Faulting application name: PGPTest.exe, version: 1.0.0.51, time stamp: 0x52f28ee5
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1116
Exception code: 0xe0434352
Fault offset: 0x0000c41f
Faulting process id: 0x5f08
Faulting application start time: 0x01cf22a83ae734f4
Faulting application path: d:\inetpub\_bin\[redacted website name]\PGPTest.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 789751fa-8e9b-11e3-87e1-0050568e508f
Application: PGPTest.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException
Stack:
at PGPTest.Program.Main(System.String[])
================
.NET Runtime version 4.0.30319.1008 - There was a failure initializing profiling API attach infrastructure. This process will not allow a profiler to attach. HRESULT: 0x80004005
Process ID (decimal): 24328. Message ID: [0x2509].
So when I use either the DidiSoft OpenPGP or System.Security.Cryptography I get errors.
In Classic ASP the application is called with:
WshShell.Exec(%pathtoexe%)
We do receive output IF if we change the Application Pool to run under LocalSystem instead of NetworkService. So it seems to be related to permissions somehow.
Our server is running:
Server 2008 R2
.NET 4.0
We're assuming running the application pool under LocalSystem is unsafe; is this correct?
Any ideas on how we can get this to work?
Thank you
Update: The author of the library has confirmed to me that it does use System.Security.Cryptography for some of its algorithms.
Update 2: To ulluoink: If you read this at all you'd realize that this DOES in-fact have to do with Classic ASP. How do I know you ask? Because when moving the code from a C# app that Classic ASP executes into a ASP.NET 4 Web API app, the SAME EXACT CODE on the exact same server works just fine. It appears to be a permissions issue tied DIRECTLY to Classic ASP's execution privileges.
So, the current work around is to deploy our code that references System.Security.Cryptography to the same server in an ASP.NET Web API app. We're POSTing to the ASP.NET app in Classic ASP; specifically sending data serialized with this: http://www.aspjson.com/

Yes running a site exposed to the internet as LocalSystem is unsafe. You can use filemon or processmon while loading the page to see which files need permissions from which users.
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

Visual C# Command Line Compiler has stopped working?

I have a project iv been working on for sometime, but today when i tried to build the solution the following message was displayed.
This message appears twice when i try run my project, but the project is able to run after this appears.
The problem is i cant publish as this stops my publishing.
The problem signature reads the following:
Problem Event Name: APPCRASH
Application Name: csc.exe
Application Version: 4.0.30319.17929
Application Timestamp: 4ffa73cb
Fault Module Name: bitguard.dll
Fault Module Version: 2.6.1694.246
Fault Module Timestamp: 524a99fc
Exception Code: c0000005 Exception
Offset: 0017966f
OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 7177
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
I have run and build this project many times as well as publish, but this now has become a problem out of the blue.
This is only happening with one project and my other run and build fine.
I have posted a bounty on a similar question as i need this resolved quickly:
Command Line Compiler stops working in specific project
Thanks in advance.

Found the solution with the help of Joe's comment above.
Following the Fault Module name you can see the problem file is bitguard.dll.
http://www.spywareremove.com/file/bitguarddll-367251/
Adw Cleaner is a free malware cleaner that helped me find bitguard and remove it safely.
http://download.cnet.com/AdwCleaner/3000-7786_4-75851221.html
The problem has been solved.

How to troubleshoot error: “Program stopped working APPCRASH”

I have a log and a try catch in this console app, but does not seem to get that far.
Works fine on my dev machine, does not on Win Server 2008. Event viewer has the same info as below.
I understand there's not much to go on here, but that's what I know. All prev deployments worked, so I'm at a loss.
Please don't close, and help me solve this problem. I will answer any questions I can.
Thanks.
Description:
Stopped working
Problem signature:
Problem Event Name: APPCRASH
Application Name: LoaderLive.exe
Application Version: 2.0.1.0
Application Timestamp: 4ef176d6
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.17651
Fault Module Timestamp: 4e211319
Exception Code: e0434f4d
Exception Offset: 0000b9bc
OS Version: 6.1.7601.2.1.0.272.7
Locale ID: 1033
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

If you have a top-level try/catch and it's not catching the exception, it might be because the fault is occurring at a very low level (e.g. somewhere in a native code library), too early (before your Main even starts), or on another thread (where your try/catch can't "reach").
To find out what is going on, run the application under a debugger. If you have Visual Studio installed on the target machine, you can do it from there (open the EXE and "Start Debugging"). If not, you can use windbg.exe / cdb.exe (available as Debugging Tools for Windows in the Windows SDK). Within the debugger, you should be able to see where the fault occurs, as it will by default stop on any fatal exception.

.NET application won't open in windows 7

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.