Restrain Exchange Corruptions Invoked from Incorrect Active Directory Policies

Productivity of any organization is directly proportional to a smooth information flow, and companies are striving best to deploy ultimate communication technologies in their premises. Ruling all generations of technology, Microsoft Exchange Server is definitely an expert email server technology which demonstrates its powerful collaborative features with the most popular MS Outlook email client. Better contact management, appointment scheduling, calendar management, and advanced email storage services had genuinely benefited Microsoft in gaining its popularity and world-wide acceptance in comparisons to other email servers available in the IT industries.

Moving towards the technicalities of MS Exchange Server, this email server stores all email user accounts, comprising of emails, contacts, journals, sent items, appointments, calendars, etc. in the Extensible Storage Engine Database (EDB) file. To facilitate the accessibility of email item, Exchange Server regularly synchronizes with MS Outlook to generate a mailbox copy on standalone systems. Running and maintaining high availability during all critical events is the challenging tasks for Exchange. As the latest versions of Exchange, i.e. MS Exchange Server 2013 and 2016 are integrated with intelligent and heavy features, their resource and bandwidth utilization has increased marginally, which sometimes degrades the network connectivity. It has been seen that MS Exchange Server 2013 also exhibits temporal disconnection and reconnection problem. One shouldn’t take this situation casually as regular disruption can destroy the integrity of email items stored in EDB files.

Perceived Evidences for Frequent Disconnections from Exchange Server 2013

Microsoft Outlook users who are connected with Exchange Server 2013 stuck with the problem of email services unavailability because of Exchange Server 2013 disconnection. However, users are not aware of intrinsic technicalities that are responsible for frequent disconnection and reconnection of Exchange with Outlook. But, Server Admins can clearly deduce the possible reasons behind the mentioned problem. Some of them are depicted here:

  • Display of specific error events in the Exchange 2013 Event Viewer indicates critical problem in the Outlook service. You can view the entire error sequence by navigating to Application and Services Logs –> Microsoft –> Exchange –> ActiveMonitoring. The window will display the following error:

    Microsoft.Exchange.Data.Storage.DatabaseNotFoundException: The database with ID couldn’t be found.

  • Admins might encounter with a situation where MSExchangeRpcProxyAppPool is restarted relentlessly. A brief grab of an error from the system logs is mentioned in the following.

    Level: Error
    Source: Service Control Manager
    Machine: The Microsoft Exchange PC Client Access service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.

  • Automatic disconnection of MS Outlook email client from Exchange Server 2013 for minimal amount of time and then subsequent reconnection also signals the violation in the Exchange database.

The reason behind all the above mentioned findings is the deletion of default public folder settings with the usage of Active Directory Services Interface Edit (ADSI Edit) tool. The default public folder configurations so deleted is indicated by the Exchange Server 2013 database as a default one. You can fetch the actual description behind this problem by entering the following command:

Get-MailboxDatabase | FL name,PublicFolderDatabase

Concrete Troubleshooting Guidelines to Rectify Exchange Disruption

It is to be noted that any misconfigured policies in the Exchange Server Active Directory poses a serious threat to the Exchange database and EDB files. Hence, if you have used ADSI Edit to configure incorrect settings, then catastrophic incidences couldn’t be avoided. However, to put maximal efforts at the final hour, you must destroy the root problem. Just delete the public folder settings from each Exchange Server 2013 mailbox which is directing towards the deleted public folder database. To do this, follow these simple steps:

  • In ADSI Edit, establish connection to CN=Configuration
  • Go through the following sections: Domain.com –> Configuration –> Services –> Microsoft Exchange –> Org –> Administrative Groups –> Exchange Administrative Group –> Databases
  • Replace the msExchHomePublicMDB value with <not set>

Applying all configurations and modifications doesn’t guarantee the recovery of Exchange database or EDB file that are corrupted because of critical interruptions in the Exchange Server connectivity. Hence, one shouldn’t rely on manual processes to claim back all EDB files. In such cases, recovery of Exchange Server from root level can only be facilitated by a EDB to PST Converter solution.

Solution – Exchange Server Recovery

The Exchange Server Recovery is the ultra-modern solution to regenerate critically damaged Exchange database into the original state. It drives expert EDB file recovery using its Standard and Advanced Scan mode and provides numerous alternatives to migrate and save EDB email items safely. The software offers Office 365, Public Folders, Archive Mailboxes, or Exchange Server migrations. It supports most recent MS Outlook 2016, MS Exchange Server 2016, and Windows 10 platforms.

Leave a Reply

Your email address will not be published. Required fields are marked *