Post reply

xp_cmdShell

  • May 19, 2006 at 1:23 am

    #190685

    Hi,

    Anyone had any experience of xp_cmdshell suddenly producing just a null.

    If I run xp_cmdshell 'dir *.* /w' the output is NULL.

    I do notice that with the first job to use xp_cmdshell, once it fails,  the process remains runnable under Current Activity. And even when I kill the process it shows as runnable, KILLED/RollBAck but with no resources ???????????

    Is there is fix without restarting the sql service.

    Thanks...Graeme

  • May 19, 2006 at 9:09 am

    #639028

    it could be the account does not have right permissions. Hung connections tend to need a server service restart to clear.

    as far as I could see xp_cmdshell produces a null when it doesn't do anything ( e.g. generates an error )

    [font="Comic Sans MS"]The GrumpyOldDBA[/font]
    www.grumpyolddba.co.uk
    http://sqlblogcasts.com/blogs/grumpyolddba/

  • May 19, 2006 at 9:47 am

    #639046

    Thanks Colin.

    It looks like a server process was hogging memory....bit of a worry but one to keep an eye on.

    Thanks for your input.

    Graeme

  • May 22, 2006 at 9:33 am

    #639305

    It's not possible to kill extended stored procedures (xp) using kill statement. Am I right ?

Viewing 4 posts - 1 through 3 (of 3 total)

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