xp_cmdshell disabled after reboot

  • I have a SQL Server 2008 STD server that has xp_cmdshell enabled for a vendor process. Whenever the server reboots, xp_cmdshell gets disabled. See below for messages in SQL Error Log.

    10/13/2010 03:11:41 Configuration option 'xp_cmdshell' changed from 1 to 0. Run the RECONFIGURE statement to install.

    10/13/2010 03:11:41 Configuration option 'xp_cmdshell' changed from 1 to 0. Run the RECONFIGURE statement to install.

    10/13/2010 03:11:41 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'STANDBY'.

    10/13/2010 03:11:41 Configuration option 'xp_cmdshell' changed from 1 to 1. Run the RECONFIGURE statement to install.

    10/13/2010 03:11:41 Configuration option 'xp_cmdshell' changed from 1 to 1. Run the RECONFIGURE statement to install.

    10/13/2010 03:11:41 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'STANDBY'.

    10/13/2010 03:11:41 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'STANDBY'.

    10/13/2010 03:11:41 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.

    10/13/2010 03:11:41 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.

    The server rebooted due to Windows Updates. For some reason, SQL Server wants to enabled it and then disable it. How do I get it to stay enabled after reboot? I enabled xp_cmdshell in the past using Surface Area Configuration and running sp_configure/reconfigure.

  • With 2008 you do it with "facets". Right click on the server instance in the SSMC and select facets......

    The probability of survival is inversely proportional to the angle of arrival.

  • sp_configure will still work, it will be interesting to see what is disabling it, are there any startup stored procedures?

    Hope this helps,
    Rich

    [p]
    [/p]

  • That's it! I had a start up procedure that enabled xp_cmdshell, ran some scripts, and then disabled it. I removed the disable statement.

    Thank you!

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

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