TDS error: The specified path, file name, or both are too long.

Versions:

TDS 5.1.0.3

Team Development for Sitecore ((TDS) from Hedgehog Development

Visual Studio 2013

Sitecore 6.6 (rev 131211)

Issue:

TDS issue with long file names  or paths:

An exception occurred while updating the sitecore item …

The specified path, file name, or both are too long.  The fully qualified file name must be laess than 260 characters, and the directory name must be less than 248 characters.

Resolution

A recommended work-around for this issue is File System Aliasing.  In my case, even with aliases the names were still too long even with aliasing all folders above.  In addition, TDS would hang after I set the File System Alias and it moving the files which resulted in getting part of the alias done, but not all of it, so it created a corrupted TDS project.  To fix the TDS project, see (TDS Issue: Value cannot be null).

In the end, it’s safest to avoid long file names (including the paths – avoid deep nesting).

The File System Aliasing option is described well here:

http://sitecorejourney.nileshthakkar.in/2014/02/are-you-facing-pathtoolongexception.html

File System Aliasing with Team Development for Sitecore

With the newest version of Team Development for Sitecore you no longer are limited to the file systems path length. File System Aliasing in TDS 3.0 allows you to rename long file path names to something shorter and easier to manage without affecting how the name appears in Sitecore or Visual Studio.

From <http://www.hhogdev.com/products/team-development-for-sitecore/videos.aspx>

TDSLongFileNames2

 TDSLongFileNames1

Advertisements

8 Responses to “TDS error: The specified path, file name, or both are too long.”

  1. TDS Error in Visual Studio: Value cannot be null. Parameter name: path1 | Horizontal Integration Says:

    […] The easy option would be to add the missing files on disk (and to your source archive) that the TDS project is listing in the Visual Studio Output Window / Team Development for Sitecore output.  In my case, the issue of missing files came along because TDS complained of file names being too long so instead of adding the missing files, I had to remove references to the files from the TDS project manually.  The initial issue I was facing was that sitecore item file names were too long when trying to “Get Sitecore items” and I tried the recommended option to use file system aliasing but ran into issues with that option described in TDS error:   The specified path, file name, or both are too long.. […]

  2. Andrewop Says:

    The easy option is being provided here try to use long path tool to solve your problem.

  3. Antuan Says:

    Hi, maybe You should try Long Path Tool?

  4. gamick lisafisher Says:

    I had this problem too before. I think the file is really too long to download. I read some articles and used Long Path Tool. I was happy because it worked.

  5. oxishmit Says:

    Never mind – Long Path Tool could be the answer to your problem.

  6. Ronald Says:

    it’s a great tool indeed the Long Path Tool It helped me out greatly.

  7. aiden carter (@aidencarter16) Says:

    The Long path tool is the very best program for error, unlock solution.
    Try it and solved your problem.
    I used the long path tool and I solved my error, unlocks problem solution.

  8. aiden carter Says:

    The Long path tool is the very best program for error, unlock solution.
    Try it and solved your problem.
    I used the long path tool and I solved my error, unlocks problem solution.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: