ERROR 183, Cannot create a file when that file already exists
ERROR 183, Cannot create a file when that file already exists
A folder with a bunch of files got deleted. I manually copied the files (the Syncovery backups of this folder) back to the destination by dragging and dropping in Windows. Now when Syncovery runs I get errors for all of the files that were copied. The error is ERROR 183, Cannot create a file when that file already exists.
Re: ERROR 183, Cannot create a file when that file already exists
Hello,
this message usually occurs when Syncovery tries to move a file or folder, but the destination already exists.
Sometimes you just need to run the job a second time, and the error message will go away.
If it does not, and you are using the feature "Cache Destination File List", you could try deleting the cache database.
But I feel that your case might be something else, and your description is too short to guess what is happening.
The most important question is: did you run the job only once and got these errors, or do you get them every time?
If you get them repeatedly and the errors won't go away, then please send one log file to support@syncovery.com so we can analyze it in detail.
this message usually occurs when Syncovery tries to move a file or folder, but the destination already exists.
Sometimes you just need to run the job a second time, and the error message will go away.
If it does not, and you are using the feature "Cache Destination File List", you could try deleting the cache database.
But I feel that your case might be something else, and your description is too short to guess what is happening.
The most important question is: did you run the job only once and got these errors, or do you get them every time?
If you get them repeatedly and the errors won't go away, then please send one log file to support@syncovery.com so we can analyze it in detail.
Re: ERROR 183, Cannot create a file when that file already exists
Just sent an email with a log file. I've run the job in attended mode a few times, but the error still remains. Thanks for looking into this. File caching is not on.
Re: ERROR 183, Cannot create a file when that file already exists
I was doing troubleshooting today and I believe I corrected the issue*. Thinking it was the profile, I created a new profile and manually made the settings the same as the other profile. This did not work. It was still trying to copy from a phantom JAR2 folder. The JAR2 folder does not exist in the source file system (left side). Then I turned off, "Detect moved files and renamed folders and adjust on..right." I started the profile in attended mode this time it showed that it was going to copy from the "JAR" folder. I ran the profile, and it copied the 20 missing files from inside of the JAR folder. After that I turned that setting back on "Detect moved files..." and everything worked. I believe that this would have also worked if I had done the same thing in the original profile. In hindsight I don't think it was necessary to create a new profile. However, creating a new profile made me start to think differently about things and that led to finding a solution.
My theory: Right after the JAR folder was deleted, another JAR folder was created then renamed to JAR2. Some files were put inside of that folder (I believe these files had previously existed in the original JAR folder). Maybe Syncovery had run during this transition time and recorded files in that JAR2 folder and it was planning on moving them to the appropriate folder.
*Digging further, this didn't fix the problem completely. I have Syncovery running on 2 Windows computers that backup a single shared directory. When I tried the same things to fix the same problem with Syncovery on the other computer it did not correct the issue.
My theory: Right after the JAR folder was deleted, another JAR folder was created then renamed to JAR2. Some files were put inside of that folder (I believe these files had previously existed in the original JAR folder). Maybe Syncovery had run during this transition time and recorded files in that JAR2 folder and it was planning on moving them to the appropriate folder.
*Digging further, this didn't fix the problem completely. I have Syncovery running on 2 Windows computers that backup a single shared directory. When I tried the same things to fix the same problem with Syncovery on the other computer it did not correct the issue.