MAX_PATH error on SVN checkout

Subscribe to MAX_PATH error on SVN checkout 4 posts, 2 voices

 
Avatar MichaelBrocious 5 posts

I’m now receiving the error below from Koders on our SVN repo. I assume this means that our directory structure is nested too deeply. Any way around this, or other thoughts?

Thanks.

Mike

09/14/2007 18:39 Checkout failed because path is above MAX_PATH limit:

C:\Program Files\Koders\Pro\FileStore\SourceFileCache\JDI All (subversion)\GPA\trunk\CPA_Pt_Mgmt\CPA_Pt_Mgmt\app\mit-fr\srctest-fitnesse\ files\xmlfiles\com\siemens\soarian\se\pt\fixturehelpers\.svn\t

 
Avatar BenMcDonald 44 posts

Hey Mike,

This is caused by a limit in the windows path limit (http://www.codinghorror.com/blog/archives/000729.html).

One way to get around this is to shorten the path as much as possible. To do that you can move our “FileStore” location to a shorter path such as “C:\FS”

  1. Create a directory directly under c:\ called “FS” (short for FileStore)
  2. Open Kodebot (All Programs > Koders > Pro Edition > Pro Setup), and stop the Web Service and Indexing Service
  3. Close Kodebot
  4. Copy the contents of “C:\Program Files\Koders\Pro\FileStore” to “C:\FS” (the MasterIndexCache, ProjectIndexCache, and SourceFileCache)
  5. Change the following line in “C:\Program Files\Koders\Pro\Configuration\KodeShare.config”

<liveindexpath>C:\Program Files\Koders\Pro\FileStore\MasterIndexCache\Index.8\</liveindexpath>

<filestore>..\FileStore\</filestore>

to

<liveindexpath>C:\FS\MasterIndexCache\Index.8\</liveindexpath>

<filestore>C:\FS\</filestore>

The final two steps are:
  1. Delete the “C:\Program Files\Koders\Pro\FileStore” directory
  2. Open Kodebot and start the Web Service and Indexing Service
 
Avatar MichaelBrocious 5 posts

Thanks, Ben. I did those steps and that shortened the path, but it still turns out to be just a little too long for some of our directories. So I’ve switched to using the file system adapter and a scheduled batch file to update the code periodically.

 
Avatar BenMcDonald 44 posts

Glad that you got it to work. We are working on a fix for this which involves keeping all paths in Unicode, and will let you know when it is deployed.