Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Microsoft distributes Microsoft SQL Server 2008 R2 and Microsoft SQL Server 2008 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 R2 or SQL Server 2008 fix release.

Summary

A hotfix is available that enables Microsoft SQL Server 2008 Reporting Services and Microsoft SQL Server 2008 R2 Reporting Services to use a 2048-bit RSA key to encrypt a Reporting Services key.

Before you apply the hotfix, SQL Server 2008 Reporting Services and SQL Server 2008 R2 Reporting Services uses a 1024-bit RSA key to encrypt a 3DES Reporting Services key. As required by Federal Information Processing Standards (FIPS), the minimum length of an RSA key for key transport scheme is 2048 bit since December 31, 2010. This hotfix enables SQL Server 2008 Reporting Services and SQL Server 2008 R2 Reporting Services to still be FIPS compliant after this standard takes effect.

Resolution

Cumulative update information

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

2279604
Cumulative update 10 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 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

Service pack information

The fix is included in SQL Server 2008 Service Pack 2. For more information about how to obtain the latest service pack for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:

968382How to obtain the latest service pack for SQL Server 2008

SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 1 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:

2289254 Cumulative update 1 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. 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:

2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 3. 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:

2261464 Cumulative update package 3 for SQL Server 2008 R2Note 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

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

References

For more information about encrypted report server data, visit the following Microsoft Developer Network (MSDN) website:

Storing encrypted report server dataFor more information about the how to configure and manage encryption keys, visit the following MSDN website:

Configuring and managing encryption keysFor more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:

935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems

For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499New naming schema for Microsoft SQL Server software update packagesFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

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.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×