Event Id | 8250 |
Source | MSExchangeAL |
Description | The Win32 API call <name> returned error code [0x<error code>] <error message>. The service could not be initialized. Make sure that the operating system was installed properly. |
Event Information | According to Microsoft: 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. Refer below given Microsoft article for more information about this event. Following newsgroup information may help: "Problem: Local users are unable to logon from win95/98 system. Suggestion: At my work place, we had the same problem. If you run DHCP, I know that you can assign static IPs and that will solve the login issue. If youre not running DHCP right now, theres a patch for win9x machines that, Microsoft says, will fix it." --------------------------------- "Check if you have enabled DHCP registration in DNS is set. For legacy clients this should enabled in DHCP server" |
Reference Links | Events
2104, 2102, and 8250 are logged after you apply Exchange 2000 Server Service
Pack 2 or Service Pack 3 Problems logging on to a Windows 2000-based server or a Windows 2003-based server |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.