SVN path not found: 404

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Symptoms

While indexing an SVN repository the following error can be seen in the atlassian-fisheye-YYYY-MM-DD.log files:

2013-03-15 10:09:40,094 DEBUG [SvnExecution4095 PRJ_PHOEBUS] fisheye SvnTask-run - Executing cat -r 21 http://svn.server/svn/src/main/java/file.java@21
2013-03-15 10:09:40,219 ERROR [btpool0-93 ] fisheye SvnCache-getBinaryRevision - Exception loading SVN content for /src/main/java/file.java@21
com.cenqua.fisheye.rep.RepositoryClientException: org.tigris.subversion.javahl.ClientException: svn: E160013: '/svn/2012/!svn/bc/21/src/main/java/file.java' path not found: 404 Not Found (http://svn.sever)
	at com.cenqua.fisheye.svn.SvnThrottledClient.executeNoThrottle(SvnThrottledClient.java:114)
	at com.cenqua.fisheye.svn.SvnThrottledClient.execute(SvnThrottledClient.java:93)
	at com.cenqua.fisheye.svn.SvnThrottledClient.streamFileContent(SvnThrottledClient.java:250)
	at com.cenqua.fisheye.svn.SvnCache.getBinaryRevision(SvnCache.java:397)
	at com.cenqua.fisheye.svn.SvnCache.getTextRevision(SvnCache.java:358)

Diagnosis

Check if the URL in the debug log points to the correct file path (e.g.: http://svn.server/svn/src/main/java/file.java@21 ) by running the following command from the command line:

jsvn --no-auth-cache --username USER --password PASS info -r 21 http://svn.server/svn/src/main/java/file.java 

You can find more information on how to use JSVN on the following page:

Cause

There are three possible causes for this error:

  1. The Fisheye/Crucible server does not have access to the file.
  2. The repository settings have been changed but a full reindex has not been performed, which causes the path to be incorrect.
  3. FE-5551 - SVN E160013 404 Not Found for paths with url decodable seqences

Resolution

For the causes mentioned above the resolutions are:

  1. Confirm that the user configured in the repository settings has permissions to access the file.

  2. Perform a full reindex under Administration > Repository Settings > Repositories > <Repository Name> > Maintenance > Repository Source Index > Re-index.
  3. See FE-5551 - SVN E160013 404 Not Found for paths with url decodable seqences for workarounds until it is fixed.

Last modified on Jan 27, 2025

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.