DCOM was unable to communicate with the computer <Server.company.local> using any of the configured protocols. (4229871)

Chat now with support

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

DCOM was unable to communicate with the computer using any of the configured protocols.
Description

When using a Remote Task Execution Server and running a task with that Task Execution Server, you see the following error similar to the following in the System Event logs:

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 9/25/2017 12:00:00 PM
Event ID: 10009
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer:

Description:
DCOM was unable to communicate with the computer using any of the configured protocols.
Cause

DNS issue and that in MessageStats 7.4.1 it resolves remote Task Execution Servers using FQDN rather then NETBIOS name in any version earlier than 7.4.1.
Resolution

Ping the Task execution server by FQDN, what is returned? If its not correct, update your DNS entry to reflect the correct FQDN or create a local hosts file to include the corrected FQDN. That way when MessageStats attempts to resolve the Task Execution Server it can reach it by FQDN.

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title