Home » Categories » SureSync

Cannot create a file when that file already exists (Error 183)

The "cannot create a file when that file already exists" error can occur for a number a different reasons.

  • During the initial scan process, SureSync notes whether a file is to be added or replaced based upon whether or not that same file already exists in the destination path. If SureSync is unable to see the destination file due to permissions issues yet is does indeed exist, SureSync will encounter this error from the destination system indicating that file we intended to create as new is already present. This case of the error is caused by incorrect or inadequate permissions.
  • When SureSync copies any file, it is always copied first to a temporary file of the same size as the source. When the copy process completes and comparison of the temporary file to the source confirms an identical copy, a "rename and replace" API is called to rename the temporary file and cause it to simultaneously replace the destination copy. If the destination copy is open atthis time, this error is raised.
  • Unless the short filename option has been disabled (highly unusual), all Windows Operating Systems generate an internal, short filename (called the 8.3 filename) for all files you see in an Explorer Window. These names are not visible to the end user without going to some degree of trouble and the choice of name is not under user control. Often, older programs and processes (and sometimes even modern ones) will save a file as the same 8.3 filename format such as "DOCUME~1.TXT", for example. This means that the long file name is now in the same form as the internally generated short file names. On the same machine, this is not an issue. However, when SureSync copies the long file name "DOCUME~1.TXT" to a destination machine where a different long file name happens to have a short file name which matches "DOCUME~1.TXT", a conflict is raised and the file is not copied. When this problem is the cause of the issue, you will often see  "Possible attempt to copy a "short" file name to a location where a long file name already uses the short name." as part of the message. Often the easiest way to resolve this issue is to rename the 8.3 filename format file names.
3 (2)
Article Rating (2 Votes)
Rate this article
  • Icon PDFExport to PDF
  • Icon MS-WordExport to MS Word
Attachments Attachments
There are no attachments for this article.
Comments Comments
There are no comments for this article. Be the first to post a comment.
Related Articles RSS Feed
Action suppressed. File change or added to multiple paths since last successful synchronization
Viewed 40881 times since Aug 22, 2013
Tips for using SQL Express
Viewed 5901 times since Aug 6, 2012
SPIAgent Return code=0; Unable to initialize SPIAgent.
Viewed 4089 times since Aug 6, 2012
System.Data.OleDb.OleDbException: Invalid argument
Viewed 5055 times since Aug 6, 2012
Will a reboot be required when upgrading a Software Pursuits application?
Viewed 5666 times since Aug 6, 2012
Real-Time Monitor stuck on waiting to start
Viewed 7979 times since Aug 17, 2012
SPIAgent Configuration Utility Doesn’t List All IPs on a Multiple IP Machine
Viewed 2220 times since Aug 6, 2012
What Type of Encryption Does the SPIAgent Use?
Viewed 3256 times since Aug 6, 2012
Error 1047 System.Data.ConstraintException
Viewed 13066 times since Aug 10, 2012
SPIAgent Init unable to acquire cryptographic resources
Viewed 3356 times since Aug 6, 2012