FIX: "An error has occurred during report processing" error message when you try to preview an SSRS 2008 R2 or SSRS 2012 report after you set the dataset collation to Greek or Greek_100

Article ID: 2708027 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 1 (SP1) 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 Service Pack 1 (SP1) fix release.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenario:
  • You create a dataset for a Microsoft SQL Server 2008 R2 Reporting Services (SSRS 2008 R2) or Microsoft SQL Server 2012 Report Services (SSRS 2012) report in SQL Server Business Intelligence Development Studio (BIDS).
  • You right-click the dataset and select Dataset Properties in the Report Data pane.
  • In the Dataset Properties dialog box, you select Option. Then, you select Greek or Greek_100 in the Collation drop-down list.
  • You try to preview the SSRS 2008 R2 report.
In this scenario, you receive the following error message:

An error occurred during local report processing.
An error has occurred during report processing.
Culture ID 66568 (0x10408) is not a supported culture.
Parameter name: culture

Back to the top | Give Feedback

Resolution

Cumulative update information

Cumulative update package 1 for SQL Server 2012 Service Pack 1

The fix for this issue was first released in Cumulative Update 1. For more information about how to obtain this cumulative update package for SQL Server 2012 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
2765331
(http://support.microsoft.com/kb/2765331/ )
Cumulative update package 1 for SQL Server 2012 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 2012 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:
2772858
(http://support.microsoft.com/kb/2772858/ )
The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released

SQL Server 2012

The fix for this issue was first released in Cumulative Update 3 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2723749
(http://support.microsoft.com/kb/2723749/LN/ )
Cumulative update package 3 for SQL Server 2012
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 2012 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:
2692828
(http://support.microsoft.com/kb/2692828/LN/ )
The SQL Server 2012 builds that were released after SQL Server 2012 was released
You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.

SQL Server 2008 R2 Service Pack 2

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 R2 Service Pack 2. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2720425
(http://support.microsoft.com/kb/2720425/ )
Cumulative Update package 1 for SQL Server 2008 R2 Service Pack 2
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:
2730301
(http://support.microsoft.com/kb/2730301/ )
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

SQL Server 2008 R2 SP1

The fix for this issue was first released in Cumulative Update package 7 for SQL Server 2008 R2 SP1. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2703282
(http://support.microsoft.com/kb/2703282/ )
Cumulative update package 7 for SQL Server 2008 R2 SP1
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 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:
2567616
(http://support.microsoft.com/kb/2567616/ )
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released
Back to the top | Give Feedback

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

Properties

Article ID: 2708027 - Last Review: November 20, 2012 - Revision: 7.0
Applies to
  • Microsoft SQL Server 2008 R2 Reporting Services
Keywords: 
kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2708027
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top