15 สิงหาคม 2554 9:19
Hi there all,
I hope someone can help me with our issue we are having. We have a major issue with a process that we can not kill and the only way to get rid of the process is to reboot the machine.
I have tried killing it from the normal task manager but no joy.
I have tried killing it using the taskkill /F command from a command prompt and no joy. The command reports as sucessful but the process remains.
I have tried to start task manager with system rights by calling "psexec -s -i -d taskmgr" and attempting to kill the process but no joy
I have tried killing it from Process Explorer but again the process remains.
Nothing I do will kill this process. Even logging off and logging back on will not kill this process.
Using Process Explorer I notice that there is on stubborn thread that is in the Wait:Executive state. I have tried to kill this thread using Process Explorer but again no joy.
We are using Windows Server 2008 R2 64-Bit. The server is brand new and windows is freshly installed.
Now heres the thing. We have brought two identical servers from Dell with the same specs and the same OS installed and I can not replicate this issue on the other server. Only on this server, under certain circumstances does this server process hang and can not be restarted!
I have also changed the compatability mode by setting it the process to "Windows 2003" but this has not helped.
I have noticed in Process Explorer that DEP is turned on but im not sure this has got any bearing on the issue ot not.
Please, can someone help??
15 สิงหาคม 2554 11:43
I have used a trick with scheduler for some time. Schedule an interactive task with SYSTEM permission. Open Task manager and try to kill the process.
(It would be interesting to use Process Explorer to find possible dependences.)
15 สิงหาคม 2554 13:02
It seems that this funcationality was removed in Windows 2008 and Windows 7. You can now, no longer schedule a task and have it run under the user account where you can interact with it.
so this command:
schtasks /create /ru system /sc once /st 14:11 /tn test1 /tr cmd.exe /it
will start cmd.exe under the SYSTEM process but it has no window and can not be interacted with!!!
15 สิงหาคม 2554 13:19
by the way:
schtasks /create /ru system /sc once /st 13:16 /tn test1 /tr "taskkill /F /PID 1576" /it
did not work.. The process still remains!!!!!!!
15 สิงหาคม 2554 15:19
1. Any clue about the name/origin of process described by PID 1576?
2. It seems to be HW specific. Have you asked Dell support for the help? (Changing parts may help to find the faulty one.)
3. I would suggest "crossposting" in Sysinternal Forum.
4. Give it a try via GUI setting of Scheduled task. On the first sheet change the user to NT AUTHORITY\SYSTEM and add parameter and batch file as needed. If it does not work, is there any information in History?
- แก้ไขโดย Milos PuchtaMicrosoft Community Contributor 15 สิงหาคม 2554 15:34 Add 4.
15 สิงหาคม 2554 15:49
Thank you Milos.
The process in question is SchOPC.exe. It is a 3rd party OPC Server that we use to communicate to devices in the field. I also believe it is called into existence via COM. I dont know if that helps.
I will try the GUI setting/NT Authourity\System setting as you suggest and get back to you with my findings..
16 สิงหาคม 2554 6:16
1. Is this software compatible with operating system?
2. Is it possible to start OPC server with lower priority
3. I would recommend "srossposting" to the OPC server vendor forum or address the support.
16 สิงหาคม 2554 8:52
I tried your suggestion of modifying the scheduled task via the GUI but still no joy!
In answer to your other questions, this software ran fine on Windows Server 2003. I have also set the compatability to Server 2003 also.
I will try starting the server with a lower priority to see if that helps. Can I ask, what would the side effects of doing this be??
17 สิงหาคม 2554 12:46
Windows 2008 is different to a large extent when compared to W2K3 environment. Especially in security. Is this application compatible with W2K8 formally? (I mean vendor software prerequisites. I afraid that it is not the case.).
Give pls different thread/process priority a try. If the problem is caused by taking too much resources, then at lower priorty the dispatcher would give less operating time to this process. If the process wait for something or is trying to enter something without appropriate rights, then this will not help.
Can you mine more information from Process Monitor, namely the dependences on other threads, possible leaks,etc?
- แก้ไขโดย Milos PuchtaMicrosoft Community Contributor 18 สิงหาคม 2554 6:12 Typo
14 มิถุนายน 2555 14:00
We are also having the same issue. We could not kill a process from task manager and the only way to get rid of the process is to reboot the machine. I have tried all you have tried to kill the process. Ours is also windows Server 2008 R2 64-bit. Please help if you have any resolution.
19 กันยายน 2555 8:28