Events 2104, 2102, and 8250 are logged after you apply Exchange 2000 Server Service Pack 2 or Service Pack 3 (322837)

SYMPTOMS

After you apply Service Pack 2 (SP2) or Service Pack 3 (SP3) for Microsoft Exchange 2000 Server, you may see the following events logged in the application event log each time that you restart the server:

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2102
Description:
Process MAD.EXE (PID=1484). All Domain Controller Servers in use are not responding: computer.domain.com

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2104
Description:
Process MAD.EXE (PID=1484). All the DS Servers in domain are not responding.

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Description:
The Win32 API call 'DsGetDCNameW' returned error code [0x862] The specified component could not be found in the configuration information. The service could not be initialized. Make sure that the operating system was installed properly.

MORE INFORMATION

You can safely ignore the three events that appear together, as described in the "Symptoms" section of this article.

The events are logged when a call to DsGetDcName is made before the Microsoft Exchange Management Service is fully initialized. DsGetDcName is a Windows Application Programming Interface (API) function that returns the name of the domain controller.

Microsoft Exchange Management Service is automatically installed when you install Microsoft Exchange 2000 Server Service Pack 2 (SP2).

For additional information about the DsGetDcName function, visit the following Microsoft Web site:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ad/ad/dsgetdcname.asp