Exchange

Exchange 2013 DB’s not mounting, Exchange Replication crashing

I am facing an issue where my Exchange 2013 server has run into trouble mounting databases. Also the Microsoft Exchange Replication has crashing repeatedly.

Attempting to mount database result in error during the crash events.
Error: An Active Manager operation failed.
Error: The database action failed.
Error: The Microsoft Exchange Replication service may not be running on server

It becomes a race condition to mount the database during the very brief window between the service restarting and then crashing

I’ve attempted:

Restarting the “Microsoft Exchange Replication” Service – crashes with Event ID 7031 – The Microsoft Exchange Replication service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.

Restarting the “Microsoft Exchange Mailbox Replication” Service

Restarting the “Microsoft Exchange Mailbox Transport Delivery & Submission” Services

Restarting the host server of Exchange Server 2013

I’ve check that the Exchange Server has proper communication to the domain controllers.

I’ve check that the logon server for the Exchange Server was also in good health.

The only new introduction to our Exchange environment has been the CU6 update released on August 26, 2014. Source:  http://support.microsoft.com/kb/2961810

We recently rebooted our Exchange for maintenance and these issues started.

I hope to be able to provide more info on this as I search for a solution.

 

Update: 2014-09-19

Office 365 Support are no help and directed me to work with the Product Support Team.  Product Support indicates known bugs in my situation, although they have not been made public and wouldn’t go into further details. 

What they now want me to  turn up a new Exchange 2013 Server. Download and install CU6 (again) and install it on the new server. 

Once installed and working they want me to perform a “Forklift” migration, of my databases. 

 

Update: 2014-09-29 – Problem Fixed 

So it turns out, that the cause of my issue came from an application event log in the following location which contain corrupted items:  Applications and Services Logs / Microsoft / Exchange / MailboxDatabaseFailureItems / Operational

Once removed I was able to restart the service and all was working as normal. Command issued:  Wevtutil.exe cl “Microsoft-Exchange-MailboxDatabaseFailureItems/Operational”

Remove Dead Exchange Servers from Active Directory

Working with  my Exchange 2012 Hybrid configuration I into the following error:

ERROR : Subtask NeedsConfiguration execution failed: Configure MRS Proxy Settings

Execution of the Get-WebServicesVirtualDirectory cmdlet has thrown an exception. This may indicate invalid parameters in your hybrid configuration settings.

The task wasn’t able to connect to IIS on the server ‘exchange’. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.

This is because I did not properly remove the retired exchange servers form Active Directory during past migrations to Exchange 2013.

To remove these objects to continue with your Hybrid configuration task do the following:

  1. Launch the run dialog (Windows Key + R)
  2. Type in the command “adsiedit.msc” and press OK
  3. In the drop down menu select “Configuration”
  4. Expand “CN=Configuration [domain]\CN=Services\CN=Microsoft Exchange\CN=[organization]\CN=Administrative Groups\CN=Servers”
  5. Right click on the dead server and “Delete”
  6. Navigate to ”CN=Configuration [domain]\CN=Services\CN=Microsoft Exchange\CN=[organization]\CN=Administrative Groups\CN=Databases”
  7. Right click on each dead database and “Delete”

Step 1-5 will get you past the Hybrid error, but you might as well cleanup while your here.

Cumulative Update 6 for Exchange Server 2013

I’ve been working with the Microsoft team on several issues I have faced with my Exchange Hybrid deployment.

Most recent issue: HCW Serialization Error

Today I am informed that Cumulative Update 6 for Exchange Server 2013 was just released.

Cumulative Update 6 for Microsoft Exchange Server 2013 was released on August 26, 2014. This cumulative update resolves a list of issues.

Source:  http://support.microsoft.com/kb/2961810

Download Here

 

O365: On-premises users aren’t getting email messages from Office 365 users in an Exchange hybrid deployment

It was complex, and it was difficult; but I was able to get a hybrid setup with my exchange server (on-premises) with Office 365

I am still working on other items such as logging in with a default domain suffix of my choosing but more on that later.

The issue I had faced involved sending emails from my email account now hosted in O365 to emails on my On-Premise Exchange Server. Each attempt would fail.

So I followed the steps listed in the following kb article  kb2730609

  1. Sign in to the Office 365 portal (https://portal.microsoftonline.com) as a global admin.
  2. In the header, click Admin, and then click Exchange.
  3. In the left navigation pane of the Exchange Admin Center, click Mail Flow, and then click Accepted Domains.
  4. Select the domain that is set up for the hybrid deployment, and then click Details.
  5. Select Shared, and then click Save.

As I said prior somethings were complex and I will address that as this was only part of my resolution

Exchange Server 2013 SP1

If your following my posts you may notices I touched on a bug with Exchange 2013 SP1 before even posting about this update. That’s because I started to write this and didn’t yet finish; better late than never; I guess!

The following enhancements have been made with the release of Service Pack 1 for Exchange 2013

  • Support for running Exchange 2013 SP1 on Server 2012 R2.
  • Support for Windows Server 2012 R2 Domain Controllers and Windows Server 2012 R2 Forest and Domain Functional Level.
  • MAPI over HTTP. More information on MAPI over HTTP here. Note that MAPI over HTTP requires Outlook 2013 SP1; you can download Office 2013 SP1 32-bit version here and the 64-bit version here.
  • DLP policy tips for OWA.
  • Add custom document types to DLP using fingerprinting technologies.
  • Cmdlet logging in Exchange Administrative Console.
  • Support for IP-less DAGs (on Windows Server 2012 R2).
  • S/MIME support.
  • Rich-Text editor for OWA.
  • Edge Transport server role.
  • Support for SSL Offloading.

Notice
Since the release of Microsoft Exchange Server 2013 Service Pack 1 (SP1), Microsoft has become aware of an issue that affects some customers who use transport agents that are provided by third-party OEMs. For more information about this issue and a supported fix, see the following Microsoft Knowledge base article:

2938053 Third-party transport agents cannot be loaded correctly in Exchange Server 2013

This service pack resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

  • 2860242 HTML format is lost after saving as an MSG file in Exchange 2013
  • 2900076 Mailbox quota warning message uses an incorrect language in Exchange Server 2013
  • 2910199 “Reply all by IM” chat window displays seven recipients in Outlook Web App
  • 2913999 Meeting request body and instructions are lost in delegate’s auto-forwarded meeting request
  • 2918655 Microsoft.Exchange.Servicehost.exe crashes after you enable FIPS
  • 2918951 Users cannot access public folders after you upgrade to Exchange Server 2013 Cumulative Update 3
  • 2925281 Outlook connectivity issue if SSLOffloading is “True” in Exchange 2013
  • 2925544 Empty ExternalURL value for ActiveSync virtual directory after build-to-build upgrade of Exchange Server 2013
  • 2927708 Resource mailboxes that are created by EAC will not be updated by policies in Exchange Server 2013
  • 2928748 Default from delegate’s address in shared mailboxes in Exchange Server 2013
  • 2928803 Long server connection for Outlook after a database failover in Exchange Server 2013
  • 2930346 POP3 access does not work if the name of the resource mailbox differs from the user’s name
  • 2930348 Manual redirection occurs in Outlook Web App if External URLs in each site are the same
  • 2930352 Outlook Web App cross-site silent redirection does not work in Exchange Server 2013