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...

IIS stuck with old SSL Certificate despite of deleting it from Server

Follow me Recently one of out client requested to configure remote app publishing through windows 2012 server. After configuring all remote app setting it failed because of certificate error as Remote app requires a valid trusted certificate to be installed so that the clients can open the applications from their desktop icon.  We went ahead and generated a self signed certificate on the remote app server and assigned it correctly on the required sites in IIS by editing the binding settings. Refer the screen shot below However despite of these changes the server kept presenting the old server certificate and hence the remote app wasn’t able to connect. I even deleted the old server certificate from the server and rebooted the server but still it kept presenting the old certificate. I researched further and found the following commands to check the installed certificates on the server and delete them as needed. Following command (ran from command prompt) display the certificates installed on a server. Netsh Http Show Sslcert   As we can see in the screenshot above, this command did reveal that the old certificate (which I had already deleted from the server) was still present on the server. The old and new certificates can be identified from the certificate hash value.   I used the following command to delete the non required stale certificate from the server Following command (ran from command prompt) deleted the required certificate from the server. Netsh delete Sslcert Ipport=[::]:443 (please replace IP Port value with your required value After this SSL certificate was deleted we ran the following command again and validated that its showing only...

Planning to upgrade to Outlook 2016 ? Better Think Again !!! Error :Outlook cannot log on

Follow me If your organization is planning to upgrade all their PC’s to Office 2016 or just Outlook 2016 then I would recommend you to wait a little longer especially if you are on Office 365.  Reason being yet again, the biggest multibillion $$ IT software company is doing the beta testing on its customers, because of which its own products Outlook 2016 and Office 365 are having issues to seamlessly connect to each other. The functionality of Autodiscover is supposedly changed in Outlook 2016 and I can only guess but probably for that reason 9 out of 10 times when you uninstall your existing Office 2013 or 2010 and install the new and flashy Office 2016 (Outlook 2016) you end up having the following error. Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The Microsoft Exchange information service in your profile is missing required information. Modify your profile to ensure that you are using the correct Microsoft Exchange information service. The only solution we have found to this issue so far is to rebuild the Outlook profile for the user and that works again 9 out of 10 times.  In some rare cases we ended up creating a completely new User profile and then obviously new outlook profile with in it. We have seen this issue happening so far with Office 365 users, as we have a lot of eager customer trying to jump to their included version of Office 2016 so we are really unhappy with it and now we are asking the customer to...