FIX: "Index was outside the bounds of the array" SMO error message when you connect to a SQL Server code-named 'Denali' CTP1 Database Engine instance in SSMS 2008 R2 and in SSMS 2008

Article ID: 2459027 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 R2 and Microsoft SQL Server 2008 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 and Microsoft SQL Server 2008 fix release.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You install a Database Engine instance of Microsoft SQL Server code-named 'Denali' Community Technology Preview 1 (CTP1) on a computer.
  • You register the Database Engine instance by using SQL Server 2008 R2 Management Studio (SSMS 2008 R2) on the same computer or on another computer.
  • You double-click the instance in the Registered Servers pane to connect the instance, and then the connection is established successfully.
In this scenario, you receive the following SQL Server Management Objects (SMO) error message:
Index was outside the bounds of the array. (Microsoft.SqlServer.Smo)
Back to the top | Give Feedback

CAUSE

This issue occurs because of an error in SSMS 2008 R2.
Back to the top | Give Feedback

RESOLUTION

NoteTo resolve this issue, apply Cumulative Update 5 for SQL Server 2008 R2 on the computer that has SSMS 2008 R2 installed.

Cumulative update information

SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 3 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2498535
(http://support.microsoft.com/kb/2498535/LN/ )
Cumulative update package 3 for SQL Server 2008 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 2008 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:
2402659
(http://support.microsoft.com/kb/2402659/LN/ )
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 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.

SQL Server 2008 Service Pack 1

The fix for this issue was first released in Cumulative Update 12 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2467236
(http://support.microsoft.com/kb/2467236/LN/ )
Cumulative update package 12 for SQL Server 2008 Service Pack 1
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 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:
970365
(http://support.microsoft.com/kb/970365/LN/ )
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Cumulative Update 5 for 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:
2438347
(http://support.microsoft.com/kb/2438347/ )
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
(http://support.microsoft.com/kb/981356/ )
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

MORE INFORMATION

To download Microsoft SQL Server code-named 'Denali' Community Technology Preview 1 (CTP1), visit the following Microsoft Download Center website:
Download information for Microsoft SQL Server code-named 'Denali' Community Technology Preview 1 (CTP1)
(http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6a04f16f-f6be-4f92-9c92-f7e5677d91f9&displaylang=en)

Back to the top | Give Feedback

Properties

Article ID: 2459027 - Last Review: March 21, 2011 - Revision: 4.0
APPLIES TO
  • Microsoft SQL Server 2008 R2 Datacenter
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Standard
Keywords: 
kbqfe kbexpertiseadvanced kbsurveynew kbfix KB2459027
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top