FIX: SQL Server Configuration Manager takes a long time to open if many SQL Server 2008 R2 or SQL Server 2012 instances are installed

Microsoft distributes Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2012 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 or Microsoft SQL Server 2012 fix release.

Consider the following scenario:

• You have installed many instances of the following on a computer:
  • Microsoft SQL Server 2008 R2
  • Microsoft SQL Server 2008 R2 Reporting Services (SSRS 2008 R2)
  • Microsoft SQL Server 2008 R2 Analysis Services (SSAS 2008 R2)
  • Microsoft SQL Server 2008 R2 Integration Services (SSIS 2008 R2)
  • Microsoft SQL Server 2012
• You try to open SQL Server Configuration Manager on the computer.

In this scenario, SQL Server Configuration Manager takes a long time to open.

Note This issue also occurs in Microsoft SQL Server 2008 or in Microsoft SQL Server 2012.

This issue occurs because the service enumeration module (Svrenumapi100.dll) collects too much unnecessary information.

Cumulative update information

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 6 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: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:

SQL Server 2012

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 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 2012 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: You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.

Cumulative update package 12 for SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 12. 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: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:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.