Skip to main content

B & R 11 Failed to connect to the process

Thread needs solution

Hi,

I did raise this under #25960 but got no response so I'll start a new thread.

I'm getting repeated failures of B&R 11 for all defined tasks. The details are:

Failed to connect to the process.
Additional info:
--------------------
Error code: 11
Module: 300
LineInfo: 2a463402369021a2
Fields: $module : C:\Program Files\Acronis\BackupAndRecovery\mms.exe
Message: Failed to connect to the process.
--------------------
Error code: 12
Module: 300
LineInfo: 2a463402369021a3
Fields:
Message: The operation has timed out.
--------------------

My backup location is a Vault created in folder on a 2TB USB drive connected directly to the machine which is an HP desktop running Win 7 Pro. I have run the reporting tool and have a zip file ready for you. Do you want it attached here or sent another secure location?

The backup tasks I did have defined ran OK for a couple of days but then I started getting this error. This machine previously had trial versions of TIH 2011 and ABR11 Advanced Workstation with the central management console. In trying to resolve this issue, I have already tried uninstalling, running the clean up routines for TIH and ABR and then reinstalling. The problems remain!

Suggestions?

Brenda

0 Users found this helpful

Same thing here (locally-managed ABR11 Workstation, latest available build; Win7 x64 SP1; backing up to a locally-attached external drive):

Failed to connect to the process.
Additional info:
--------------------
Error code: 11
Module: 300
LineInfo: 2a463402369021a2
Fields: $module : C:\Program Files (x86)\Acronis\BackupAndRecovery\mms.exe
Message: Failed to connect to the process.
--------------------
Error code: 12
Module: 300
LineInfo: 2a463402369021a3
Fields:
Message: The operation has timed out.
--------------------

Hi Robert and Brenda.

I have nearly the same setup, but Win 7 64 bit ultimate. I have B and R 11 advanced workstation. I had the same cannot connect error. The error is solvable. There seems to be a problem setting up the default "AMS User" and the other two default Acronis backup users. This is what I did:

1. Uninstall Backup and Recovery. It takes about 5 minutes.

2. Remove all traces of "AMS User" and the other two acronis users. To delete the user profiles do this:
-Left click start:Right click computer:left click properties:left click advanced system settings:left click Setting button in User Profiles pane:left click user profiles:click delete. Do this for all of the acronis users that were there.
try to remove all evidence of these users from the computer.

3. Reboot

4. Create a user. I used "AcronisUser". I gave this user administrative privileges.

5. rerun the installation exe. Mine was called ABR11A_17318_en-US.exe. Of note, when I tried to rerun the installation I was given an option to uninstall more Acronis things. I took that option and uninstalled some more things. Then I rebooted and ran the installation again.

6. When the installer asks to either use an existing user, or to create a new one, definitely be sure to use your own user "AcronisUser". This seems to be the most important part of this repair procedure.

7 Finish the installation.

A full re-installation takes about 15 minutes, I believe.

For some reason, when I did this procedure, all of the permissions problems evaporated and I have a 100 percent functioning B and R 11. I believe that the permissions and ownership of the "AMS User" and the other two users like that are installed incorrectly by the installation routine. For some reason, using your own user works much better.

Thanks John,

I'm glad it worked for you, but alas, not for me. And I was very careful about assigning the proper groups and rights (such as log on as a service) so the installer wouldn't have to touch it.

I'm afraid it might be just a matter of time before it bites you again as well. This behavior in the initial builds induced me to revert to ABR10. I tried again only many months later. First, I concluded that the newer build somehow fixed itself. Then, same problem resurfaces on the latest build.

There must be a fundamental lack of quality to have resulted in a product so fragile.

And Brenda, I noticed that on a parallel thread Acronis support is asking their first victim to run the AcronisInfo utility. Good luck with that ;-)

Way back when I started with ABR10, AcronisInfo wouldn't even run to completion. Their diagnostic-gathering program would crash before it could collect any meaningful data. I haven't tried that again either.

I fixed this without uninstalling everything; you have 4 services at the top of the services list after the installation,

To get to services, go to start/run or search in windows 7 and type in services.msc

in here you will find at the top normally the 4 services

Acronis Managed Machine Service user account .\Acronis Agent User
Acronis Remote Agent Service user account .\local system account
Acronis Removable Storage Management Service user account .\local system account
Acronis Scheduler2 Service user account .\local system account

next
I went into the user account ( control panel users )and reset the password for acronis ( i chose acronis as the password to keep it easy )after checking that is was an administrator so that I could use it on the other three services

next I changed the thee services to the user account ( double click on the service and go to the log on tab )

Acronis Managed Machine Service user account .\Acronis Agent User
Acronis Remote Agent Service user account .\Acronis Agent User
Acronis Removable Storage Management Service user account .\Acronis Agent User
Acronis Scheduler2 Service user account .\Acronis Agent User

Make sure you type the password again for the service you didnt change as you did change the password, next restart all 4 services ( right click restart )

If you have any services that dont start check you have typed the password that you chose correctly when you reset the acronis password.

once yo uahve all 4 services running try your job again , for me at this point is was fixed.