Event 2153 - Log copier was unable to communicate with server E13MB02.domain.local - but everything appears to be working okay???

I am periodically receiving the following error in my event log after updates and reboots last night. However, everything appears to be working fine. A get-mailboxdatabasecopystatus show the DAG as healthy on one server, mounted on the other, and no copy or replay queue. Any ideas what is generating this error?

Event ID: 2153
User (If Applicable): N/A
Computer: E13MB01.domain.local
Event Description: The log copier was unable to communicate with server 'E13MB02.domain.local'. The copy of database 'DAGDB01\E13MB01' is in a disconnected state. The communication error was: An error occurred while communicating with server 'E13MB02'. 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 Log Name: Application
Event Log Type: error
Event Log Date Time: 2015-08-01 11:16:50


  • Edited by Alceryes Saturday, August 01, 2015 4:36 PM SS
August 1st, 2015 4:35pm

Hi,

Suggestions for reference:

1. Observe frequency of Event ID 2153, if it is too high in a day, which may lead to high copy queue length, then we need to do health check on network between mailbox server.

2. Make sure TCP Chimney is set correctly on all MBX servers if you enabled and NIC drivers are up to date.

Best Regards.

Free Windows Admin Tool Kit Click here and download it now
August 3rd, 2015 5:12am

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

Other recent topics Other recent topics