FIX: The DateTime parameter is not displayed by using the regional setting format of a SharePoint website in SSRS 2012

Article translations Article translations
Article ID: 2764343
This issue applies to Microsoft SQL Server 2012 Reporting Services.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenario:
  • You configure an instance of Microsoft SQL Server 2012 Reporting Services (SSRS 2012) to run under the Microsoft SharePoint integrated mode.
  • You create a report that contains a DateTime parameter.
  • You deploy the report to a SharePoint website. When you select the DateTime parameter, the parameter is displayed by using the format of the regional setting of the SharePoint website.
  • The language setting of the SharePoint website and the regional setting of the website are different. For example, the language setting of the SharePoint website is English (United States) [en-US] and the regional setting of the website is English (United Kingdom) [en-GB].
  • You review this report in a browser.
In this scenario, the parameter is displayed by using the format of the language setting of the SharePoint website.

Resolution

Cumulative update information

Cumulative Update 3 for SQL Server 2012 SP1

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 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2812412 Cumulative update package 3 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 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:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released

Cumulative update 5 for SQL Server 2012

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 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2777772 Cumulative update 5 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. 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:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released

Status

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

Properties

Article ID: 2764343 - Last Review: March 18, 2013 - Revision: 2.0
Keywords: 
kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2764343

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com