Microsoft KB Archive/292527

= XADM: Access Violation in the Active Directory Connector Service (Adc.exe) =

Article ID: 292527

Article Last Modified on 2/28/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q292527



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 Description of the Microsoft Windows Registry



SYMPTOMS
When you attempt to start the Active Directory Connector service, it does not start and the following error is logged in the Application log:

Event Type: Error

Event Source: MSADC

Event Category: Replication

Event ID: 8145

Date: 3/9/2001

Time: 3:08:12 PM

User: N/A

Computer: RDORAN8

Description:

Exception c0000005 was raised at address 00407C6E.

For more information, click http://search.support.microsoft.com/search/?adv=1



CAUSE
This behavior occurs because the HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\ClientProtocols registry key is missing or the account under which the Active Directory Connector service starts does not have read permissions on the registry key.



WORKAROUND
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.

To work around this behavior, use the appropriate method.

Required Key Is Not Present
Create a registry file with the following information to rebuild the missing key:   Copy and paste the following text into Notepad:   Windows Registry Editor Version 5.00    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientProtocols]       &quot;ncacn_np&quot;=&quot;rpcrt4.dll&quot; &quot;ncacn_ip_tcp&quot;=&quot;rpcrt4.dll&quot; &quot;ncadg_ip_udp&quot;=&quot;rpcrt4.dll&quot; &quot;ncacn_nb_tcp&quot;=&quot;rpcrt4.dll&quot; &quot;ncacn_http&quot;=&quot;rpcrt4.dll&quot;  In the Save As dialog box, in the Save as type drop-down box, click All Files, and use the .reg extension. After you create the file, place it on the server that is having the problem, and then import it into the registry by double-clicking it.

Permissions Are Incorrect
If the permissions are incorrectly set on this key, add the account under which the Active Directory Connector service starts and grant this account a minimum of read permissions.  To determine the account under which the Active Directory Connector service starts, open the services Microsoft Management Console (MMC), double-click the Active Directory Connector service, and then click the Log on tab.</li> After you determine the correct account to which to add permissions, start Registry Editor, and then navigate to the following key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\ClientProtocols

</li> Click the ClientProtocols key, click the security pulldown, and then display the permissions on the key. Now add the permissions to the appropriate account.</li>  By default, the following permissions should be set on the object: <pre class="fixed_text">  <DOMAIN>/Administrators          Full Control Authenticated Users             Read CREATOR OWNER                   None (Full control on subkeys only if you look in advanced permissions) Server Operators                Read SYSTEM                          Full Control </li></ol>

Keywords: kbprb KB292527

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.