39989: Acronis Files Connect: when I tried to copy some files from one location to another on the server using the Macintosh Finder, I got an error message that said "FILENA~1.TXT" already existed. What's wrong?

Question:

When I tried to copy some files from one location to another on the server using the Macintosh Finder, I got an error message that said "FILENA~1.TXT" already existed. What's wrong?

 

Answer:

Note:The following description applies to Mac OS 9 clients, or Mac OS X clients that are not running Acronis Files Connect (formerly ExtremeZ-IP) 3.0. Acronis Files Connect 3.0/Mac OS X clients can work with files longer than 31 characters.

This has to do with the way Acronis Files Connect (and Services for Macintosh) handles file names that are longer than the normal 31 characters allowed by the Macintosh. When Acronis Files Connect encounters a file that has such a name, it uses the MS-DOS 8.3 name when it reports the name to the Macintosh. Therefore, a file with a long name of: AVeryVeryVeryVeryVeryVeryLongName.TXT

and short name of:
AVERYV~1.TXT

will show up on the Macintosh client as:
AVERYV~1.TXT

(Windows NT automatically generates the short names of files for MS-DOS and Windows 3.1 clients; you can find more information about how this name is generated by consulting Microsoft's Windows NT documentation.)

As an example, suppose you have a folder that has two files in it:
AVeryVeryVeryVeryVeryVeryLongName.TXT (AVERYV~1.TXT)
AVeryVeryLongName.TXT (AVERYV~2.TXT)

When the Macintosh sees this folder, it will see the following:

AVeryVeryLongName.TXT
AVERYV~1.TXT

Now, suppose the Macintosh attempts to "duplicate" this folder (by selecting the folder in the Finder and choosing "duplicate").

The Macintosh Finder will respond by issuing a set of commands to Acronis Files Connect that include the following:

Copy file "AVeryVeryLongName.TXT" to the new directory Copy file "AVERYV~1.TXT" to the new directory

Acronis Files Connect responds to these commands as follows. First, it copies the file "AVeryVeryLongName.TXT" to the new directory. However, when it does this, Windows NT automatically generates a new short name for the file. So at this point, the new directory now contains:

AVeryVeryLongName.TXT(AVERYV~1.TXT)

Next, Acronis Files Connect attempts to copy the file "AVERYV~1.TXT" to the new location. However, when it tries to copy the file using the short name (since that is what the Macintosh told it to use), the resulting name already exists! Consequently, the Macintosh client gets an error.

The only complete work around for this problem is to try to limit your file names to 31 characters, or upgrade to Acronis Files Connect 3.0 and use Mac OS X as a client, since both support file names longer than 31 characters.

 

Tags: 

You are reporting a typo in the following text:
Simply click the "Send typo report" button to complete the report. You can also include a comment.
CAPTCHA
This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.
14 + 5 =
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.