we have a windows 2012 hyper-v host server with Veeam B&R v7 installed. On this Host I get this error three times every morning at about 08:23 am to 08:25 am:
04.09.2013 08:25:09
DCOM was unable to communicate with the computer "This server" using any of the configured protocols; requested by PID 93c (C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Backup.Manager.exe).
04.09.2013 08:25:10
DCOM was unable to communicate with the computer "This server" using any of the configured protocols; requested by PID 93c (C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Backup.Manager.exe).
04.09.2013 08:25:10
DCOM was unable to communicate with the computer "This server" using any of the configured protocols; requested by PID 93c (C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Backup.Manager.exe).
Since the problem is in accessing the COM Service on a local computer, could this be a DNS resolution issue, like it is described here? Does it affect your backups in any way?
horst wrote:I`m wordering of the name "This server" which is shown in the error message.
Yes, this is how the local server is referred to in Veeam B&R UI and that was why I suggested to try the above solution, as this clearly indicates that the issue is within a local computer (backup server, actually).
From the screenshot I can see that there's an RPC server error while adding this server to Veeam B&R console. Probably this is the root cause of your issue, so I recommend contacting support in order to resolve it.
Hi, Im having the same exact issue and have spent hours on the phone with Veeam support and providing logs. Could you please let me know if you got this resolved and what you did to resolve it? Thanks for your time.
I had the exact same issue. To resolve it, this is what I did:
1. Add remote DCOM admin access via the following:
call netsh firewall set service RemoteAdmin enable
call netsh firewall add portopening protocol=tcp port=135 name=DCOM_TCP135
2. Reboot the server
3. Go into Backup Infrastructure and add the local server using the DNS name
4. Set up a new backup repository on the newly created backup server
5. Change the Configuration Backup to use the newly created repository
6. Remove all repositories that are listed against "This Server"
You should now be able to create backup jobs and in my case use the direct SAN method of backup with an Equallogic SAN (my original problem).
We're seeing the exact same issue. It occurred immediately after installing VEEAM. Looking at the user interface, on the Files tab, there is a server called "This server" and it looks like it cannot be removed or edited.
What we're seeing is System Log errors in Event Viewer. They occur every 4 hours and given enough time there will be thousands of them;
Event ID 10009 : DCOM was unable to communicate with the computer This server using any of the configured protocols.
Immediately before the error we see this is the System Log; The Microsoft Software Shadow Copy Provider service entered the running state.
Immediately after the service starts we get the Event ID 10009 error
Immediately after that, The Volume Shadow Copy service entered the stopped state.
Given that this issue was first reported back in 2013, and that VEEAM was working on it then (?) and the issue is still present, I'm guessing that fixing this error in the program is not too important?
We opened a case but it seemed that support did not understand and we were going to go off on a tangent.
I got the same error on a freshly installed Windows Server 2012 R2 with Veeam B&R Build 8.0.0.2030.
Is there any Solution about this or should i open a Support Case?
The Support answered my Request with the following words:
"Veeam is incorrectly sending the phrase "This Server" to DNS via WMI. This is purely a cosmetic issue and never actually results in job failures or other problems because we're also trying 127.0.0.1. Will be fixed in the further releases of product."
