Error: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine. The copier will automatically retry after a short delay.

Hi All ,

Please find the below mentioned error message and all of you share me your suggestions.It is an production issue please someone suggest me in a quick manner.

Error:

Description:

The log copier was unable to communicate with server 'DR-servername'. The copy of database 'databasename\DR-servername' is in a disconnected state. The communication error was: An error occurred while communicating with server 'PR-servername'. Error: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine. The copier will automatically retry after a short delay.

Event ID:    

 2153

Environment Details :

Exchange 2013 sp1 with three node DAG .Two node in PR site and one node in DR site.

Issue : 

1.Randomly database state switching from healthy to disconnected and healthy state on the database copies in DR mailbox server.

2.Then the above mentioned event id is generating on the application events.

Please someone suggest me quickly as possible.

March 19th, 2015 3:09am

Hi ,

Please someone shed light on this case.

Free Windows Admin Tool Kit Click here and download it now
March 19th, 2015 8:15am

Hello,

 

Have you tried disabling any third-party AV or checking if the issue caused by backup softwares?

 

Thanks, Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

 

March 25th, 2015 4:39pm

Hi Simon ,

Thanks for your response.

We have completely removed the third-party AV and backup software's on the server which is residing on the DR site.But still the DB state is randomly switching from healthy to disconnected and healthy and vice versa.At the same time the above mentioned event on my previous post is still appearing on the event logs.

Please tell me how to pinpoint where the cause for this issue is residing.

Free Windows Admin Tool Kit Click here and download it now
March 28th, 2015 8:20am

Hi Simon ,

Please tell me if anything else need to be checked.

March 30th, 2015 7:46am

Hi All ,

Any updates on this thread ?

Free Windows Admin Tool Kit Click here and download it now
March 31st, 2015 10:16am

Hi All ,

Any help on this thread?

April 6th, 2015 9:38am

Hi All ,

Is this issue is an BUG in exchange 2013 CU4 ?

I have found a link which says that it is an bug and it is resolved in CU5.Please update me if so.

Reference Link : 

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_28423594.html

Free Windows Admin Tool Kit Click here and download it now
April 7th, 2015 6:04am

HI

DAG is configured with MAPi and Replication network as separate or both are on the single nic. (please share DAG Architecture).

let me know copy queue length and replay queue length status.

please check AV and Backup software at times both will cause the mentioned issue.

April 7th, 2015 9:18am

Hi ,

Thanks for your reply.



1.DAG is configured with single card for MAPI and replication and it is extended with two sites.

site 1 - primary site - MBX 1 & MBX 2

Site 2 - DR site - MBX 3 

2.During the issue time we do have have only the limited copy queue length which is up to 9 and replay queue length is 0 .

3.We have faced the same issue even after the AV and Backup software are removed from the node which is present at DR site.

Is this a bug in exchange 2013 CU4 ?I just wanted to confirm that.

Free Windows Admin Tool Kit Click here and download it now
April 8th, 2015 12:56am

I understood  DAG configured with one nic which is used for MAPI and Replication.

On the primary site you two Mailbox servers MBX1 and MBX2 which hosting active copies of databases.

On DR Site Mailbox Server MBX3 you are experience replication issue. correct me if I am wrong.

Meanwhile please refer the below link for DAG Nic configuration.

https://technet.microsoft.com/en-us/library/dd638104(v=exchg.150).aspx#NR

also pay attention below point in the link:

MAPI networks should be isolated from Replication networks   Windows network policies, Windows firewall policies, or router access control lists (ACLs) should be used to block traffic between the MAPI network and the Replication networks. This configuration is necessary to prevent network heartbeat cross talk.

This posting is provided "AS IS" with no warranties.

April 8th, 2015 3:40am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics