Skip to main content

The server {1EF75F33-893B-4E8F-9655-C3D602BA4897} did not register with DCOM within the required timeout.

Beginner
Posts: 1
Comments: 0

I am getting frequent DCOM errors  with the above message - 100s in a day. They seem to be associated with TI_Managers_Proxy.DLL

I have a Win 10 64bit system with all updates applied. It started life as a clean Win 10 install.

Why am I getting this and how can I fix it?

Forum Hero
Posts: 29
Comments: 9700
mvp

Top

John, welcome to these user forums.

It is difficult to say from the brief details you have provided whether this error is related to Acronis True Image or not?

I would recommend opening a Support Case directly with Acronis Support and send them an Acronis System Report which will include a copy of the Windows System & Application event logs, that they could review to see if there are any indications that any Acronis programs or link libraries etc are involved.

Beginner
Posts: 0
Comments: 2

Top

I am having the same problem. I did a fresh instali of Windows 10 creator. I installed Acronis 2017, 8053 and I get event error 10010, The server {1EF75F33-893B-4E8F-9655-C3D602BA4897} did not register with DCOM within the required timeout. Everytime I boot the computer I get more than 10 event error on just this issue.

I talked to a Acronis tech rep on the phone and he said that the problem isn't Acronis, but Microsoft new registration system in Windows 10 Creator. Hum, Something tells me Microsoft is not going to fix this problem.

This is an irritating issue and needs to be fixed, ASAP.

 

 

Forum Hero
Posts: 29
Comments: 9700
mvp

Top

D Myers, welcome to these user forums.

I am not aware of any Acronis cause for this particular DCOM error being reported in the system Event logs, but if it is caused by ATIH 2017 then you will need to continue to work with Acronis Support via a support ticket to resolve it.

See webpage: KB3213986: Stuck at "Please wait for the local session manager" which has a fairly long discussion between other users and Microsoft for the same error, where the last update would suggest that using multiple logins and not using an Administrator account can contribute to these problems.

ATIH 2017 requires full administrator privileges in order to work correctly and should be installed from an Administrator account.

Forum Hero
Posts: 29
Comments: 5601
mvp

Top

My suspicion is that if you are using a Microsoft account to log on to your computer that is the problem.

If you are I would try to log on to Microsoft at this link:   https://login.live.com/ on the computer having the issue and see if that clears things up for you.

Beginner
Posts: 0
Comments: 2

Top

I am the only user/administrator and login as "owner" and no password on the local account only. Except for "guest" there are no other accounts on this computer. Discussions with Microsoft level 3 tech support says Acronis is the problem.

Any more suggestions?

 

Forum Hero
Posts: 29
Comments: 9700
mvp

Top

The only other suggestions are as follows:

  • Reopen your Acronis Support Case and request this issue be escalated to their second level or development.
  • Uninstall ATIH 2017 and test that this problem has stopped happening.  If it has, then run the Acronis Cleanup tool (link below) to ensure all traces are removed, before doing a clean install and checking to see if the problem returns or not?

In reply to by Steve Smith

Forum Member
Posts: 36
Comments: 49

Top

If you do an Internet search for the string "1EF75F33-893B-4E8F-9655-C3D602BA4897" you'll find essentially identical reports going back at least as far as 2012, some in Acronis forum posts.

Forum Hero
Posts: 29
Comments: 9700
mvp

Top

Bert, I understand that you can search for and find evidence of other users reporting the same issue but there is nothing any of the users here in these forums can do to help resolve this even if it is proven that it is caused by a particular Acronis component.  Only the Acronis developers can confirm if this is a problem in their code, and only they can make any changes to that code if it is necessary.

In reply to by Steve Smith

Beginner
Posts: 0
Comments: 1

Top

True Steve. But I came back to the same results, reaching back till at least 2012, and it didn't get any batter with version 2018 = that's 6 years to get something fixed.

My system is Win 10, latest patches, and apart from those DCOM errors, my logs are clean.

It doesn't need rocket science to find the issue. Searching the registry for the specific AppID in the system error log comes up with following registry key:

Computer\HKEY_CLASSES_ROOT\AppID\{1EF75F33-893B-4E8F-9655-C3D602BA4897}

which contains following Value:

TIManagersProxy Class Application

How about passing this on to the programers and save them the work to find excuses why they didn't fix it in those last 6 years? This is clearly a True Image issue, and the key goes away when uninstalling True Image, as do the DCOM errors.

I do have a support case, btw, but thought it might help to post it here too, just to clarify where exactly the issue is.

 

Forum Hero
Posts: 29
Comments: 9700
mvp

Top

Werner wrote: "How about passing this on to the programmers and save them the work to find excuses why they didn't fix it in those last 6 years? This is clearly a True Image issue, and the key goes away when uninstalling True Image, as do the DCOM errors."

