MS11-049: Description of the security update for SQL Server 2008 R2 GDR: June 14, 2011

• Home users:
  http://www.microsoft.com/security/pc-security/bulletins/201106.aspx

  (http://www.microsoft.com/security/pc-security/bulletins/201106.aspx)
  Skip the details: Download the updates for your home computer or laptop from the Microsoft Update website now:
  http://update.microsoft.com/microsoftupdate/

  (http://update.microsoft.com/microsoftupdate/)
• IT professionals:
  http://www.microsoft.com/technet/security/bulletin/MS11-049.mspx

  (http://www.microsoft.com/technet/security/bulletin/MS11-049.mspx)

How to obtain help and support for this security update

Back to the top | Give Feedback

Known issues with this security update

• After you install this security update, the original (RTM) version of SQL Server 2008 R2 may not start. This issue is known to occur on systems that are running the original release version of SQL Server 2008 R2 on which Utility Control Point is configured. On these systems, the security update fails to apply the Upgrade Scripts. When the issue occurs, you may receive a message that resembles the following in the SQL Server error log:
  
  
  Date, Time spid7s Executing [sysutility_mdw].sysutility_ucp_core.sp_initialize_mdw_internal
  Date, Time spid7s SQL Server blocked access to procedure 'sys.xp_qv' of component 'Agent XPs' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Agent XPs' by using sp_configure. For more information about enabling 'Agent XPs', see "Surface Area Configuration" in SQL Server Books Online.
  Date, Time spid7s Error: 15281, Severity: 16, State: 1.
  Date, Time spid7s SQL Server blocked access to procedure 'sys.xp_qv' of component 'Agent XPs' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Agent XPs' by using sp_configure. For more information about enabling 'Agent XPs', see "Surface Area Configuration" in SQL Server Books Online.
  Date, Time spid7s Error: 912, Severity: 21, State: 2.
  Date, Time spid7s Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 15281, state 1, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
  Date, Time spid7s Error: 3417, Severity: 21, State: 3.
  Date, Time spid7s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
  
  
  This is a known issue that is documented in the following article in the Microsoft Knowledge Base:
  2163980

  (http://support.microsoft.com/kb/2163980/ )

  FIX: The SQL Server service cannot start after you install cumulative update package 1 for SQL Server 2008 R2 if a UCP exists in the instance of SQL Server
  Note This issue is specific to security update 2494088 for SQL Server 2008 R2. This issue only applies to systems that run the original release version of SQL Server 2008 R2. If you already applied a cumulative update (CU) or a critical on-demand (COD) hotfix to the system and are no longer running the original release version of SQL Server 2008 R2, you must install security update 2494086 instead of security update 2494088. Because security update 2494086 includes the fix from update 2163980, this issue does not occur to systems in that configuration.
  To resolve this issue, use either of the following methods, appropriate for your situation:
  • Security update 2494088 already is applied and the original release version of SQL Server 2008 R2 is now in a failed state.
    If SQL Server 2008 R2 is already in failed state, follow the steps mentioned in the Workaround section of Microsoft Knowledge Base article 2163980:
    2163980

    (http://support.microsoft.com/kb/2163980/ )

    FIX: The SQL Server service cannot start after you install cumulative update package 1 for SQL Server 2008 R2 if a UCP exists in the instance of SQL Server
    After you apply the workaround that is described in KB2163980, restart SQL Server. The upgrade then is completed successfully.
  • The original version of SQL Server 2008 R2 is in a working state. Security update 2494088 is not applied
    To avoid this issue, follow these steps:
    1. Stop the SQL Server Agent service for the associated instance. On a clustered SQL Server, the SQL Server Agent resource must be taken offline.
       
       Important If SQL Server Agent service is running when setup is started, setup stops the service. This disables the Agent XPs sp_configure option.
    2. Log on to SQL Server and make sure that the sp_configure Agent XPs option is enabled.
    3. Install security update 2494088.
    4. Start the SQL Server Agent service after security update 2494088 is installed.
    More Information Security update 2494088 was released on June 14th 2011 as part of security bulletin MS11-049. This security bulletin affects SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2. These security updates are available through automatic updates. For more information, visit the following Microsoft webpage:
    http://www.microsoft.com/technet/security/bulletin/MS11-049.mspx

    (http://www.microsoft.com/technet/security/bulletin/MS11-049.mspx)
    For more information about the terminology that is used to describe SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
    935897

    (http://support.microsoft.com/kb/935897/ )

    An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
• When you use the /? switch or the /Help switch with this security update package, you receive an error message.
  
  This issue occurs because Microsoft SQL Server 2008 R2 packages use a new a new IACCEPTSQLSERVERLICENSETERMS command line argument that is required for command line installations. To display Help for these packages, use the following switches:
  • /IACCEPTSQLSERVERLICENSETERMS /?
  • /IACCEPTSQLSERVERLICENSETERMS /Help
  For example, type the following to view the Help information:
  
  SQLServer2008R2-KB2494086-x64 /IACCEPTSQLSERVERLICENSETERMS /?
• After you install this security update, the Add or Remove Program entries for this security update do not have "Security Update" in the title of the security update.
  
  Note This is only a cosmetic issue and does not affect the functionality of the security update.
• After you install this security update, the installation wizard shows the security update as an "Update Program" instead of a "Security Update."
  
  Note This is only a cosmetic issue and does not affect the functionality of the security update.

Back to the top | Give Feedback

For all supported x86-based systems

SQL Analysis Services

Business Intelligence Development Studio

Database Services Common Core

Database Services Core Shared

Integration Services

SQL Reporting Services

Management Studio

SQL Tools

SQL Native Client

SQL Native Client

SQL Native Client

For all supported x64-based systems

Analysis Services SharePoint Integration

SQL Analysis Services

Business Intelligence Development Studio

Database Services Common Core

Database Services Core Instance

Database Services Core Shared

Integration Services

SQL Reporting Services

Management Studio

SQL Tools

SQL Native Client

For all supported IA-64-based systems

Database Services Common Core

Database Services Core Instance

Database Services Core Shared

Integration Services

SQL Reporting Services

Management Studio

SQL Tools

SQL Native Client

SQL Analysis Services

Analysis Services SharePoint Integration

Back to the top | Give Feedback

• SQL Server 2008 R2 Management Studio Express

Back to the top | Give Feedback