Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

MSExchangeAL/MSExchangDSAccess Errors in Application Log (2103, 8026, 8250)

Posted on 2006-07-16
3
Medium Priority
?
2,093 Views
Last Modified: 2008-03-17
I'm getting the following three events in my Application log.  I'm not sure if they're directly related, but they seem to happen at the same time.  The OS was installed about 2 months ago, but these errors just started happening within the last 2 weeks.

Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      Service Control
Event ID:      8250
Date:            7/16/2006
Time:            3:00:37 AM
User:            N/A
Computer:      [Server Name]
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.


Event Type:      Error
Event Source:      MSExchangeAL
Event Category:      LDAP Operations
Event ID:      8026
Date:            7/16/2006
Time:            3:00:37 AM
User:            N/A
Computer:      [Server Name]
Description:
LDAP Bind was unsuccessful on directory theserver.millsentertainment.office for distinguished name ''. Directory returned error:[0x51] Server Down.


Event Type:      Error
Event Source:      MSExchangeDSAccess
Event Category:      Topology
Event ID:      2103
Date:            7/16/2006
Time:            3:00:34 AM
User:            N/A
Computer:      THESERVER
Description:
Process MAD.EXE (PID=2876). All Global Catalog Servers in use are not responding:
[server name].[domain].office
0
Comment
Question by:rtedi222
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 74

Accepted Solution

by:
Jeffrey Kane - TechSoEasy earned 2000 total points
ID: 17127199
Those errors are normal when you reboot your server.  Since they are happening around 3:00am, then I suspect they are after an automatic update has required a server reboot.

Jeff
TechSoEasy
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The problem of the system drive in SBS 2003 getting full continues to be an issue, even though SBS 2008 and SBS 2011 are both in the market place.  There are several solutions to this, including adding additional drive space or using third party uti…
Because virtualization becomes more and more common, and, with Microsoft Hyper-V included in Windows Server at no additional costs, and, most server hardware nowadays is more than capable of running a physical Small Business Server (SBS) 2008 or 201…
In response to a need for security and privacy, and to continue fostering an environment members can turn to for support, solutions, and education, Experts Exchange has created anonymous question capabilities. This new feature is available to our Pr…
We’ve all felt that sense of false security before—locking down external access to a database or component and feeling like we’ve done all we need to do to secure company data. But that feeling is fleeting. Attacks these days can happen in many w…

715 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question