I have observed the similar situation couple of times in the past one year. Everything is normal from event viewer, server component state, service status, database copy health but the database activation will fail every time when I try to activate it from one of the nodes in 4 node DAG cluster. The databases are easy to do all possible operations in other 3 nodes, but one node. The issue occurs after a reboot, but will not resolve even if we wait for so longer or do another round of reboot.

Errors received are listed below,

An Active Manager operation failed. Error: The database action failed. Error: An error occurred while trying to validate the specified database copy for possible activation. Error:

SERVER:

       A server-side administrative operation has failed. The Microsoft Exchange Replication service may not be running on server server.domain.local. Specific RPC error message: Error 0x6ba (The RPC server is unavailable) from cli_RpcsGetCopyStatusWithHealthState [Server: server.domain.local]

       [Database: DB01, Server: PAM Server]

Failed to mount database " DB01". Error: An Active Manager operation failed. Error: The database action failed. Error: The Microsoft Exchange Replication service may not be running on server server.domain.local. Specific RPC error message: Error 0x6ba (The RPC server is unavailable) from cli_AmMountDatabaseDirect3 [Database: DB01, Server: PAM Server]

The error is very common, and you will be flooded with multiple resolutions however all will have longer procedure such as (not limited to),

-          Verify the health of AD

-          Look at the event log for AD replication errors

-          Check the integrity of database

-          Verify the cluster quorum status

-          And so on

Solution Worked for me (both occasions):

Try to move the PAM to different healthy node available in the DAG (not to the activation failed server), and try to repeat the operations. When you only have 2 node DAG, you may have no choice other than trying other possible solutions as we mentioned earlier this post. However, it is worth checking if you have more than one IP assigned to the DAG members in the production network range.

Move-ClusterGroup "Cluster Group" -Node NODENAME

Verify the PAM role has moved post the above command,

Get-DatabaseAvailabilityGroup -Status -Identity DAGNAME | fl name,primaryActiveManager

Once you confirm that the PAM role is currently hold by another healthy node, try to mount/activate database on server where we observed issues. It should just work fine!

Additional Info: I found this when we use more than one IP Address assigned a single network card on Exchange for relay/HA purposes. If we reassign the IPs to other nodes of the cluster, a communication gap between PAM and the node can occur. But, there are no harm in moving the PAM before you take major steps to make the cluster communication restored.

-Praveen

Published in Solutions

Microsoft Exchange team has released Update Rollup 11 for Exchange Server 2010 SP3 & Cumulative Update 10 for Exchange Server 2013. As usual these updates are addressing number of customer reported issues. These updates are also should be considered as milestone updates for Exchange 2010 and Exchange 2013 respectively.

Download Cumulative Update 10 for Exchange Server 2013 (KB3078678) now.

Download Update Rollup 11 for Exchange Server 2010 SP3 (KB3078674)

Why these updates are important?

These updates are important for the customers with existing deployments who plan to upgrade the infrastructure to the Exchange Server 2016, which is expected to be released by end of this year. Update Rollup 11 for Exchange Server 2010 SP3 & Cumulative Update 10 for Exchange Server 2013 are the important pre-requisites for Exchange Server 2016 co-existence. No earlier versions of Exchange would support the co-existence with Exchange server 2016.

For more information, please go through the following reference links.

Released: September 2015 Quarterly Exchange Updates

Update Rollup 11 for Exchange Server 2010 Service Pack 3

Cumulative Update 10 for Exchange Server 2013

-Praveen

Published in News

Event ID 15021, HTTPEvent Error An error occurred while using SSL configuration for endpoint 0.0.0.0:444 – Exchange Server 2013

Error Decription:

An error occurred while using SSL configuration for endpoint 0.0.0.0:444. The error status code is contained within the returned data.

You will find the multiple events are thrown every minute with similar description.

This is a common error I observed in Exchange Server 2013. You will observe the all or few of the following,

