Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1017
  • Last Modified:

Event ID 2101

In my exchange 2000 server I noticed an error message as below:
Process MAD.EXE (PID=1560). All Domain Controller Servers in use are not responding.
This is a Topology category error.
Can anyone suggest what caused the error and how to fix it?

Thanks!
0
exchangesmith
Asked:
exchangesmith
1 Solution
 
jpmartenCommented:
What is the event ID?  Run a dcdiag /v on the computer that is giving the errors, if it is not a dc, then run netdiag /v.
0
 
jpmartenCommented:
Ok sorry bout that, I saw the ID after I posted that.  Not much on that specific event 2101.  The source is MSExchangeDSAcess correct?  Turn up diagnostics loggin to maximum on DSAccess and also go to MSExchangeSA and turn up NSPI Proxy and RFR Interface to maximum, you do not have to restart any services.  Let that run and see if you get any errors.

How many DC's GC's do you have and is the Exchange server a DC or GC?
0
 
exchangesmithAuthor Commented:
Event ID is 2102, it is a DC but can't run either dcdiag /v nor netdiag /v
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
jpmartenCommented:
Event ID is 2102 or 2101?????  Do you get a event ID 9154 also?
0
 
exchangesmithAuthor Commented:
It is the only DC in the domain.
Please advise how to turn up diagnostics to maximun on DSAccess...
0
 
exchangesmithAuthor Commented:
event ID 2102, no 9154...
0
 
jpmartenCommented:
Hold off on the logging for now.  IF this is the only DC in the Domain then it must be the Global Catalog server also.  Save out your application and system log files and send them to me to review at a-jmart@microsoft.com
0
 
jpmartenCommented:
Hold off on the logging for now.  IF this is the only DC in the Domain then it must be the Global Catalog server also.  Save out your application and system log files and send them to me to review at a-jmart@microsoft.com
0
 
jpmartenCommented:
Hold off on the logging for now.  IF this is the only DC in the Domain then it must be the Global Catalog server also.  Save out your application and system log files and send them to me to review at a-jmart@microsoft.com
0
 
kevalaCommented:
A-JMART!! DANG man! I didn't know you were on here too! LOL -

What do you think about the hotfix in Q318067?
Also, let's check DNS -
Is the DC/GC hosting internal A.D. integrated DNS?
If so, does the Exchange server point to itself first for DNS with forwarders setup to external ISP?

We might have to look into creating a topology creation timeout key per Q312859 -

Later,
a-kevcar

0
 
matth3whCommented:
What happens if this error occurs on SBS2011 / Exchange 2010?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now