Article ID: 2715841 - View products that this article applies to.
This issue applies to Microsoft SQL Server 2012 Reporting Services.
Consider the following scenario:
This issue occurs because of a change in the .NET Framework 4.0 that prevents the application and SSRS 2012 from using the correct information based on the regional settings of the operating system. Applications that are based on the .NET Framework 4.0 use regional settings that are returned by Windows. However, SSRS 2012 is built on the .NET Framework 3.5 Services Pack 1 (SP1). Therefore, SSRS 2012 uses the regional settings that are embedded in the .NET Framework 3.5 SP1.
When a SSRS 2012 server runs a report by using the "." symbol as a time separator, the DateTime type parameter is sent back to the client as a string. The Report Viewer control calls the DateTimeOffset.TryParse method to validate the string by using the ":" symbol as the time separator. Therefore, the string is validated as false and it is not displayed in the parameter prompt area.
Note This issue only occurs if the Long Time format is set to "HH:mm:ss", the default setting for Italian regional settings. The default setting for Italian regional settings depends on your operating system. Additionally, you can configure the default setting of your operating system by changing the Long Time format.
Cumulative update information
Cumulative update 2 for SQL Server 2012 Service Pack 1 (SP1)The fix for this issue was first released in Cumulative Update 2. 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:
2790947Note 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 Service Pack 1 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:
(http://support.microsoft.com/kb/2790947/ )Cumulative update package 2 for SQL Server 2012 Service Pack 1
(http://support.microsoft.com/kb/2772858/ )The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To work around the issue, use one of the following workarounds:
Microsoft Report Viewer 2010 SP1 Redistributable Package is available to download from the following Microsoft Download Center website:
Microsoft Report Viewer 2010 SP1 Redistributable PackageTo know more about DateTimeOffset.TryParseExact method and DateTimeOffset.TryParse Method, visit the following MSDN websites:
DateTimeOffset.TryParseExact Method (String, String, IFormatProvider, DateTimeStyles, DateTimeOffset%)
DateTimeOffset.TryParse Method (String, DateTimeOffset%)
Article ID: 2715841 - Last Review: January 24, 2013 - Revision: 1.0