Exchange 2010 on SBS 2011 - Event Id 2102 MSExchange ADAccess

Hi Everyone,

Exchange 2010 services will not start on our SBS2011 server. A tech was in late last night on the server to add a 2nd DNS server and setup replication from it and the SBS server and everything has gone to crap since the changes were made.

I have removed it from DNS and removed all the NS entries from both forward and reverse look-up items within DNS and disabled the replication for all of them also but issues remain. Here are the Application Log entries we see each time we try to start the services:

1) Error ID 2102 MSExchange ADAccess: Process STORE.EXE (PID=5980). All Domain Controller Servers in use are not responding: SBSserver.domain.local

2) Info ID 2080 MSExchange ADAccess: Process STORE.EXE (PID=5980). Exchange Active Directory Provider has discovered the following servers with the following characteristics:
 (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
In-site:
SBSserver.domain.local      CDG 1 0 0 1 0 0 0 0 0
 Out-of-site:

3) Error ID 2114 MSExchange ADAccess: Process STORE.EXE (PID=5980). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.

4) Error ID 2155 MSExchangeRepl: The Third Party Replication Manager could not access Active Directory. Error: The Microsoft Exchange Active Directory Topology service on server localhost did not return any suitable domain controllers.. Initialization will be retried automatically.

5) Info ID 2080 MSExchange ADAccess: Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=2112). Exchange Active Directory Provider has discovered the following servers with the following characteristics:
 (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
In-site:
SBSserver.domain.local      CDG 1 0 0 1 0 0 0 0 0
 Out-of-site:

6) Error ID 2114 MSExchange ADAccess: Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=2112). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.

7) Error ID 2102 MSExchange ADAccess: Process MAD.EXE (PID=2484). All Domain Controller Servers in use are not responding:
SBSserver.domain.local

I have run SBS BPA and it found no errors only warning about share point which we do not use on this server.

I am at a loss - downloading Exchange BPA now to try it to see if I get any further errors - any help you can provide would be appreciated.

thanks,

TheSonicOne
TheSonicGodAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Alan HardistyCo-OwnerCommented:
What is the NIC on the SBS server configured to point to for DNS?

It should ONLY be pointing to itself (not 127.0.0.1.

Alan
0
TheSonicGodAuthor Commented:
Yes - points to 192.168.1.15 (IP of itself)
0
Alan HardistyCo-OwnerCommented:
Okay - have you run the fix my network wizard?  If not, please run it.

May also be good to give the server a reboot.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
TheSonicGodAuthor Commented:
Thanks Alan,

Ran Fix My Network wizard too a while but found that IPv6 was disabled but not correctly.

Added the registry entry as per MS article: http://blogs.technet.com/b/sbs/archive/2008/10/24/issues-after-disabling-ipv6-on-your-nic-on-sbs-2008.aspx

and then rebooted to apply the changes.

Server came right back up (Versus 1.5+ hours from earlier) and exchange started automatically with no errors.

Tested all email now but looks to have fixed it.

Thanks Alan,

Spencer
0
Alan HardistyCo-OwnerCommented:
Excellent - well done.

Glad all is now working happily and thanks for the points.

Alan
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.