We have a chronic issue with our Exchange Server 2013 environment. Currently, our environment consists of a single Exchange Server. After installing the latest Windows Server 2012 r2 security rollup, the Microsoft Exchange Replication Service stopped working and the Exchange DB changed to an unmounted service. We were finally able to restore operation of the Exchange Server by recovering the DB and remounting. We found out post rollup, from Microsoft support, that there was an issue with .NET 4.7 Framework installation which was included in the latest rollup and was not fully tested on the version of Exchange that we are currently operating. We were able to successfully roll back from the update. However, there is an ongoing issue with the Microsoft Exchange Replication service, wherein it crashes and does not restart. When the service is not running, it causes issues with OWA, ActiveSync and Mailobox Transport. All incoming messages remain in the SMTP queue and are not delivered. Once the Mailbox Exchange Replication service has been restarted, Exchange operation appears to return to normal and Mail flow resumes. One of the directly related error messages posted in the Application Event log is below:
Azure Service Connectivity failed, Unable to Procced: Azure AD Connect Error
In my recent assignment, I was configuring new Azure AD Connect Server and helping the customer to decommission the older one. However, while configuring the Azure AD Connect Server, we encountered below error:
Azure Service Connectivity failed, Unable to Procced:
The on-premises synchronization service is not able to connect to the Azure Active Directory, Updating the proxy settings for the AD sync account may resolve this issue.