Solved

destination does not support long file names

Posted on 2004-09-30
11
5,917 Views
Last Modified: 2011-08-29
I get the above error message when I copy a Word document from the network drive and then paste it to another directory on the same network drive.

The name is "Squadon Directory.doc"  

it also happens on other similar names with other extensions like Excel.

The server is NT2000

Copy..pasting the file from the harddrive to the same harddrive works no problem.

Can anyone help? Thanks.

0
Comment
Question by:NeerDeth
  • 4
  • 2
  • 2
  • +3
11 Comments
 
LVL 2

Expert Comment

by:dev8
ID: 12193601
Hello,

Is this just happening with the Word documents and Excel documents?  What is the filesystem in use?  
0
 
LVL 9

Expert Comment

by:tosh9iii
ID: 12193659
maybe the folder name is too long

Can you give us the entire path (address) of the file, you know like:  C:\document and settings\folder name\squadron directory.doc

Is it the same for all of the documents, or only that one?
0
 

Author Comment

by:NeerDeth
ID: 12194216
yes, the folder names are very long, quite often over 100 char longs and 4+ directories deep
but not all people have trouble copying files to these folders

0
Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

 

Author Comment

by:NeerDeth
ID: 12194240
i'm told that it's file system 'posix'
but I've never heard of that, so I'm not sure
0
 

Author Comment

by:NeerDeth
ID: 12194341
scratch the posix
0
 
LVL 9

Expert Comment

by:tosh9iii
ID: 12210493
Is renaming those folders with a shorter name a possibility?
0
 

Author Comment

by:NeerDeth
ID: 12210619
no
0
 
LVL 12

Accepted Solution

by:
alandc earned 500 total points
ID: 12312087
I have encountered the same and similar errors before.  (and tosh9iii is very close to the correct answer.)  What will work is taking spaces OUT of the directory name -or- the file name.  It will probably work okay if either of them have spaces but NOT BOTH.  Strange but true.  In most cases I advise folks to keep long file names and scratch long directory names using anacronyms instead like PWC\planning\teams or AFG\financial\committee.

This become expecially important the longer the paths get because the entire length cannot be over 256 characters. This may be the limit you have run into. In this case you might get away with a few longer directory names but will need to shorten some of them. Your directory structure is probably NTFS (instead of POSIX):

http://www.burnthacker.com/archives/000019.html
NTFS Maximum Path Name Length
"The maximum length of a path on Windows (at least from the command line) is 256 characters. "
What this means from a practical perspective is that if you have deep paths structured you'll run into stray messages like: "The system cannot find the path specified."

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/base/naming_a_file.asp
According to Microsoft that is supposed to be extended to "32,767 characters, composed of components up to 255 characters in length" using Unicode functions however I would expect that most functions still use Windows API where "the maximum length for a path is MAX_PATH, which is defined as 260 characters".

0
 
LVL 1

Expert Comment

by:CSSupport2007
ID: 22184899
I've seen this before a few times when copying a file to another folder.  The total character length was not close to the max.  After logging out and back in, the user I was supporting was able to copy the file into the folder that was giving the error previously.
0
 
LVL 1

Expert Comment

by:CSSupport2007
ID: 22184933
Also, check the mapping of the drive you're trying to save to.  The user I was supporting had lost his
0
 
LVL 1

Expert Comment

by:maynardinc
ID: 22306971
CSSupport2007....Your fix did work. It was weird, because the "Map Network Drives" showed that drive to be mapped, but "My Computer" did not, and the user was able to move files, but would get that error.
I went into Windows Explorer, Unmapped the drive using Tools - Disconnect Network Drive, then remapped, and the error went away.
0

Featured Post

The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

If you build your web application in Visual Studio you'll get at least a few binaries, or .DLL, files in your bin folder. However, there is more compiling to be done. Normally this would happen when an ASP.NET resource within the web site is request…
When you start your Windows 10 PC and got an "Operating system not found" error or just saw  "Auto repair for startup" or a blinking cursor with black screen. A loop for Auto repair will start but fix nothing.  You will be panic as there are no back…
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…
Email security requires an ever evolving service that stays up to date with counter-evolving threats. The Email Laundry perform Research and Development to ensure their email security service evolves faster than cyber criminals. We apply our Threat…

829 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question