Exchange 2010 Std: Mailbox server has reached the maximum database limit of 5 Error RcrExceedDbLimitException

Follow me So far in 2 part series of this article we worked on how one member of a Database availability group (DAG) cluster of Exchange 2010 server got broken and the cluster service got stopped and then in Part 2, how to add database copies back on a freshly added DAG member. Please refer to following links to article if you would like to understand that in detail. Part 1 : Removing a mailbox server from DAG and Windows Cluster and re-adding it Part 2: Reseeding a database copy after re-adding a new member to DAG. Now after we had re added the member to windows cluster and DAG and we also added two of the database copy to the problem Mailbox server (which is now fixed) back, as we tried to add the third mailbox database copy we encountered the following error. [PS] C:\Windows\system32>Add-MailboxDatabaseCopy -Identity usersDB -MailboxServer ex-mb1 -ActivationPreference 2 Server “EX-MB1” has reached the maximum database limit of 5. + CategoryInfo          : InvalidOperation: (UsersDB:ADObjectId) [Add-MailboxDatabaseCopy], RcrExceedDbLimitException + FullyQualifiedErrorId : 61A9F5C9,Microsoft.Exchange.Management.SystemConfigurationTasks.AddMailboxDatabaseCopy So, we know that Exchange 2010 Std server has a hard limit of 5 active mailbox databases on it. Hence, we checked the exchange management console and found 4 active databases on the server, now this was a huge concern. So we decided to dig deep and we opened Adsiedit and went to databases under exchange administrative group in configuration partition. CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=North company,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=org Here we were able to locate all sorts of databases, basically, all the databases in the whole exchange organization including our problem server and other mailbox servers in exchange organization,...

Exchange 2010: Unable to add Mailbox Database copies on DAG member servers, Error: An error occurred while processing a request on server

Follow me This issue is about an Exchange 2010 HA deployment which we almost 4 years back and today some of the mailbox databases dismounted, we found issues with Windows cluster and database availability group which we fully explained and fixed in Part 1 of this article series, You may want to have a quick look there to ensure what exactly has happened so far. Anyways, here we will be picking from where we left. We fixed our DAG in part 1 and now we started adding our databases copy back to our problem server (which is now fixed), so I simply right click on the database and click to add a copy to my problem Exchange server, I received the following error, In the snap in I could see the copy (Only after completely exiting and restarting the EMC) but the health said failed. Incremental seeding of database JournalDB\EX-MB1 encountered an error. A full reseed is required. Error: The Microsoft Exchange Replication service failed to determine   if the log files in database ‘JournalDB’ are divergent from the source copy on server ‘EX-MB2.domain.org’. Error: An error occurred while processing a request on server ‘EX-MB2’. Error: Database ‘33962035-b005-4a26-ad1f-43639040e9dd’ was not active on source server ‘EX-MB2’. So if we read this error carefully, it’s basically suggesting that we need to do a complete reseeding of the database as it just cannot resume from where it left before failing, I feel that’s completely acceptable especially when we actually took the problem server off DAG and readded it, we cannot just expect replication to reconvene from where we left it. Thankfully this problem has...

Unable to Mount Microsoft Exchange DAG Database, Error: Failed to determine the mount status of the active database copy

Follow me Around a couple of years back we did an Exchange 2010 HA project for a client in Florida, it was a simple 2 Mailbox server and 2 CAS/HT server highly available Exchange 2010 setup.  So this client called us a few days back stating that some of his exchange databases are dismounted and mail flow was interrupted.  I checked the server to find some interesting issues which I wanted to document here. I started with Exchange Management console and found that the databases which were part of DAG were running successfully on the other server but couple of databases which were local to one of the server were dismounted, as first try, I simply tried to mount them and they failed to mount with the following error ——————————————————– Microsoft Exchange Error ——————————————————– Failed to mount database ‘Mailbox Database DB1’.   Mailbox Database DB1 Failed Error: Database ‘Mailbox Database DB1’ can’t be mounted on server ‘EX-MB1.domain.org’ due to a previous error: Failed to determine the mount status of the active database copy. Verify that the underlying cause of the error has been corrected before attempting to mount the database. The error can be ignored and the mount allowed if Mount-Database is reissued with the -Force switch.    ——————————————————– OK ——————————————————– So as we can see in last line of error that we do have an option to use Mount-Database -Force switch to force mount the database but I usually do not recommend force mounting a database as Exchange must have unmounted it to prevent some damage. So I wanted to fix the issue, it was clearly a DAG issue. I went...

Microsoft Exchange: Relay Access Denied Error 554 5.7.1

Follow me A customer with Microsoft Exchange 2010 suddenly reported email down situation, we found the databases to be Mounted and Outlooks were connected fine, it was just that when they were sending outbound email they were getting error Relay access denied Error 554 5.7.1 Your message wasn’t delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may be preventing delivery. The following organization rejected your message: mx1-us1.ppe-hosted.com. Diagnostic information for administrators: Generating server: -Exchange.Domain.com shishir@pledgetechnologies.com mx1-us1.ppe-hosted.com #554 5.7.1 <shishir@pledgetechnologies.com>: Relay access denied ## We troubleshoot the error and found that the issue to be with Smart host server with an US based company PPE.  PPE was acting as smart host as well as Spam protection for the Exchange server.  To troubleshoot and to eliminate the role of PPE We created a new Exchange Outbound connector, Under Organisation Configuration -> Hub Transport -> Send Connector This was configured as an Internet connector ( to relay emails directly to internet) and not via the smart host. We disable the existing smart host send connector and started outbound email delivery directly via internet, this fixed our outbound emails After ensuring the issue was with PPE  smart host solution, We didn’t try fixing inbound connection as such (our MX was pointed to PPE ) instead we called them and had our PPE issue resolved. Incase you also want to fix the incoming and want to remove the role of SmartHost/ Spam filter then follow the steps above to create an outbound send connector to...

Exchange with Local Domain – Your Certificate will Expire by Nov 2015

Recently, I noticed that the Certificate Authorities like GoDaddy are issuing a warning when you purchase a Certificate with Internal Sever name (example: domain.local). The use of internal domain names has been discontinued by Certification Authorities and Browsers (CAB). If you intend to issue a certificate with .local or any internal domain name, then your certificate will expire by November 2015. After November 2015, you’ll loose the ability to purchase an SSL Certificate if you include a .local domain or any other internal domain in it. If you already have one, and you have not done anything about it till Nov 2015, it will expire. You must have a question in your mind, why not purchase the certificate without the internal domain (.local) and use it. Yes, you can use it, however if your Internal domain is .local, then your users will continuously get Certificate warning on Outlook when launched and while using it. What does it mean for you? Since Active Directory was introduced by Microsoft, most of the users have promoted their internal domain separate from an external domain. Exchange Servers were configured with the internal domain names as well. Outlook always contacted the Exchange Server via its .local domain name. Now, if you also have a similar environment, you must be thinking about how you can avoid this from happening, and also issue a proper certificate for your Exchange Organization. How do you fix it – Redirect your Exchange Server to use External URL You’ll need to run the following commands on your Exchange 2007 or Exchange 2010 Management Shell. These commands will update the URL for three services:...

SBS 2008: Exchange Services Down with event id 2114 error 0x80040a02 (DSC_E_NO_SUITABLE_CDC)

Follow me Let me begin by saying that SBS servers are my least favourite ones and with Windows 2008 i.e. SBS 2008 its icing on the cake 🙂 .  Anyways, so a client reported with SBS 2008 server that Exchange services are down. Upon checking the server we found the following state The Server is unbearably slow and not responding at all Information storing service is stuck on Starting state System Attendant service is stuck on Stopping 🙂 We tried restarting the server in safe mode and were unable to login with Error “No Logon server available” We also tried safe mode with networking and failed with error “Netlogon service not started” PS: For Domain controller we should have tried to login to DSRM mode instead of SafeMode because on a DC, local SAM is disabled. I forgot to do that but just putting it here for other’s reference. We booted the server back to Normal mode and connected to services snap-in from another machine in the domain. We went ahead and disable all the Exchange & SQL services on the server. Apart from this we also did a clean boot on the server and rebooted it . (Refer Article, How to cleanboot) This time-server came back up quite fast and also it was responding OK.  We executed DCdiag on the server and found it to be clean.  Tried starting exchange services but the services failed to start. Upon examining the event viewer we found event Id 2114 with following error repeatedly Process MAD.EXE (PID=6276). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP)...