Go Premium for a chance to win a PS4. Enter to Win

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

Troubleshooting Event 2080 from Exchange 2010 topology

Hello All,
I am encountering a problem which causes lockups on our network. When there is a problem with a server (bla1) it causes our local network including (bla2) (also our exchange server) to lock up network drives and lock mail. After about 5 minutes it goes back to normal. No errors are logged on (bla1) only on (bla2) see below. I belive its due to the "reachablity" flag but im not sure how to fix it. Please Help!!!

Process STORE.EXE (PID=1844). 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:
bla1.bla.com      CDG 1 7 7 1 0 1 1 7 1
bla2.bla.com      CDG 1 0 0 1 0 0 0 0 0
 Out-of-site:
bla3.bla.com      CDG 1 7 7 1 0 1 1 7 1
0
portillosjohn
Asked:
portillosjohn
2 Solutions
 
Vijaya Babu SekarAssociate Ops ManagerCommented:
It should be problem with Active directory topology service error. it intermittent issue with communication between Exchange and AD

so please the below article. it should be helpful for understanding and isolate the issue.


http://howdouc.blogspot.com/2011/01/exchange-active-directory-topology.html

Thanks
0
 
portillosjohnAuthor Commented:
Great article but how do I start troubleshooting this? I run dcdiag with no errors. One quick note is that exchange is installed on bla2.bla.com if that makes a difference. I inhertited this problem.
0
 
Simon Butler (Sembee)ConsultantCommented:
If Exchange is installed on a domain controller, then that server must also be a global catalog. Exchange will also only use itself for DC functionality.

I would start planning to move Exchange off the DC (you cannot run DCPROMO on the machine with Exchange installed).

You could run the EXBPA from the toolbox and ensure that doesn't flag anything else up.

Simon.
0
Technology Partners: 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!

 
portillosjohnAuthor Commented:
The link I need is broken......

This is taken from the page that sandeshdubey posted.

Since you are getting event id 2080.This is commonly caused by the SACL right not being applied on the new Domain Controller. In the event id check the first Domain Controller the fifth number is a one and shows that the SACL right is correctly applied. Next to the new domain controller the field is a zero and the SACL is the cause.
 
dc1.domain              CDG 7 7 1 0 1 1 7 1
newDC01.domain      CDG 7 7 1 0 0 1 7 1....this is the cause.


 broken link......................................................
Refer below link to fix the same.
 http://benosullivan.co.uk/windows/server-2003/event-id2080-exchange-will-not-run-with-second-domain-controller/
............................................
 
However for better assistance related to exchange you can refer exchange2010 forum.
 http://social.technet.microsoft.com/Forums/en-us/category/exchange2010
 
Hope this helps
0
 
portillosjohnAuthor Commented:
I ended up enabling ipv6 and it worked.
0
 
portillosjohnAuthor Commented:
This was the actual result of investigating the link provided.
0

Featured Post

Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

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