Microsoft distributes Microsoft SQL Server 2012 fixes in one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2012 update release.
This issue applies to the following product:
Microsoft SQL Server Integration Services 2012
Consider the following scenario:
You have Microsoft SQL Server Integration Services (SSIS) 2012 installed on a computer. The display language of the operating system differs from the setting in the Region and Language dialog box. For example, the display language is "English (United States)," while the Region and Language locale is "English (United Kingdom)."
You run an SSIS package that has a DateTime variable which has to be filled in at execution time.
You input a DateTime value.
In this scenario, the DateTime value is parsed incorrectly. For example, when you input an "English (United Kingdom)" format value (dd/MM/yyyy), the value will be incorrectly parsed to an "English (United States)" format value (MM/dd/yyyy).
This issue occurs because the variable value is parsed by using the display language format.
Cumulative update information
Cumulative update package 5 for SQL Server 2012 Service Pack 1 (SP1)
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:
2861107 Cumulative update package 5 for SQL Server 2012Note 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 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.