SQLTeam.com | Weblogs | Forums

Need to kill SQL Server child process


Windows Server 2012 R2 ,SQL Server 2012

I am running into an issue with a child process called 'ISServerExec', which is spawned from the 'sqlservr.exec' process... The short story is that ISServerExec will not terminate after an SSIS job completes. The process will eventually consume all CPU causing the node to die causing a failover. I have tried adding code to kill these rogue ISServerExec processes, but I get messages that state that the processes cannot be terminated. Here are example statements for both command line and powershell steps generated by a job to kill the rogue processes:


EXEC master.dbo.xp_cmdshell 'TASKKILL /pid 7000 /f /t'


stop-process 7000

Both commands return the message - ' ERROR: The process with PID 7000 (child process of PID 5894) could not be terminated.'

The process tree shows that PID 7000 (ISServerExec) is a child process from 'sqlservr.exe' -PID 5894 - Of course, I don't want to kill my SQL instance, just to kill ISServerExec...

Any ideas or thoughts to address with would be helpful...


This sounds like a bug. Are you up to date on the hotfixes for SQL Server 2012? What does SELECT @@VERSION show?


The SQL Server version is shown below - thanks...

Microsoft SQL Server 2012 - 11.0.5058.0 (X64)
May 14 2014 18:34:29
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor)


Yup, you're missing SP1


Hmmm - well I am actually running SP2 - https://support.microsoft.com/en-us/kb/321185

Please advise....


That's not what it says in your version info


can you run this query and post the results?

SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')


Here are the results - thanks

11.0.5058.0 SP2 Enterprise Edition (64-bit)


Yes 11.0.5058 is SP2, but it's without the latest hotfix (CU6, build 5592). I'm not saying that this issue is fixed in CU6 or CU1-CU5, however it's the first thing that I'd try. If the latest hotfix doesn't do the trick, you'll need to open a support case with Microsoft.



Not sure if this is related - but does show there are some fixes available for this process.


OK - thanks for this info... I did manage to find and cmd utility called 'pskill' that I incorporated in the code as a band-aid for now... I will look into the CU's mentioned. Thanks!