J
JTPR
I have 2 scheduled backups that run daily. A local backup at 23:00 that and a backup to Azure 3x daily at 01:00, 13:00, and 18:00. I also have a scheduled reboot of the machine at 04:00 on Thursday that used to be at 04:00 on Sunday.
First, the reason for the restart. I have been having an issue with dcom error 10010 "The server {73E709EA-5D93-4B2E-BBB0-99B7938DA9E4} did not register with DCOM within the required timeout". These errors would start flooding in every Friday in the afternoon sometime and if the machine was not restarted it would eventually become unresponsive. Not finding a solution to the problem and as an interim measure while I looked into that I set it to restart on Sunday morning at 04:00. Well, the errors would pile up and the restart would stop them until the next Friday. But I noticed that the Saturday backups, both of them, did not occur on Saturday. No errors, just wouldn't happen. Also, sometimes, the task to run the restart also did not happen.
So I moved the restart to 04:00 on Thursday to see if the errors would occur on Friday again, or on Tuesday or Wednesday. To see if it was a Friday issue or a time since restart issue. They moved to Tuesday. I'm going to schedule the second restart on Sunday at 04:00 again to see if they disappear altogether, but I realize this is no solution. But backups being the primary reason for my existence I don't like seeing any missed.
Now, that registry key indicates the Microsoft WMI Provider Subsystem Host. But before I start rebuilding WMI, which appears to be a somewhat daunting task and could come with pitfalls, how exactly can I determine that this is the solution? Why do these start happening after a period of time? Why does Task Manager fail? Oh, this is a Server 2012 with all the latest patches and updates. It is used as a file/print server and DC. The only application running on it is Quickbooks for multiuser access. That had a recent major update which changed nothing in regards to this issue.
Please let me know what else I can provide to help rectify this.
Jim
Jim Θ¿Θ¬
Continue reading...
First, the reason for the restart. I have been having an issue with dcom error 10010 "The server {73E709EA-5D93-4B2E-BBB0-99B7938DA9E4} did not register with DCOM within the required timeout". These errors would start flooding in every Friday in the afternoon sometime and if the machine was not restarted it would eventually become unresponsive. Not finding a solution to the problem and as an interim measure while I looked into that I set it to restart on Sunday morning at 04:00. Well, the errors would pile up and the restart would stop them until the next Friday. But I noticed that the Saturday backups, both of them, did not occur on Saturday. No errors, just wouldn't happen. Also, sometimes, the task to run the restart also did not happen.
So I moved the restart to 04:00 on Thursday to see if the errors would occur on Friday again, or on Tuesday or Wednesday. To see if it was a Friday issue or a time since restart issue. They moved to Tuesday. I'm going to schedule the second restart on Sunday at 04:00 again to see if they disappear altogether, but I realize this is no solution. But backups being the primary reason for my existence I don't like seeing any missed.
Now, that registry key indicates the Microsoft WMI Provider Subsystem Host. But before I start rebuilding WMI, which appears to be a somewhat daunting task and could come with pitfalls, how exactly can I determine that this is the solution? Why do these start happening after a period of time? Why does Task Manager fail? Oh, this is a Server 2012 with all the latest patches and updates. It is used as a file/print server and DC. The only application running on it is Quickbooks for multiuser access. That had a recent major update which changed nothing in regards to this issue.
Please let me know what else I can provide to help rectify this.
Jim
Jim Θ¿Θ¬
Continue reading...