Microsoft KB Archive/938823

= FIX: Dates in the Datetimepicker control appear in the incorrect format when you view a report of SQL Server 2005 Reporting Services with SP2 on a server that is set to a German locale =

Article ID: 938823

Article Last Modified on 10/23/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Reporting Services, when used with:
 * Microsoft SQL Server 2005 Service Pack 2

-



Bug: #50001284 (SQL Hotfix)



Microsoft distributes Microsoft SQL Server 2005 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 2005 fix release.



SYMPTOMS
Consider the following scenario.
 * You create a report of Microsoft SQL Server 2005 Reporting Services with Service Pack 2 (SP2). The report contains a report parameter whose data type is DateTime.
 * You deploy the report to a report server.
 * On the server that runs the report server, you select German locale under Standards and formats in the Regional and Language Options item in Control Panel.
 * In the Internet Options item in Control Panel, you specify German to be the language that Internet Explorer uses to display content in Web pages.
 * You open the report from the URL of the virtual directory of the report server.
 * In the report, you select a date by using the Datetimepicker control.

In this scenario, the date appears in the mm/dd/yyyy format in the Datetimepicker control. However, you expect that the date appears in the dd.mm.yyyy format.

Note By default, the mm/dd/yyyy format is used for the English (United States) locale. The dd.mm.yyyy format is used for the German locale.

This problem does not occur in the versions of SQL Server 2005 Reporting Services that are earlier than SQL Server 2005 Reporting Services SP2.



RESOLUTION
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 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

941450 Cumulative update package 4 for SQL Server 2005 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 2005 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:

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released

Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

941450 Cumulative update package 4 for SQL Server 2005 Service Pack 2

