Killing a process

Question

We have a custom application that was developed for Windows Server 2003 but have issues since migrating this to Windows Server 2008 R2.

Part of the application/process is to kill a Windows process with C# code. This worked fine on Windows 2003, but on Windows 2008 R2 the code fails to kill the process. Has anyone come across anything similar or have any ideas what the issue could be?

Answer 1

Exception code: 0xe053534f

Always inspiring when the problem has something to do with this site's name. Microsoft programmers often pick exception codes that can be decoded to a 3 letter acronym. The exception code for a C++ exception is 0xe04d5343, the last 3 hex bytes decode to "MSC", Microsoft C++. The exception code for a managed exception is 0xe0434f4d, "COM+" which was the early name for .NET

Give your exception the same treatment and you'll get "SSO". Which means "soft stack overflow". That is the exact same thing as a regular stack overflow, except that the system can predict it up front. It knows that, if it completes the call, the program will bomb because there is not enough stack space left.

Exactly why your app is bombing on a stack overflow isn't clear from the info you provided. You'll have to debug it.