Post reply

Process xp_get_mapi_profiles can''t be killed

  • July 8, 2005 at 8:32 am

    #109991

    Hi

    I have a process "EXECUTE master.dbo.xp_get_mapi_profiles" wich I can't kill

    Please, could someone help me.

    Thanks!

    Celso

  • July 8, 2005 at 9:38 am

    #572441

    Unfortunately you can't kill an extended stored procedure once it's become disconnected, we had this sort of thing happen a while back and I ended up researching it pretty heavily.  The main problem is that the XP sits there and keeps eating up CPU and memory, it's never going to finish so it'll just keep growing and growing.

    I wasn't brave enough to try the following on a production box and ended up going for the stop/start option which does work, however, it did work on the test server so maybe one day.

    If you have a look on sysinternals website you can download an app called 'process explorerer', install that on your sql server and go down to the threads that SQL is using, you should be able to identify the one used by the XP.

    Once you've found the thread you can simply kill it.

    I wouldn't recommend that anyone does this on a production box as it's messy and may cause memory problems or crashes further down the line (The OS thread dies but the entry for the SPID remains till SQL is restarted, but the good news is that it doesn't use any more resources).

    It did work so I leave it up to you whether to do it or not (but don't say I didn't warn you)

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply