SVN login fails after moving Fisheye to another machine

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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

Problem

After moving Fisheye to another machine, SVN repository fail to login to the Subversion server.

The following appears in the atlassian-fisheye-<date>.log:

1 2 3 4 5 6 7 8 9 10 11 12 2013-08-06 10:19:47,542 WARN [SvnExecution3 REPO] fisheye SvnPasswordSupplier-prompt - SVN is requesting password too often for realm '<https://subversion.server.com:443>' and user 'testuser' 2013-08-06 10:19:47,542 ERROR [InitialPinger3 REPO] fisheye BaseRepositoryScanner-handleSlurpException - Problem processing revisions from repo REPO due to class com.cenqua.fisheye.rep.RepositoryClientException - org.tigris.subversion.javahl.ClientException: svn: E200015: authentication cancelled com.cenqua.fisheye.rep.RepositoryClientException: org.tigris.subversion.javahl.ClientException: svn: E200015: authentication cancelled at com.cenqua.fisheye.svn.SvnThrottledClient.executeNoThrottle(SvnThrottledClient.java:163) at com.cenqua.fisheye.svn.SvnThrottledClient.execute(SvnThrottledClient.java:132) at com.cenqua.fisheye.svn.SvnThrottledClient.info2(SvnThrottledClient.java:99) at com.atlassian.fisheye.svn.Svn2RepositoryClient.getLatestRevision(Svn2RepositoryClient.java:90) at com.atlassian.fisheye.svn.Svn2Scanner.doChangesetPump(Svn2Scanner.java:248) at com.atlassian.fisheye.svn.Svn2Scanner.slurpRepository(Svn2Scanner.java:202) at com.atlassian.fisheye.svn.Svn2Scanner.doSlurpTransaction(Svn2Scanner.java:177) at com.cenqua.fisheye.rep.BaseRepositoryScanner.ping(BaseRepositoryScanner.java:85) at com.cenqua.fisheye.rep.BaseRepositoryEngine.doSlurp(BaseRepositoryEngine.java:92)

Cause

Cause #1 - multiple repositories using different credentials

See the following page: SVN Authentication Issues

Cause #2 - Windows Authentication

The Subversion server is setup to allow Windows Authentication only but Fisheye is trying to use Basic Authentication.

Resolution

Resolution for Cause #1

Refer to the options on the following page: SVN Authentication Issues

Resolution for Cause #2

Configure Subversion server to allow Basic Authentication.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.