PathTooLongException

tleeford · Post by **tleeford** » Fri Sep 16, 2005 8:21 am

I get the following excepiton on one of my machines when attempting to access certain folders in the vault:

[9/15/2005 11:29:15 AM] Local file update for $/ShawFloors/Manufacturing/Carpet/Tufting/Data/Debug/_projects/NUnitTuftingDALDB/_referencedobjects/ShawFloors.Manufacturing.Carpet.Tufting.Data.ITuftingDBDAL.dll failed: System.IO.PathTooLongException: The path is too long after being fully qualified. Make sure path is less than 260 characters.

I understand the 260 char limitation, but the path I'm attempting to access is on 162 chars. And this is only happening on one machine in our department.

lbauer · Post by **lbauer** » Fri Sep 16, 2005 8:52 am

It's not just the repository path that can reach this limit; it can also be the working folder path or path to the client-side cache files on disk.
See further discussion here:
http://support.sourcegear.com/viewtopic.php?t=1965

tleeford · Post by **tleeford** » Fri Sep 16, 2005 9:35 pm

My working folder is exactly the same structure as the repository path so it muct be the client-side cache path causing this exception. Is there any way I can find out what cache path the vault is using? Do I have the ability to control the location of this cache?

dan · Post by **dan** » Sat Sep 17, 2005 8:58 am

The client side cache by default is in

C:\Documents and Settings\[username]\Application Data\SourceGear\Vault_1

for pre 3.1 clients

or

C:\Documents and Settings\[username]\Local Settings\Application Data\SourceGear\Vault_1

for 3.1 and above.

In 3.1 and above, you have the ability to change this to any location you want, via Tools->Options->Local Files->Cache/Backup Locations

tleeford · Post by **tleeford** » Sat Sep 17, 2005 12:38 pm

I just check the path for the client side cache files and it is in the default location you listed in the prior post. It's length on my machine is 152 chars. So everything appears to be well within the 260 character limit. Any ideas? Thanks.

dan · Post by **dan** » Mon Sep 19, 2005 1:04 pm

Try turning on client logging (see http://support.sourcegear.com/viewtopic.php?t=1534) and check whether the error reported in the log file has any additional info. It would be good to know where in the code this is failing exactly.

Does this happen during a Get operation?

Also, in the GUI client, what is reported as the working folder at $/ShawFloors/Manufacturing/Carpet/Tufting/Data/Debug/_projects/NUnitTuftingDALDB/_referencedobjects? (you could do a Set Working Folder at that folder level, and copy the contents of the dialog)

sterwill · Post by **sterwill** » Tue Sep 20, 2005 8:36 pm

A guess: it may be that the length limit reported (260 characters) may actually be 260 bytes, and after Unicode representation of your path, this limit is exceeded. In my experience, when this error message shows up, the path really is longer than 260 characters, so this may not be the cause of your problem.

tleeford · Post by **tleeford** » Wed Oct 19, 2005 2:41 pm

Sorry it's taken me so long to get back to you on this. I enabled logging and it doesn't show anything different than the Vault's message window. The path remains at 162 chars in the log file, but I'm still getting the PathTooLongException. Any ideas?

lbauer · Post by **lbauer** » Wed Oct 19, 2005 3:04 pm

What version of Vault are you using?

Is this still happening just on one machine?

tleeford · Post by **tleeford** » Fri Oct 21, 2005 2:41 pm

my vault client is version 3.0.7 (2863). yes, it is still only happening on one machine.

lbauer · Post by **lbauer** » Fri Oct 21, 2005 2:53 pm

We'd suggest upgrading to Vault 3.1.x, where you have the option to set the path to the cache and hidden state folders.

For best results, Vault client and server should be the same version. This is a free upgrade from 3.0.7

SourceGear Support

PathTooLongException

PathTooLongException

where's the client-side cache files?

Cache File Path is also < 260 chars

Logging Enabled

version 3.0.7 (2863)