Modify Package Issue

  • I'm trying to modify a daily backup package I built awhile back, but when I right-click on it and click "modify", I get a message that says "Agent XPs component is turned off".

    I went to the SQL Server 2005 Surface Area configurator, and turned on "XP_clamshell", which I assume is the issue. It errored out with a message about "AWE". I don't understand. Can anyone help?

    I should point out I'm running this instance of SS2k5 on MS Server 2008 (64bit)

    Jim

  • XP_CMDSHELL allows you to run OS commands via T-SQL

    What you wanted to do was either

    sp_configure 'show advanced options', 1;

    GO

    RECONFIGURE;

    GO

    sp_configure 'Agent XPs', 1;

    GO

    RECONFIGURE

    GO

    OR since you are familiar with the Surface Area Configuration tool within SQL | Click on SQL Server Agent | change Startup to Automatic | click Start

    Chris Powell

    George: You're kidding.
    Elroy: Nope.
    George: Then lie to me and say you're kidding.

  • When I ran your T-SQL, I got a message set I've seen before:

    Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.

    Msg 5845, Level 16, State 1, Line 1

    Address Windowing Extensions (AWE) requires the 'lock pages in memory' privilege which is not currently present in the access token of the process.

    Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.

    Msg 5845, Level 16, State 1, Line 1

    Address Windowing Extensions (AWE) requires the 'lock pages in memory' privilege which is not currently present in the access token of the process.

    Jim

  • Hi Jim

    Mr. Jetson's script should work to solve the problems with the Agent XP's being disabled. The problem here is that you have 2 problems.

    When you enable Agent XPs, you're essentially changing the "Configured Value" of "Agent XP's" from 0 to 1. When you run RECONFIGURE, you're asking SQL to make all the "Configured Values" on your server to their "Run Values" where possible. This RECONFIGURE applies to all configured values.

    Your second problem here is that you have AWE enabled on this server. If you check sp_configure you'll see that the "Configured Value" is 1, but the "Run Value" is 0. So when you run RECONFIGURE, SQL tries to enable the Agent XPs and also enable AWE. Your AWE isn't working because your SQL Server service account doesn't have the OS-level "Lock Pages In Memory" privilege.

    -- Confirm that AWE configured_value = 1, but run_value = 0. Assuming confirmation, proceed with below steps.

    EXEC sp_configure 'awe enabled'

    -- If so, temporarily turn off AWE so that its error doesn't block other configurations

    EXEC sp_configure 'awe enabled', 0

    -- RECONFIGURE will now not be "blocked" by the erroring AWE setting

    RECONFIGURE

    -- Reset the AWE value to its original value. Note that AWE isn't fixed, you're just putting things back where they were.

    EXEC sp_configure 'awe enabled', 1

    -- Go fix the AWE problem

    -- http://technet.microsoft.com/en-us/library/ms190673(v=sql.90).aspx

    -- http://technet.microsoft.com/en-us/library/ms190730(v=sql.90).aspx

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

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