I would love to be able to do so but am just another user with no extra access to Acronis programmers, developers or anything else other than some private MVP forums which have been fairly quiet of late!

The reality here is that this probably is a side-effect of how the Acronis code works, perhaps it is poor or lazy programming but from what I understand the only ill effect is that these log entries are posted which very few users of the software would ever see.  The majority of users would never think of looking at the Windows Event logs and most wouldn't even know how to start to do so.

In reply to by Werner Kaffl

Beginner
Posts: 0
Comments: 1

Top

Fully support. See this problem also for several years, the problem is in True Image 100%

Beginner
Posts: 0
Comments: 3

Top

Yes, the problem is definitely True Image, and I have it too. It relates to the process "TIManagersProxy Class Application" which is the Acronis dll ti_managers_proxy.dll. That's all I can say and I don't know how to fix it.

I, like hundreds of other users no doubt, will not report this fault to tech support because I will get charged. Consequently Acronis will continue to deny that it's a problem and it won't get fixed.

This software is so inherently flawed by using a support paywall, which is making users pay for the bugs in their software, and blocking their devs from getting a true picture of what's going wrong. I don't know why they continue to do this, and I'm surprised this business is still operating tbh. It started out as a world leader and now it's a pos.

Forum Hero
Posts: 29
Comments: 9700
mvp

Top

Stephen, welcome to these User Forums.

If you have ATI 2017 or 2018, then you could open a Support Case for this issue without fear of being charged, as Acronis changed the Support model with these releases and went away from only giving 30-days support (from date of purchase) to now giving 2 years support.

If, as you say, hundreds of other users are not reporting this problem, then Acronis won't know that there is a significant problem and won't be looking any time soon at fixing it.

One option that is open to all users, regardless of the version of ATI installed, is to use the Feedback tool - this is shown in the ATI GUI Help section, or else there is an online Feedback page that can be used.

Beginner
Posts: 0
Comments: 3

Top

I am glad to hear that has been changed finally, that changes everything. I will open a case then.

Forum Hero
Posts: 29
Comments: 9700
mvp

Top

Stephen, please see webpage: Acronis Support Lifecycle Policy for Consumer Products where the new support arrangements are documented.

ATI 2017 is covered by Extended Support with no declared end date at this time where this is described in more detail on the webpage as to what it covers.

ATI 2018 has full Support given it is the latest / most recent product available.

Beginner
Posts: 0
Comments: 3

Top

Thanks. For ATI 2017 "An upgrade is considered a valid solution if no other options are available." would appear to be a total get out of jail free card then. And this particular problem has persisted through all the upgrades.

Forum Hero
Posts: 29
Comments: 9700
mvp

Top

Understand your comment Stephen, but if there is significant development work needed to resolve a problem, then Acronis would prefer to invest that work in the most current product version rather than on an older version which is already out of mainstream support.

Beginner
Posts: 3
Comments: 9

Top

The obligatory "me too" post.

 

Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          1/11/2017 03:18:14
Event ID:      10010
Task Category: None
Level:         Error
Keywords:      Classic
User:          ARMS\icela
Computer:      arms
Description:
The server {1EF75F33-893B-4E8F-9655-C3D602BA4897} did not register with DCOM within the required timeout.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
    <EventID Qualifiers="0">10010</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2017-10-31T19:18:14.025478300Z" />
    <EventRecordID>3546</EventRecordID>
    <Correlation />
    <Execution ProcessID="856" ThreadID="5048" />
    <Channel>System</Channel>
    <Computer>arms</Computer>
    <Security UserID="S-1-5-21-4174466385-3352991235-1917151931-1001" />
  </System>
  <EventData>
    <Data Name="param1">{1EF75F33-893B-4E8F-9655-C3D602BA4897}</Data>
  </EventData>
</Event>

 

This event likes to happen when the computer is slept, like once every two minutes. I wonder if It's keeping my computer awake all night when it should have been asleep.

Beginner
Posts: 2
Comments: 8

Top

"Me too" too. TI 2018 build 9850 on a clean install of Windows 10 v1709 (Fall Creators edition)

Forum Hero
Posts: 29
Comments: 9700
mvp

Top

All the 'me too's' are fine but unless the people posting these are also opening Support Cases with Acronis for this issue, then nothing is likely to be done about it.

Forum Star
Posts: 82
Comments: 1494
mvp

Top

If you want the issue to be addressed, as Steve says, you need to open a support case with Acronis (it may help to include a link to this thread).

Ian

Beginner
Posts: 2
Comments: 8

Top

I think I've fixed it.

In Component Services / Computers / My Computer / DCOM Config, right-click TIManagerProxy Class Application then Properties / Security and in both Access and Configuration click Customise and make sure Administrators have full control.

**edit** I retract the above "fix". Since the Windows 10 Fall Update (1709) the problem is back. I added LOCAL SERVICE permissions in DCOM but no difference.