Need Help to close w3wp.exe

Question

0.00/5 (No votes)

See more:

Hi,

I have created a console application to close w3wp exe , below is the code.

C#

public static void KillProcessByNameAndUser(string ProcessName, string ProcessUserName, int HasStartedForHours)
       {
           Process[] foundProcesses = Process.GetProcessesByName(ProcessName);
          
           foreach (Process p in foundProcesses)
           {         
               p.Kill();           
           }
        }

when I run it as a normal exe by clicking it working final, but when i call it in my asp.net page it also close the w3wp exe, but it also stopping the IIS application pool. I need only to stop the w3wp.exe not the IIS application pool. This is how I called it in my asp.net page.

C#

Process p = new Process();
            p.StartInfo.FileName = @"C:\inetpub\wwwroot\Kill\Debug\Kill.exe";
            p.Start();

Please help asap why is that happening and any solution for this.

Posted 15-Sep-15 3:09am

Dipayan Basu

Add a Solution

Comments

F-ES Sitecore 15-Sep-15 9:22am

I think this is one of those situations where you should explain the problem you're trying to solve rather than stating why your chosen solution doesn't work, as there might be a batter way of doing things.

Dipayan Basu 15-Sep-15 9:25am

Actually I am trying to close all opened w3wp.exe and excel.exe after automatic scheduled execution of websites.

Dave Kreskowiak 15-Sep-15 9:30am

WHY??

Do you realize that w3wp.exe is what is running you website? If you stop that process OF COURSE it's going to kill your application pool.

Again, WHY do you think you need to do this? WHAT "automatic scheduled execution of websites"? What does "execution of websites" even mean?

F-ES Sitecore 15-Sep-15 9:31am

Automating Excel from asp.net isn't supported. You should use a method of manipulating Excel files that is such as the odbc driver, Microsoft's XML SDK, or third party libraries like aspose, docx etc. That way you won't need to kill your processes to release copies of Excel.

Dipayan Basu 15-Sep-15 10:08am

We have previously coded projects, so we can't change in them, what we have to do is closing the running exe's , we don't having problems in closing the excel exe, we are facing problem in closing the w3wp exe. as it stopping the iis application pool.

F-ES Sitecore 15-Sep-15 10:16am

The app pool is hosted in that exe, so killing it is going to kill the pool.

Dipayan Basu 15-Sep-15 10:20am

But by using the console application I am able to kill the exe only, not the app pool, but calling the exe from asp.net page is stopping the service.

Dave Kreskowiak 15-Sep-15 10:32am

Yeah, and it ALWAYS WILL. You cannot kill W3WP.EXE and NOT stop a set of websites. That's the process that's running them!!

Oh, and there is the possibility that you have multiple copies of W3WP.EXE running. Killing one will not affect the others so, yeah, you can kill one and still have YOUR website running.

Richard Deeming 15-Sep-15 12:40pm

Read Considerations for server-side Automation of Office[^] - using Excel Interop is not supported in unattended applications like ASP.NET, and is liable to break in interesting ways.

There are various ways to create Excel spreadsheets on the server without using Office interop. For example:
EPPlus[^]
ClosedXML[^]
The OpenXML SDK[^]

And, as the others have said, w3wp.exe IS the app pool. If you kill the process, you kill the app pool.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Rakesh Meel · Answer 1 · 2015-09-15T03:50:00

you have to send excel a "WindowClose" message in Sequence to forcefully close the process.

You will be use these API functions

Private Declare Function OpenProcess Lib "kernel32" (ByVal dwDesiredAccess As Long, ByVal bInheritHandle As Long, ByVal dwProcessId As Long) As Long
Private Declare Function TerminateProcess Lib "kernel32" (ByVal hProcess As Long, ByVal uExitCode As Long) As Long
Private Declare Function CloseHandle Lib "kernel32" (ByVal hObject As Long) As Long
Private Declare Function GetWindowThreadProcessId Lib "user32" (ByVal hWnd As Long, lpdwProcessId As Long) As Long
Public Declare Function FindWindow Lib "user32" Alias "FindWindowA" (ByVal lpClassName As String, ByVal lpWindowName As String) As Long

And it should be look something like:

// First, Find handle 
hWindow = FindWindow(vbNullString, "Excel")
//Find proccess ID
GetWindowThreadProcessId(hWindow, ProcessValueID)
//Kill the process
ProcessValue = OpenProcess(PROCESS_ALL_ACCESS, CLng(0), ProcessValueID)
TerminateProcess(ProcessValue, CLng(0))
CloseHandle ProcessValueID