Microsoft distributes Microsoft SQL Server 2008 Service Pack 1(SP1) and SQL Server 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 Service Pack 1(SP1) and SQL Server 2008 R2 fix release.

Important This article contains information that shows you how to help lower security settings or how to turn off security features on a computer. You can make these changes to work around a specific problem. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this workaround in your particular environment. If you implement this workaround, take any appropriate additional steps to help protect your computer.

Symptoms

Consider the following scenario:

  • You run Internet Explorer 8 on a computer that is running Windows Vista or a later version of a Windows operating system. Note You do not run Internet Explorer 8 as an administrator.

  • You enable the following features, or the following features are already enabled:

    • The User Account Control (UAC) feature is enabled in Windows.

    • The Enable Protected Mode check box is selected for the Internet zone, for the Local Intranet zone, and for the Trusted sites zone.

  • You use Internet Explorer 8 to access the Report Manager website for Microsoft SQL Server 2008 Reporting Services (SSRS 2008) or SQL Server 2008 R2 .

  • You create a report on the website, and then you try to print the report.

  • You receive a message that advises you to install the RSClientPrintControl ActiveX control in Internet Explorer 8.

  • You install the control.

In this scenario, the report is not printed, and then you receive the following error message:

An error occurred during this operation

Cause

This issue occurs because the RSClientPrintControl ActiveX control handles WM_INITDIALOG messages for the printing dialog box incorrectly.

Resolution

Cumulative update information

SQL Server 2008 SP1

The fix for this issue was first released in Cumulative Update 11. For more information about how to obtain this cumulative update package for SQL Server 2008 Service Pack 1 (SP1), click the following article number to view the article in the Microsoft Knowledge Base:

2413738 Cumulative update package 11 for SQL Server 2008 Service Pack 1 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 Service Pack 1 (SP1) fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 5. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:

2438347 Cumulative Update package 5 for SQL Server 2008 R2 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 2 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2467239 Cumulative update package 2 for SQL Server 2008 Service Pack 2Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Workaround

Warning This workaround may make a computer or a network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.To work around this issue, click to clear the Enable Protected Mode check box in the Local Intranet zone and in the Trusted sites zone. To do this, follow these steps:

  1. Open Internet Explorer 8, click Tools, click Internet Options, and then click Security tab.

  2. Click the Local Intranet zone, and then click to clear the Enable Protected Mode check box.

  3. Click the Trusted sites zone, and then click to clear the Enable Protected Mode check box.

  4. Restart Internet Explorer 8.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.