I'm using the following code (any tried many variations) in a web page that is supposed to kill a process on the server:
Process scriptProc = new Process(); SecureString password = new SecureString(); password.AppendChar('p'); password.AppendChar('s'); password.AppendChar('s'); password.AppendChar('w'); password.AppendChar('d'); scriptProc.StartInfo.UserName = "mylocaluser"; scriptProc.StartInfo.Password = password; scriptProc.StartInfo.FileName = @"C:\WINDOWS\System32\WScript.exe"; scriptProc.StartInfo.Arguments = @"c:\windows\system32\killMyApp.vbs"; scriptProc.StartInfo.UseShellExecute = false; scriptProc.Start(); scriptProc.WaitForExit(); scriptProc.Close();
The VBS file is supposed to kill a different w3wp.exe process, which tends to lock up. This is a legacy web app that we are going to replace soon, but in the meantime we need to limp by and force the app to shut down when this happens.
I should note that killing w3wp.exe is not something I.T. professionals do.
What happens is, WScript.exe is in task manager every time I run the kill page, and it never goes away.
The process WScript.exe (and I tried others such a psexec.exe) is being run as a local user with admin rights (and I tried other types of users including domain admins) when run from IIS, but it works when run from the command line on the server.