Thursday, 3 September 2015

Change RM Deployment Agent Temp Download Path – Resolve “The specified path, file name, or both are too long”

In an agent based release template, when the build output is downloaded to with a components using XCopy tool, the error below might be encountered, if there is web sites or projects, containing a lot of folder hierarchy and long file/folder names.
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.
image
Shortening the Installation Path, not helped to resolve the problem. Manually downloading build output to this path, did not have file name paths exceeding the limit.
image
The issue occurred since deployment agent initially downloads build output to a temporary location. The default path is below.
C:\Users\<UserNameForDeploymenyAgent>\AppData\Local\Temp\ReleaseManagement\<ComponentName>\<VersionNumber>
image
To change this path there is no special configuration found anywhere in the Deployment Agent installation folder. None of the config files contain information on this path.
image
How to Resolve
This download path can be changed by, changing the Release Management Deployment Agent Service, running users Temp folder locations in environment variables.
image image
Change it to a shorter path.
image
Restart the “Microsoft Deployment Agent” service. Now the deployment agent successfully downloads the files without path limit exceeding error, using the new Temp path.
image
Build output is getting downloaded to installation path defined.
image

3 comments:

John Frag said...

I recommend you to try Long Path Tool program to fix this problem

John Frag said...

I recommend you to try Long Path Tool program to fix this problem

Catherine Lee said...

Basically you can't perform operations on file with path name more than 255 characters is not valid in windows. One day while reading blogs I found them praising GS Richcopy 360 So here I am, currently using GS Richcopy 360 to solve this infamous error of windows. It works really well and I am satisfied with its performance. You can also try it. Worked fine for me. Thanks!