This event can be ignored if it occurred when Windows was started in Active Directory Restore mode or some other form of Safe Mode.
This problem can occur after a windows sockets program installs the "Windows Socket 2.0 Non-IFS Service Provider Support Environment" component and prevents the local LDAP server from starting. See ME315182
for information on how to solve this problem.
If the Intersite Messaging Service is installed after promotion on the only DC in the domain, it will fail to run after a restart, and this event will be logged. See ME266657
for details on this situation.
for a hotfix applicable to Microsoft Windows Server 2003. Also, check ME305837
for information about this event.
If you install an application on a Domain Controller (DC) that binds to port 389 with a listener, multiple failures are seen on the DCs. These include failures running dcpromo, startup failures with Inter-Site Messaging service, as well as NTFRS preventing a machine from becoming a DC.
This can usually be detected by using Ldp.exe from the Support Tools to confirm that you are succeeding in connecting to the Active Directory on each DC.
This problem occurs because the NT Directory Service Agent (NTDSA) fails to maintain exclusive control of port 389. Therefore, any other application that attempts to setup a listener on port 389 succeeds and gains control of the port from the NTDSA.
To resolve this problem, install Windows 2000 Service Pack 2.