This event can be recorded in several situations and the troubleshooting approach should be based on the actual error code and the error description recorded in the event.
Error code 0x54b
(The specified domain either does not exist or could not be contacted.) - indicates that Exchange looked for a domain controller and couldn't find any. Verify all the networking settings, check if the DNS can obtain the name of a domain controller. Most probably there is a problem with a basic network configuration.
Error code 0x862
("The specified component could not be found in the configuration information.") - Indicates that some information is missing from the Exchange configuration. It may as well be the result of a bug. You may try to restart the service and see if that fixes the problem.
* * *
The most common Win32 API function is DsGetDcName. See EV100055
for Microsoft's documentation.
We had the same error and in our case a faulty WINS entry caused the problem. After deleting the entry and restarting the Exchange 2003 server, everything was working fine.
I had a system with a malfunctioning network card. After disabling the NIC, stopping the IS resulted in dozens of these errors. I could only stop it by ending the store.exe process in Task Manager.
As per Microsoft: "This event may be seen if a call to the DsGetDcName function is made before the Exchange Management Service is fully initialized. If this is the case, you will also see events 2104 and 2102 (both having a source of MSExchangeDSAccess) preceding this event". See MSEX2K3DB
for more details.
As per ME322837
, after you apply Service Pack 2 (SP2) for Exchange 2000 Server, you may see this event logged in the Application event log each time that you restart the server. See ME322837
to find out when this event can be ignored.
Error 0x862 (hex) or 2146 (decimal) means as the message says: "The specified component could not be found in the configuration information." and Microsoft's explanation via "net helpmsg 2146" is:
"Windows NT could not find the required information in your configuration. ACTION: Ask your network administrator to check your configuration. The administrator should make sure your system configuration contains all information required to run Windows NT and any associated applications."
Obviously, this does not do the job if you are already the administrator. This event seems to occur after the installation of Exchange 2000 SP2 and usually the server does not function properly.
The "DsGetDCNameW" API is a function part of ADSI and as the name says it returns the name of the Domain Controller. A newsgroup posts says that "Stopping and restarting the SMTP service manually will allow SMTP to start without this error."
From another post: "I'm told by a tech at PSS (Microsoft Professional Support Services) that all three of these can be ignored. Apparently they'll be taken care of in the next Exchange SP."