Sometimes there are many errors in the event logs which we ignore, and they fill up complete event log. When we have some issue and data is needed for root cause analysis, we do not see the actual data because its overwritten by meaningless messages. In this blog, we would learn how to fix Event ID: 10028 – SQL Server Distributed Replay Client – DCOM was unable to communicate with the computer.
My client contacted me when he was supposed to provide root cause analysis for the issue, but event log was showing many messages like below.
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Event ID: 10028
Task Category: None
Level: Error
Keywords: Classic
User: NT SERVICE\SQL Server Distributed Replay Client
Description:
DCOM was unable to communicate with the computer DREPLAY using any of the configured protocols; requested by PID 20f4 (C:\Program Files (x86)\Microsoft SQL Server\140\Tools\DReplayClient\DReplayClient.exe).
As we can see below, the message comes every 5 seconds.
When I looked at the message, my first question was “Are you using the Distributed Replay feature of SQL Server”. Interestingly, he was even not aware of the feature and answer was negative. His goal was to get rid of those messages which are continuously logged in “System Event Log” at a very rapid rate and filling it (every 5 seconds).
WORKAROUND/SOLUTION
If you are not using the feature and want to avoid these messages, then stop below service.
- SQL Server Distributed Replay Client.
- SQL Server Distributed Replay Controller.
You also may want to change the service startup to manual to avoid the same issue popping up after next reboot.
As soon as I stopped the service, the messages stopped coming in the event log.
Reference: Pinal Dave (https://blog.SQLAuthority.com)
First appeared on SQL SERVER – Event ID: 10028 – SQL Server Distributed Replay Client – DCOM was Unable to Communicate with the Computer