XADM: Error 0xc00206b7 When You Start the Exchange Server System Attendant on a Windows 2000-based Server

Article ID: 267573 - View products that this article applies to.
This article was previously published under Q267573
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986
(http://support.microsoft.com/kb/256986/EN-US/ )
Description of the Microsoft Windows Registry
Expand all | Collapse all

SYMPTOMS

When you start the Exchange Server system attendant on a computer that runs Microsoft Windows 2000, you may receive one of the following error messages:
Source: MSExchangeSA
Event ID: 1028
Description: Unexpected error - There are no protocol sequences available. NT ID 0xc00206b7
-or-
Event Type:Error Event Source:MSExchangeSA Event Category:General Event ID:1005 Description: Unexpected error - There are no protocol sequences. Facility: Win32 ID no: c00706b7 Microsoft Exchange System Attendant occurred.
Exchange Sever Setup is also unable to start the system attendant, and the following event is written in the application Event Log:
Event ID: 1005 from the MSexchangeSA with the error code 0xc00206b7
The following event may also appear in the application Event log:
Source: MSExchangeSA
Category: General
Event ID: 1005
Description:
Unexpected error. There are no protocol sequences. Facility: Win32 ID no: c00706b7 Microsoft Exchange System Attendant occurred.
For more information, click http://search.support.microsoft.com/search/?adv=1.
Back to the top | Give Feedback

CAUSE

The HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\ClientProtocols registry key is absent. It is likely that the removal of a previous software application removed this key by mistake.
Back to the top | Give Feedback

RESOLUTION

Replace the key in the registry and it enables the system attendant to start.

NOTE: Import this registry key from a Microsoft Windows 2000-based server that has the same protocols installed on it. You can manually rebuild the ClientProtocols folder and add all the protocol values, but it is recommended that you import this key from a Windows 2000-based server running with the same protocols.
Back to the top | Give Feedback

MORE INFORMATION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

You can manually add the needed registry key and values. To do this, perform the following steps:
  1. Open regedit.
  2. Browse to the HKLM\SOFTWARE\Microsoft\Rpc key.
  3. Under RPC, If there is not a subkey named ClientProtocols, add one. Under the subkey named ClientProtocols, if any of the following values and data strings are missing, add them.
    Value 0
  Name:            ncacn_http
  Type:            REG_SZ
  Data:            rpcrt4.dll
 
Value 1
  Name:            ncacn_ip_tcp
  Type:            REG_SZ
  Data:            rpcrt4.dll
 
Value 2
  Name:            ncacn_nb_tcp
  Type:            REG_SZ
  Data:            rpcrt4.dll
 
Value 3
  Name:            ncacn_np
  Type:            REG_SZ
  Data:            rpcrt4.dll
 
Value 4
  Name:            ncadg_ip_udp
  Type:            REG_SZ
  Data:            rpcrt4.dll
  4. Close regedit.
Now you can start Exchange 2000 successfully.
Back to the top | Give Feedback

Properties

Article ID: 267573 - Last Review: February 20, 2007 - Revision: 4.2
APPLIES TO
  • Microsoft Exchange Server 5.5 Standard Edition
  • Microsoft Exchange 2000 Server Standard Edition
  • Microsoft Small Business Server 2000 Standard Edition
Keywords: 
kbprb KB267573
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top