Microsoft SQL Server 2012 Service Pack 1 fixes have been released as one downloadable file. Given that the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 Service Pack 1 fix release.
Symptoms
Consider the following scenario:
-
You have a computer that is running Microsoft SQL Server 2012 Reporting Services (SSRS 2012).
-
You install Service Pack 1 for SSRS 2012 on the computer.
-
You have Federal Information Processing Standard (FIPS) standard enabled on the computer.
-
You run a report that contains multivalued parameters.
In this scenario, the report does not appear, and you receive the following error message:
ui!ReportManager_0-1!bc4! DateTime:: e ERROR: HTTP status code --> 500
-------Details--------
System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
at System.Security.Cryptography.SHA512Managed..ctor()
at Microsoft.Reporting.WebForms.MultiValidValuesSelector.SelectedIndicies.ComputeValidValuesHash(IEnumerable`1 validValues)
at Microsoft.Reporting.WebForms.MultiValidValuesSelector.SelectedIndicies..ctor(IEnumerable`1 validValues)
Resolution
Cumulative update information
Cumulative Update 4 for SQL Server 2012 SP1
The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to go to the article in the Microsoft Knowledge Base:
2833645 Cumulative update 4 for SQL Server 2012 SP1Note 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 2012 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 go to the article in the Microsoft Knowledge Base:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released
Status
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 the FIPS in SQL Server 2012, click the following article number to go to the article in the Microsoft Knowledge Base:
2733626 Instructions for using SQL Server 2012 in the FIPS 140-2-compliant mode For more information about the Incremental Servicing Model for SQL Server, click the following article number to go to 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 go to the article in the Microsoft Knowledge Base:
822499 Naming schema for Microsoft SQL Server software update packages For more information about software update terminology, click the following article number to go to the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
