• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Error Message: "Cannot Copy File: Path is too deep"

Status
Not open for further replies.

lorinser75

Golden Member
Hey guys,
I need some assistance,
Does anybody know what is causing this message to appear
"Cannot Copy File: Path is too deep"

I'm trying to transfer a file from 1 PC to another across the network.
Both machine are loaded with Win2k Pro. It was working fine for a while (transfer freely no problem), and this issue suddenly pop up. I check all "permission" and everything checked out.
Another problem is for some weird reason, whenever I tried to send e-mail with attachments, It is always a failure - server is not responding..blah..blah, but without attachment, it went in a few seconds. This is via DSL line that is connected to a router.
Could this be hardware issue or windows issue?

I really appreciate any help. Thanks
 
The path + filename is too big, try to rename the file and the paths, and after you finished copying, rename them back.
 
Use robocopy. It supports 65535 char paths. It comes on anything XP and newer and can be downloaded right off MS's website for older OS's.

Code:
robocopy \\2kmachine\c$\somepath c:\newfolder\ *.* /s /e
 
Use robocopy. It supports 65535 char paths. It comes on anything XP and newer and can be downloaded right off MS's website for older OS's.

Code:
robocopy \\2kmachine\c$\somepath c:\newfolder\ *.* /s /e

Be careful with this. Robocopy may support it, but the OS does not.

You've got I think 256 characters for the *entire* path and name of the file. I remember in the good old Kazaa days accidentally downloading a file with a bunch of junk letters and numbers as the name on a WinXP system. The OS wouldn't even let me delete it, I had to boot onto a linux livecd to get rid of the damn thing.

Edit: and we all got suckered by a necro thread from 2005. 😛
 
You can also get around it by going to a command prompt and doing the following:
set sname1 = "C:\some\really\obnoxios\long\path"
set sname2 ="C:\some\equally\obnoxios\long\path"
copy sname1\file.name sname2\file.name
 
Be careful with this. Robocopy may support it, but the OS does not.

You've got I think 256 characters for the *entire* path and name of the file. I remember in the good old Kazaa days accidentally downloading a file with a bunch of junk letters and numbers as the name on a WinXP system. The OS wouldn't even let me delete it, I had to boot onto a linux livecd to get rid of the damn thing.

Edit: and we all got suckered by a necro thread from 2005. 😛

Yeah suckered ; ; However to correct, Windows 2000 NTFS supported a path length of 32767 characters. You could have deleted a file with that long of a name via cmd.exe (not command.com) or via the \\?\ method.

Just finished our XP migration 12 months ago and there was plenty of XP / 2003 systems with ~1000+ character path depths.
 
Status
Not open for further replies.
Back
Top