C:\Program Files\Microsoft Web Deploy>msdeploy.exe -verb:sync -source:webServer60 -dest:archivedir=d:\msdeploy -verboseLevel:Informational > msdeploy.log
gives the error -
Fatal: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
I don't know if this has been addressed before, but if a path\filename are too long the entire operation will fail. this seems like a pretty tight limitation and i would imagine it could be easily fixed. are there plans to increase this length limitation
in future versions? or is there a way to just skip the files in question and continue the operation?
Thanks for reporting this issue. File path length limitation is enforced by the file system and not by msdeploy but I will follow up in the team to see what can we do to get around this limitation. If you want to skip sync/migrate of few files, you can either
create a skip rule in the microsoft.web.deployment.config (see SkipUNC rule for an example of skip rule) or you can add -skip switch on the commandline. Here is how skipping a file rule can be added on the command line (absolutepath is a regular expression).
Thanks for reporting this issue. File path length limitation is enforced by the file system and not by msdeploy but I will follow up in the team to see what can we do to get around this limitation. If you want to skip sync/migrate of few files, you can either
create a skip rule in the microsoft.web.deployment.config (see SkipUNC rule for an example of skip rule) or you can add -skip switch on the commandline. Here is how skipping a file rule can be added on the command line (absolutepath is a regular expression).
l_g
2 Posts
Filename length limitation
Feb 08, 2008 02:34 PM|LINK
C:\Program Files\Microsoft Web Deploy>msdeploy.exe -verb:sync -source:webServer60 -dest:archivedir=d:\msdeploy -verboseLevel:Informational > msdeploy.log
gives the error -
Fatal: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
I don't know if this has been addressed before, but if a path\filename are too long the entire operation will fail. this seems like a pretty tight limitation and i would imagine it could be easily fixed. are there plans to increase this length limitation in future versions? or is there a way to just skip the files in question and continue the operation?
ksingla
1138 Posts
Microsoft
Re: Filename length limitation
Feb 08, 2008 02:55 PM|LINK
Hi l_g,
Thanks for reporting this issue. File path length limitation is enforced by the file system and not by msdeploy but I will follow up in the team to see what can we do to get around this limitation. If you want to skip sync/migrate of few files, you can either create a skip rule in the microsoft.web.deployment.config (see SkipUNC rule for an example of skip rule) or you can add -skip switch on the commandline. Here is how skipping a file rule can be added on the command line (absolutepath is a regular expression).
-skip:objectName=filePath,absolutePath=\w+longfilenamepart\w+
You can add multiple -skip switches to add multiple skip rules. Let us know if you have trouble getting this to work.
Thanks,
Kanwal
l_g
2 Posts
Re: Filename length limitation
Feb 08, 2008 03:02 PM|LINK
Thanks a lot for the quick response and the information - I will work with it