DCOM error 10010
Just for the record, since Acronis clearly have no idea how to fix it (or don't care), TIBU 2020 still fills the Windows event log with:
Error 10010 - The server {1EF75F33-893B-4E8F-9655-C3D602BA4897} did not register with DCOM within the required timeout.
It's been reported in these forums for every version going back to 2012 at least.
The culprit is TI_Managers_Proxy.DLL.
(I know most DCOM event log errors don't really matter but it's annoying).
Attachment | Size |
---|---|
dcom.PNG | 57.82 KB |

- Log in to post comments

I will, but if you look at this thread from 2016 a system report didn't achieve anything and it wasn't fixed. There are many other threads if you search on " {1EF75F33-893B-4E8F-9655-C3D602BA4897}".
My TIBU 2020 is an upgrade, not new install.
- Log in to post comments

Laurie,
There is a KB out on this particular error look Here
- Log in to post comments

Thanks - I was aware of that KB but it's hardly a permanent solution. Surely it can't be that hard to fix?.
As it hadn't been mentioned for v2020, someone might think it had actually been.
Anyway, for me it's really just a minor annoyance, but it doesn't reflect well on Acronis.
- Log in to post comments

Hello Laurie,
this issue had multiple root causes, some of them were fixed in the earlier product version, but not all. If the issue reproduces on the latest build and you have some time for investigation, it's worth raising a support ticket, where our engineers can involve the development team.
- Log in to post comments

On my old PC this issue had disappeared someday, but on the new one with fresh installation of everything it's back again. ATI2020, version 25700, event log permanently flooded with 10010 error messages for this particular component.
I will send my system report as well, hoping thar Acronis engineers will be able to identify and fix this issue.
- Log in to post comments

After applying the TI_Managers_Proxy.DLL "fix" ATI2020 let me alone with annoying 10010 error messages.
Yesterday I updated to ATI2021, and guess what - the issue is back.
Why is it so difficult to fix such problem which is reproducibly experienced by so many users across many versions and over years???
I will not buy any further updates unless this problem has been fixed.
- Log in to post comments

Hello Karsten,
sorry to know you've faced this issue with our software! I'm afraid the only workaround for now is renaming ti_managers_proxy.dll per instructions in https://kb.acronis.com/content/62200
- Log in to post comments