Comments on: Long Path Error While Copying/Moving Data

By: TomLiotta

TomLiotta — Wed, 03 Apr 2013 00:17:57 +0000

Why buy a tool when it’s easier to resolve the problem with what comes with the system and the resolution has the support of the system vendor? — Tom

By: tool

tool — Tue, 02 Apr 2013 03:19:30 +0000

This tool solved my problem, its easy. try to google this tool “Long Path Tool” or you can download it in longpathtool.com..

By: prince123456789

prince123456789 — Tue, 09 Nov 2010 15:20:57 +0000

hello prashant ! you need not to worry about because i got a solution for ur problem. now u can easily move your data where ever you want

By: jzcutler

jzcutler — Fri, 21 Jul 2006 13:46:44 +0000

Try using the UNC names of the paths (ServerNameShareName…). If that doesn’t work, try putting ? in front of the server name in the UNC path. Try a Google on “long short path UNC” to find free utilities to convert long path names to short path names. If you’re in VB, look on MSDN for the function that will do this for you in your code. The same search terms might get you there…

By: bvwatson

bvwatson — Fri, 21 Jul 2006 07:57:10 +0000

Windows has the SUBST command which is used to map a virtual drive letter to a long path name. I don’t know if this will work for you, but you can try it on the server.

The syntax from the command prompt is:

subst drive: path

For example:
subst V: “C:Documents and SettingsMyLogonIDStart MenuProgramsAdministrative Tools”

After this command, drive V: will reference the Administrative Tools subdirectory.

This may solve your long path name. I’ve used this in the distant past (Windows 3.1) but not recently.

bryan

By: cruzincooper

cruzincooper — Thu, 20 Jul 2006 10:34:15 +0000

Microsoft has a free tool call File Server Migration Wizard its a great tool for copying share drives, etc. It won’t solve the problem of the long file paths, however, it will give you a report of long file paths. We perhaps will use this tool to consolidate our servers.