-
- 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>
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?
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?
-
- Product Manager
- Posts: 20666
- Liked: 2375 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: DCOM was unable to communicate with the computer <ESXi h
Have you contacted our support team already? Thanks.
-
- 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
I've created a case now; #02515067
-
- Product Manager
- Posts: 20666
- Liked: 2375 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: DCOM was unable to communicate with the computer <ESXi h
Thanks, let's wait and see what support engineer says about the problem experienced.
-
- 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>
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).
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).
-
- Veeam Software
- Posts: 21164
- Liked: 2148 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: DCOM was unable to communicate with the computer <ESXi host>
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!
-
- Veteran
- Posts: 412
- Liked: 31 times
- Joined: Nov 21, 2014 10:05 pm
- Contact:
Re: DCOM was unable to communicate with the computer <ESXi host>
Same problem here with 9.5 U4, opening support ticket, However mine are for proxies and backup repositories only.
Code: Select all
DCOM was unable to communicate with the computer repostitory.domain.local using any of the configured protocols; requested by PID 7c0 (C:\Program Files\Veeam\Veeam ONE\Veeam ONE Monitor Server\VeeamDCS.exe).
DCOM was unable to communicate with the computer ip_of_proxy using any of the configured protocols; requested by PID 7c0 (C:\Program Files\Veeam\Veeam ONE\Veeam ONE Monitor Server\VeeamDCS.exe).
Bed?! Beds for sleepy people! Lets get a kebab and go to a disco!
MS MCSA, MCITP, MCTS, MCP
VMWare VCP5-DCV
Veeam VMCE
MS MCSA, MCITP, MCTS, MCP
VMWare VCP5-DCV
Veeam VMCE
Who is online
Users browsing this forum: Google [Bot] and 59 guests