D
Daniel Feather
Hi Guys
We are currently having issues with our Windows server. We currently have Veeam Backup and Replication 9.5 installed on our server and after a few days of operation, the entire application will just stop working. You have to restart the entire server for the application to work again, then the issue happens again after a few days and the cycle continues.
I have looked at the event logs and one thing that is consistent is I keep finding an error from 'DistributedCOM' stating that 'The server {73E709EA-5D93-4B2E-BBB0-99B7938DA9E4} did not register with DCOM within the required timeout'.
I have tracked this AppID down in the registry and it is referring to the 'Microsoft WMI Provider Subsystem Host'. I have tried restarting the 'Windows Management Instrumentation' service when the server goes into this failed state, but when the service is in the process of stopping, I will get a prompt similar to the error that I get in the Event Log stating that it didn't check in within the required timeout, then the service will just get stuck on stopping, I then have to restart the server to get it back to normal.
I have tried contacting Veeam about this issue and they said that this is an issue with our Windows server and therefore they couldn't help.
Does anyone have any ideas on what might be causing this? and is there a solution?
Continue reading...
We are currently having issues with our Windows server. We currently have Veeam Backup and Replication 9.5 installed on our server and after a few days of operation, the entire application will just stop working. You have to restart the entire server for the application to work again, then the issue happens again after a few days and the cycle continues.
I have looked at the event logs and one thing that is consistent is I keep finding an error from 'DistributedCOM' stating that 'The server {73E709EA-5D93-4B2E-BBB0-99B7938DA9E4} did not register with DCOM within the required timeout'.
I have tracked this AppID down in the registry and it is referring to the 'Microsoft WMI Provider Subsystem Host'. I have tried restarting the 'Windows Management Instrumentation' service when the server goes into this failed state, but when the service is in the process of stopping, I will get a prompt similar to the error that I get in the Event Log stating that it didn't check in within the required timeout, then the service will just get stuck on stopping, I then have to restart the server to get it back to normal.
I have tried contacting Veeam about this issue and they said that this is an issue with our Windows server and therefore they couldn't help.
Does anyone have any ideas on what might be causing this? and is there a solution?
Continue reading...