Visual Studio .NET Server Explorer takes a long time to show the data (308457)


The information in this article applies to:

  • Microsoft Visual Studio .NET (2002), Professional Edition, when used with:
    • the operating system: Microsoft Windows 98
    • the operating system: Microsoft Windows NT 4.0
  • Microsoft Visual Studio .NET (2003), Professional Edition
This article was previously published under Q308457

SYMPTOMS

When you are running Microsoft Visual Studio .NET on a Microsoft Windows NT 4.0-based system and are using Server Explorer to explore a Windows 95,Windows 98, or Windows Millennium Edition-based system, most management data and management events operations for that system take a very long time to complete. These operations include expanding the nodes, adding classes to the Management Data node, and adding event queries to the Management Events node.

A similar problem may occur in other management applications that utilize Windows Management Instrumentation (WMI) when the applications are connecting from Windows NT 4.0 to Windows 95/Windows 98/Windows Millennium Edition-based systems and establishing connections to multiple WMI namespaces at once.

CAUSE

A problem in Distributed COM (DCOM) substantially increases the time it takes for an application to connect to a WMI namespace when connecting from a Windows NT 4.0 system to a Windows 95/Windows 98/Windows Millennium Edition-based system.

RESOLUTION

For Windows NT 4.0 systems that are running Visual Studio .NET, you can work around this problem by using the following steps:
  1. Start the DCOM Configuration Utility (Dcomcnfg.exe).
  2. Click the Default Protocols tab.
  3. Move "Connection-oriented TCP/IP" to the top of the DCOM Protocols stack.
  4. Click OK.

STATUS

The problem has been fixed in Windows 2000 and later versions of Microsoft Windows.
Modification Type:MinorLast Reviewed:3/7/2006
Keywords:kbvs2005doesnotapply kbvs2005swept kbtshoot kbprb KB308457 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.