Direkt zum Inhalt

Acronis true image 2020 synchronization has failed

Thread needs solution

I am trying to sync a folder to the num acronis and I am not getting it. The error synchronization has failed appears. Can someone help me?

0 Users found this helpful

Claudio, welcome to these public User Forums.

Sorry but I do not understand what you are trying to do here, please can you clarify this more?

What are you trying to sync and where to?

Well, I was trying to sync a folder with the Acronis cloud. 
When it started to sync, it gave an error. 
I closed Acronis and stopped the Acronis synchronization service on the PC.
I restarted the service again and opened the acronis sync. 
This time, it worked normally. 
The question now is: 
every time I turn on the PC, do I need to stop and restart the agent service
for the acronis synchronization to work?

 

Claudio, the sync service should automatically pause and restart itself as needed without the need for you to stop and restart the background acronis service.

Is your source sync folder being accessed by any other software such as another cloud service (OneDrive, Google Drive, Dropbox, Box, etc)?  If so, then it is possible that the Acronis Sync may be seeing locked data.

I'm syncing the music folder. But I tried with other folders and the same error occurred. 
The music folder is not being synced with other applications in the cloud.
The synchronization service agent starts when the pc is turned on. 
But when activating acronis synchronization it gives the error. 
I need to stop the agent service and restart.

Claudio, please try doing a Repair install as per KB 60915: Acronis True Image: repairing program settings - which should correct any issues related to the application itself.

Hello. I did the procedure and nothing has changed.
When I turn on the PC and open ATI, synchronization fails and displays the error.
I have to open the services on Windows and stop the synchronization service agent and restart.
When I do this, synchronization works again.

Claudio, what is the Sync Agent service start up setting?  It should be 'Automatic (delayed)'.

Next, see the following KB documents which may be related to this issue.

KB 36429: Acronis Software: exclude program folders and executables from antivirus and other security programs

KB 46430: Acronis Software: Making Acronis Products Compatible with Antivirus Software

Steve, it was 'Automatic (delayed)' and the error persisted. I changed it to Automatic and the error continues. I think the service is started, but for some reason ATI does not communicate with it. You need to stop and restart the service on windows.

Have you tried the advice in the 2 KB documents referenced above for ensuring that all the Acronis services & processes have the needed authority to run?

But isn't it weird that synchronization works when you stop and restart the service?

In this case, it does not appear to be the antivirus or firewall that is blocking.

Anyway, I will execute the procedures and return with feedback.

Claudio, the log shows an issue with the RPC service which is one of 3 dependent services used by Sync Agent.  Please check that all these services are started correctly.

Ok.

1- Remoto Procedure Call(RPC)- Automatic

2- DCOM Server Process Laucher - Aitomatic

3-RPC Endpoint Mapper - Automatic

All currently running. The question is when the ATI is first started.

Claudio, sorry but I am out of ideas for why this isn't working correctly.

I can only recommend that you raise this issue direct with Acronis Support by opening a support case with them as per How to get support?

Okay. I appreciate your help. I'm going to open a case in support. Thank you.

Sorted out. The problem was in allowing administrator privileges for the Acronis True Image 2020 application. Without this permission, the synchronization agent started with access denied to perform folder synchronization. The sync agent service was not allowed to log in to the user's account.

Claudio, glad you have resolved this issue, ATI always should be installed / run with Administrator authority due to the low level access required by the application.  Thank you for the feedback.