[Resolved] Synchronization not working and cannot be removed

You can disable the service to stop it from working.

I would try a repair intall to see if that gets it working first. Run the installer, select the Repair option.

Unfortunately did not help.
Strange thing was that when I created the second sync, it started for a minute to initialize and then it looks like I got kicked out of the synchronization and do not have access to the config as well...

AT least double check that your firewall is not blocking the traffic .

I have the same issue. Firewall is not blocking for, also repair install was done.

My initial synchronizations ran for more than 24h, although all data was copied and were available on both drives a couple of hours later.
The synch kept running, even when I try to shutdown. Waited another 12h until computer actually shut down.

After a new start of the machine and synchs are no longer configurable or startable. Also new synchs don't start. I contacted the support already with two cases and two chat sessions, but they are not comming back to me. Anyone has an idea?

Firewall was not an issue.
Don't know what broke it. I have uninstalled and re-installed and at least that part works now (even after several reboots).
New problem: Synchronizations with CIFS shares do not start, although everything is configured correctly. But that would be off topic here...

Thanks anyways for your suggestions.

<Post edited due to the violation of TOU. User's banned for 2 weeks

Not post any material or select a username that is abusive, harassing, threatening, sexual explicit, obscene, racially or ethnically offensive or vulgar.>

Although someone form Acronis ocassionally responds on this forum, it is by and large only users here. If you need to contact Acronis best to do it through chat. Alas, it is difficult to get through and if you go past the no-additional-charge-for support period, then you have to pay before you can talk to anyone.

IF your original request for a refund was placed before the stasifaction guarantee period expired, then regardless of how long it takes Acornis to get back to you, you are entitled to the refund. A person form Acronis iterated this policy yesterday here on this forum.

Hi all,

Thank you for your comments. Scott, thanks a lot for help.

Markus, do you mind sending us Acronis Info from the problem machine? These logs might shed the light onto the situation.

Thomas, we're sorry for your situation, and as discussed in another thread, we have already notified German Management team about the situation, so you will  be contacted shortly (if haven't been contacted yet).

Let us know if you have any additional questions, we will be glad to assist.

Thank you.

Thank you, Acronis for checking the forum & facilitating personal support for Markus & Thomas. That is how you build a loyal customer base.

Acronis is clear that the forums are intended for user-helping-user support; for intractable problems Acronis wants the user to to use some form of 1-on-1 tech support.

The difficulty I have with that, is that so many people seem to have similar syncing problems as that described in this forum, yet there are no work-arounds, much less acknowledgement of the problem in the KB. If Acronis knows that many users are experiencing a similar class of problems with their software (a web search shows this problem is experienced by more than the thread participants), it seems incredibly inefficient to require all of them to avail themselves of 1-on-1 tech support (inefficient for both the users & Acronis). It speaks to a lack of professionalism on many levels, from the development cycle to support .

So how does the user track Acronis' progress on this and other software issues? The KB is great if the topic already exists, but if not, it is impossible for the user to know when there will be a fix to the problem. Back in the day (when beta-testing was done BEFORE production release), many software developers would expose "issue-tracking" to the beta tester, so s/he could follow a problem & track progress.

Since Acronis doesn't have any of this kind of issue tracking available to the user, I would encourage Acronis to post any information, fixes, or work-arounds to forum threads, at least those dealing with software issues that seem to be recurring problems experienced by more than a few people. Solutions would then be much easier to track, since the web page already exists, can be bookmarked for easy retrieval, & users can be notified of new thread activity without having to regularly query a KB topic that doesn't yet exist, & maybe never will.

Thanks to anybody that is listening

Hello Steven,

Thank you very much for your post and welcome to the forum.

The reason we have to work individually with each Acronis Customer is because issues can be system specific.

I appreciate your detailed feedback and we are currently working on implementing something like this in our forum. I will also forward your suggestions  to our Program Management team via Acronis Customer Listening system. You can always submit your ideas from a special form.

Thank you.

I support Steven's proposal! Such a solution must be preferable to both Acronis and the users.

So, back to the original topic...

The problem is solved together with the Acronis guys.
In the end it was easy, but the most important hint was not being displayed in the Logs of the application but just in a log file that was located in C:\ProgramData\Acronis\TrueImageHome\Logs.
I had the share mounted with another user account than I configured for the Acronis synchronization job.
As Windows only connects to a resouce with one user/password within one session it was throwing an error in the logfile telling me to disconnect my other share mount. Unfortunately this was never either shown as a popup window or in the event log within the application.

After unmounting the share and mounting it with the same user that was used in the synchronization, everything was working fine.

Thanks to Anton and Vadim for the support!!

Hello Markus,

I want to thank you for taking the time to update our Forum Community with the solution and I am glad to know that the issue has been resolved.

Thank you.