Discussions specific to the VMware vSphere hypervisor
Post Reply
frinnst
Influencer
Posts: 17
Liked: 1 time
Joined: Aug 26, 2013 1:32 pm
Full Name: Fredrik
Contact:

DCOM was unable to communicate with the computer <ESXi host>

Post by frinnst » Jan 29, 2018 3:39 pm

So we added an esxi host temporary to veeam b&r. Now i get these messages daily:

DCOM was unable to communicate with the computer <ip of esxi host> using any of the configured protocols; requested by PID 44a8 (C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Backup.Manager.exe).

The host has since been removed from the inventory but we still see the messages. I'm a bit confused - a DCOM connection attempt to an esxi host is doomed to fail. Has anybody seen this before?

v.eremin
Product Manager
Posts: 16137
Liked: 1318 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: DCOM was unable to communicate with the computer <ESXi h

Post by v.eremin » Jan 29, 2018 7:43 pm

Have you contacted our support team already? Thanks.

frinnst
Influencer
Posts: 17
Liked: 1 time
Joined: Aug 26, 2013 1:32 pm
Full Name: Fredrik
Contact:

Re: DCOM was unable to communicate with the computer <ESXi h

Post by frinnst » Jan 30, 2018 8:51 am 1 person likes this post

I've created a case now; #02515067

v.eremin
Product Manager
Posts: 16137
Liked: 1318 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: DCOM was unable to communicate with the computer <ESXi h

Post by v.eremin » Jan 30, 2018 11:35 am

Thanks, let's wait and see what support engineer says about the problem experienced.

StefanB
Influencer
Posts: 13
Liked: 3 times
Joined: Oct 15, 2013 7:20 am
Contact:

Re: DCOM was unable to communicate with the computer <ESXi host>

Post by StefanB » Feb 12, 2019 7:04 am

Same here since update of Veeam One 9.5 U4 (Win2016 german language)

Every minute a entry in system event log of an old rejected repository server

DCOM konnte mit keinem der konfigurierten Protokolle mit dem Computer "hostname" kommunizieren; angefordert von PID f38 (C:\Program Files\Veeam\Veeam ONE\Veeam ONE Monitor Server\VeeamDCS.exe).

foggy
Veeam Software
Posts: 17712
Liked: 1481 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: DCOM was unable to communicate with the computer <ESXi host>

Post by foggy » Feb 12, 2019 4:56 pm 1 person likes this post

Fredrik was able to resolve this by removing old hosts from Veeam B&R and rebooting the backup server. If this doesn't help in your case, I recommend contacting technical support for a closer look. Thanks!

Post Reply

Who is online

Users browsing this forum: masakichi306 and 20 guests