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.
Symptoms
Consider the following scenario:
-
You install and configure Microsoft SQL Server 2008 R2 Master Data Services (MDS) on a computer.
-
You create an MDS website.
-
You log on to the website by using Internet Explorer.
-
You try to add an attribute filter in the Filter Criteria control on an Attribute.aspx page.
In this scenario, you may encounter the following errors:
-
A JavaScript warning icon appears in Internet Explorer status bar.
Note The JavaScript warning icon is a yellow triangle with an exclamation point. -
A JavaScript error message that resembles the following is displayed in a dialog box:
{
Error on this webpage might cause it to work incorrectly.
Message: Sys.ScriptLoadFailedException: The script '/MDM/ScriptResource.axd?d=<long_random_string>' contains multiple calls to Sys.Application.notifyScriptLoaded(). Only one is allowed.
Line: 5
Char: 25340
Code: 0
}
Note The <long_random_string> placeholder represents the instance when the website is loaded. -
Internet Explorer may stop responding after the JavaScript error is encountered.
Cause
This issue occurs because of an error in the JavaScript source code for the NumericUpDownButton Tabstrip control on the Attribute.aspx page.
Note The JavaScript source code for the control is included in the ScriptResource.axd file.
When the notifyScriptLoaded method is called multiple times, the method generates an error. However, the source code for the NumericUpDownButton Tabstrip control contains redundant calls to the notifyScriptLoaded method.
For more information about the Sys.Application.notifyScriptLoaded method, visit the following MSDN website:
General information about the Sys.Application.notifyScriptLoaded method
Resolution
Cumulative update information
SQL Server 2008 R2 Service Pack 1
The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2544793 Cumulative Update package 1 for SQL Server 2008 R2 Service Pack 1Note 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:
2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released
SQL Server 2008 R2
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 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2507770 Cumulative Update package 5 for SQL Server 2008 R2 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 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
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499New naming schema for Microsoft SQL Server software update packagesFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
