Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


How to create a new Repository in VisualSVN?



VisualSVN Server version 3.5.1

FishEye version 4.3.1

Please describe how to add a repository.

Below is the VisualSVN Server repository. IDEAIC Repository.

 VisualSVN 1.png


VisualSVN 2.PNGVisualSVN 3.PNGVisualSVN 4.PNGVisualSVN 5.PNGVisualSVN 6.PNG

What's wrong?

Waiting for help.

Thank You.






1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 31, 2018

Hi Alex,

There is a knowledge base titled Unable to get info for the repository root that I would start with:

Cause #1 - unexpected trailing slash

A trailing slash has been added incorrectly to the SVN URL during the configuration of the repository. For example: https://svn.your.server/svn/project/

Cause #2 - missing execute permissions on jsvn command

Unless the native client is used, FishEye uses the jsvn command to perform SVN command which can be found in the <FishEye installation directory>/lib/svn folder.

If the user running FishEye does not have execute permissions on the jsvn command, FishEye will not be able to connect to the repository.

Resolution #1 - unexpected trailing slash

Remove the trailing slash from the SVN URL and save. For example (considering the example above): https://svn.your.server/svn/project

Resolution #2 - missing execute permissions on jsvn command

Add the execute permissions on the jsvn command.

If that does not work, when logged in as the user which is used to run FishEye, see if you can connect to the svn repository using a command similar to the following:

svn info

I would also try pinging the SVN server to see what you get back.  If you use Wireshark you can also reproduce the issue, run a tcpdump after the connection fails and see what the packet trace tells you.

Let me know what you find and we'll go from there.



Hi Branden.

I sincerely appreciate your help.

But the equipment that installed FishEye is not here right now.

It is scheduled to visit next Tuesday.

Then I will test and answer.

Thank you.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events