Microsoft distributes Microsoft SQL Server 2008 R2 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 fix release.
You encounter either of the following two issues when you use Master Data Services (MDS) on a computer that is running SQL Server 2008 R2.
Issue 1Consider the following scenario:
- You install and configure an English edition of SQL Server 2008 R2 MDS on a computer.
- You create a numeric attribute in MDS.
- You use Windows Internet Explorer to browse to the MDS website.
- Internet Explorer is set to a language that uses a comma (,) character as the decimal separator instead of a period (.) character as the separator. For example, you specify Icelandic as the language to use in Internet Explorer. The Icelandic language uses the comma to indicate the decimal place.
- In Internet Explorer, you type a decimal value that uses the comma as the decimal separator for the attribute. For example, you type 1,2345.
Issue 2You install and configure an English edition of SQL Server 2008 R2 MDS on a computer. You set the language that Internet Explorer uses to Norwegian, Finnish, or Swedish. When you try to open the entity explorer on the MDS website, an unhandled exception occurs, and you receive the following error message:
Cumulative update information
SQL Server 2008 R2The 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 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2345451 Cumulative Update package 4 for SQL Server 2008 R2Note 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:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.