[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

When a DC goes down, Exchange 2007 failed to respond for some time

Posted on 2009-05-03
6
Medium Priority
?
926 Views
Last Modified: 2012-05-06
All servers are running Windows 2008.  During a test we shuted down a DC, not the PDC.  Both DC ar GC.  For a reason or another one Exchange server was having problems with the system attendant, so the mailboxes were unavailable.  

I used "Modify configuration domain controller" to choose a DC.  The everything came back.  But as far as I know Exchange shouldn't have any trouble to run when a DC goes down, no matter which DC is down.  

Here is what I found in the event viewer
Microsoft Exchange System Attendant failed to read the membership of the universal security group '/dc=ca/dc=ourdomain/ou=Microsoft Exchange Security Groups/cn=Exchange Servers'; the error code was '8007203a'. The problem might be that the Microsoft Exchange System Attendant does not have permission to read the membership of the group.

If this computer is not a member of the group '/dc=ca/dc=ourdomain/ou=Microsoft Exchange Security Groups/cn=Exchange Servers', you should manually stop all Microsoft Exchange services, run the task 'add-ExchangeServerGroupMember,' and then restart all Microsoft Exchange services.

Could not read the Security Descriptor from the Exchange Server object with guid=D922679FE5725A4BBA65373361CF9BF1. As a result the Proxy Address Calculation RPC interface will not be available on the local Exchange Server.  

Error initializing session for virtual machine S2008MB001. The error number is 0x80040111. Make sure Microsoft Exchange Store is running. Also, make sure that there is a valid public folder database on the Exchange server.
0
Comment
Question by:quadrumane
  • 3
  • 3
6 Comments
 
LVL 58

Expert Comment

by:tigermatt
ID: 24293422

It is perfectly normal for Exchange to take somewhere in the region of 30 minutes to an hour to locate a new DC/GC to use when the one it is using is taken offline. Had you left it this long, it would have resolved the issue itself.

Bear in mind that as a best practice you should make all DCs Global Catalogs (GCs). Exchange communicates with Global Catalogs, so making all DCs GCs reduces confusion and will also ensure that if a DC is running, Exchange can communicate with it.

You must also verify that the Exchange Server is using more than one server for DNS. If it only has one DC configured as its DNS server, you need to install DNS on another DC and add that DC as an alternate DNS server. If the configured DNS Server goes down, Exchange will not be able to locate any resource records to find another DC, and will be in trouble.

-Matt
0
 

Author Comment

by:quadrumane
ID: 24296077
Both DCs are GCs so all DCs are GCs.   Eventhough, you say it's perfectly normal that it takes up to an hour to locate a new DC/GC.  I'M surprised.  I thought it was faster.  

The DNS configuration is already as you said, I try to follow the best practices.

Thanks

0
 
LVL 58

Expert Comment

by:tigermatt
ID: 24296101

If DNS has both DCs configured as DNS Servers on Exchange, then what you are seeing is normal.
If you wanted to force Exchange to detect a new DC quicker, you'd need to restart the Exchange services. Exchange won't do the detection automatically for up to an hour, as I stated previously.

-Matt
0
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

 

Author Comment

by:quadrumane
ID: 24683842
I had to restart the Exchange topology service, which is restarting all other services.  Afterward, the System attendant and the information store can be restarted.  

It doesn't restart automatically after one hour.  It it fails to start, it won't start alone.

As far as I know to avoid this problem, you have to stop the services before rebooting the Exchange server.
0
 
LVL 58

Expert Comment

by:tigermatt
ID: 24690660

Exchange will detect a DC automatically after a period of time; a restart of the services is not required. If it were, it would be a major inconvenience for large Exchange topologies.

-Matt
0
 

Accepted Solution

by:
quadrumane earned 0 total points
ID: 25449389
Exchange is not detecting a DC after a period of time, or it can take too long.
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

Question has a verified solution.

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

Want to know how to use Exchange Server Eseutil command? Go through this article as it gives you the know-how.
Stellar Exchange Toolkit: this 5 in 1 toolkit comes loaded with mega-software tool. Here’s an introduction to tools’ usage and advantages:
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…
Suggested Courses
Course of the Month19 days, 17 hours left to enroll

873 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