Solved

Unable to get Healthy state for some passive copies

Posted on 2014-04-02
3
212 Views
Last Modified: 2014-04-21
Hello,

We use Exchange Server 2013 Enterprise on Windows Server 2012 R2 Standard. We installated SP1 directly after installation without installing CU1 and CU2.

According to documentation with SP1 for Exchange Server 2013, the maximum amoumt of Active Databases per server or per DAG is 100 after installing SP1. Before CU2 this was 50.

We have 96 databases configured on 8 servers (MB / CAS) in a DAG. Each database has two passive copies. 132 copies of this passive databases are in a healthy state, and the other 60 have the status FailedAndSuspended. When I try to resume these I get a message that the number of supported databases is reached (see attachement). According to an article on technet this can occur when a value msExchMaxStoresTotal is not updated properly in the configuration container of AD. This proved to be the case of some of our servers. I have changed the value from 50 to 100 using ADSI-Edit, waited for replication and then rebooted the server.

Still the databases that were FailedAndSuspended refused to resume. The same error is given.

Technet: http://blogs.technet.com/b/timmcmic/archive/2013/11/08/exchange-2013-cumulative-update-2-where-are-my-databases.aspx
Microsoft: http://support.microsoft.com/kb/2897047/en-us

I also tried the "solution" given in the technet articel. Re-enter the product key of Exchange and restarting the MSExchangeIS service didn't resolve anything.

Anybody an idea?

Best regards

Sidney
error.png
0
Comment
Question by:mailbeheer
  • 2
3 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39972121
To be clear here - you installed Exchange 2013 RTM on to Windows 2012 R2, then updated to SP1?

If so, you are still in an unsupported build.
You should have used SP1 media to install the servers, as that is the first version that is supported on Windows 2012 R2. I am already aware of two instances where Microsoft support have said it wasn't supported and told the client to build a new server, migrate and remove the old one.

Simon.
0
 

Accepted Solution

by:
mailbeheer earned 0 total points
ID: 40005892
Yes that was the situation. After trying different options it seems that an initial setting when i configured the databases was holding the limit of 50 that was in place when i installed the RTM version of Exchange 2013. When i removed all database that were created in RTM and recreated the databases in my SP1 environment the problem seemed to disappear.

After your remark about the unsupported situation i deceided to completly reinstall our exchange environment. This to prevent any support issues if we ever need Microsoft Support, Thanks for that.

Sidney
0
 

Author Closing Comment

by:mailbeheer
ID: 40012206
I provided to solution to the problem myself
0

Featured Post

Too many email signature updates to deal with?

Do you feel like you are taking up all of your time constantly visiting users’ desks to make changes to email signatures? Wish you could manage all signatures from one central location, easily design them and deploy them quickly to users? Well, there is an easy way!

Join & Write a Comment

Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
Check out this infographic on what you need to make a good email signature that will work perfectly for your organization.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This video discusses moving either the default database or any database to a new volume.

762 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

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now