1. Exchange Administration Center (EAC) returns blank page
2. The OWA allows login, but returns blank similar to EAC result
3. Outlook or any other Exchange Clients will fail to connect.
4. Exchange Management Shell Fails to connect.

This happens, I suppose, due to the usage of non-existed certificate. I have verified the ID of the certificate in question with the available certificate in my SSL store, however I did not find the one which was assigned to 0.0.0.0:444.

How to Fix:

1. View the certificate binding, and identify and delete the certificate assigned to IP:Port
2.  Assing (Add) a valid certificate to it which is used by IP:Port 127.0.0.1:443.

Procedure:

Open Command Prompt (because EMS is broken)

1. Run “netsh http show sslcert

    Note down the Certificate Hash and Application ID of the certificate assigned to IP:Port 127.0.0.1:443.

2.  Run the below command to delete certificate assigned for IP:Port 0.0.0.0:444

    netsh http delete sslcert ipport=0.0.0.0:444

3. Run the below command to add the noted certificate to ipport=0.0.0.0:444

    netsh http add sslcert ipport=0.0.0.0:444 certhash=1234ed434 appid="{1010101010}"

    Note – replace the certhash and appid with the value noted earlier.

Wait for a while, and you will no longer observe the error events in the Event log and the Exchange will start functioning as normal. It is recommended to take a restart of the server post these changes.

 

-Praveen

 

Published in Solutions

Microsoft Exchange team is announcing the availability of Update Rollup and Cumulative Updates for Exchange Server 2007 SP3, Exchange Server 2010 SP3 and Exchange Server 2013.

Each of the following links will lead you to the respective pages for more detail and download.

Exchange Server 2007 SP3

More Info Link:- Update Rollup 14 for Exchange Server 2007 Service Pack 3

Download Link - Update Rollup 14 for Exchange Server 2007 Service Pack 3 (KB2936861)

Exchange Server 2010 SP3

More Info Link:- Update Rollup 7 for Exchange Server 2010 Service Pack 3

Download Link:- Update Rollup 7 For Exchange 2010 SP3 (KB2961522)

Exchange Server 2013

More Info Link:- Cumulative Update 6 for Exchange Server 2013

Brief Info:- Released: Cumulative Update 6 for Exchange Server 2013

Download Link:- Cumulative Update 6 for Exchange Server 2013 (KB2961810)

 

Share you experience, which will be helpful in planning and executing the updates.

Update from other blogs:

There are few issues observed of applying the CU6 for Exchange 2013, please read carefully and understand if your scenario has any simlarity with it.

Exchange 2013 CU6 hybrid and co-existence bugs cause administrators to despair

Solution/Fix: Exchange 2013 CU6 hybrid and co-existence bugs - Microsoft Released Script to Fix it

The above script to be applied post the installation of CU6.

-Praveen

Published in News

MS has recently announced that the Exchange 2010 SP3 is expected to be available by the first half of year 2013, which will be shipped mainly with the below additional support,

    • Coexistence with Exchange Server 2013: - As we all know, the current released exchange 2010 does not have the support for the coexistence with Exchange 2013 server. So if you wish to introduce the Exchange 2013 into your Exchange 2010 infra, you need to have the SP3 installed.
    • Support for Windows Server 2012:- You can plan the installation of Exchange 2010 (currently it supported on Windows 2008) on Windows 2012 server with the SP3 version.

Apart from these, of course as normal it will include many fixes for bugs reported etc.Not only the fixes, the it will also contain all rollups released prior to the release date of SP3.

To add to this, MS also informs that there will be modification (update) to the AD schema and the information about that will be delivered in advance to plan for the Exchange 2010 SP3 upgrade. There is also a hind that Exchange 2013 will only coexist with Exchange 2010 and 2007, so we may also expect some changes to Exchange 2007 as well while the 2003 is currently out of question unless some solid update from MS.

-Praveen

Published in News
theme by reviewshub