You have no rights to view any items in this repository

[jedrake]

That was the error message we experienced this morning.

Since then we have tried:

1. Clearing local cache.
2. Rebooting the web server.
3. Logging in from the Admin Console
4. Restoring a previous backup.
5. Reinstalling the application.

Server Version: 3.0.7.2863
Client Version: 3.0.7(2863)

The Server Log reads:

----12/2/2009 1:55:33 PM sgvaultsystem--()--
System Started
Version 3.0.7.2863
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\WINDOWS\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 102400
Overwrite Log on Startup = False
Session Timeout = 4320
Active Directory Domain =
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL = http://_IP_/VaultService
Identity = NT AUTHORITY\NETWORK SERVICE
----12/2/2009 1:56:01 PM USER_NAME--_CLIENT_(_IP_)--SSL Disabled Login
----12/2/2009 1:56:09 PM USER_NAME--_CLIENT_(_IP_)--SSL Disabled An error was encountered looking up the owner of a folder or file for the source code tree. The tree was not built. TreeRevision: 38280 TreeLevel: 5 ParentObjVerID: 451841 ObjID: 179961 ObjVersion: 1 Name: EnterpriseNonServicedLib.dll PinFrom: 0 ParentPathHash: 1862922124 PathHash: 0
----12/2/2009 1:56:09 PM USER_NAME--_CLIENT_(_IP_)--SSL Disabled Error in the application.
----12/2/2009 1:56:13 PM USER_NAME--_CLIENT_(_IP_)--SSL Disabled An error was encountered looking up the owner of a folder or file for the source code tree. The tree was not built. TreeRevision: 38280 TreeLevel: 5 ParentObjVerID: 451841 ObjID: 179961 ObjVersion: 1 Name: EnterpriseNonServicedLib.dll PinFrom: 0 ParentPathHash: 1862922124 PathHash: 0
----12/2/2009 1:56:14 PM USER_NAME--_CLIENT_(_IP_)--SSL Disabled Error in the application.
----12/2/2009 1:56:17 PM USER_NAME--_CLIENT_(_IP_)--SSL Disabled An error was encountered looking up the owner of a folder or file for the source code tree. The tree was not built. TreeRevision: 38280 TreeLevel: 5 ParentObjVerID: 451841 ObjID: 179961 ObjVersion: 1 Name: EnterpriseNonServicedLib.dll PinFrom: 0 ParentPathHash: 1862922124 PathHash: 0
----12/2/2009 1:56:39 PM USER_NAME--_CLIENT_(_IP_)--SSL Disabled Logout

[Beth]

Let's start first with reviewing your permissions. In your Vault admin tool, take a screenshot of the list that shows who has repository access. Then, go to your folder security tab and check to see if the person has any rights. Can you show me a screenshot that shows the user having rights to something in that repository?

If you post the screenshots here, you will be able to delete them later. If you prefer to email them, then send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread.

[jedrake]

I have attached a screen shot showing the permissions.

My apologies for not mentioning that I checked that earlier.

[jedrake]

Okay,

We upgraded to 3.5. This appears to have resolved the issue. The admin account can access the repository and some of our developers will be attempting to connect shortly.

[jedrake]

We were able to successfully connect to the repository and check in outstanding files. We did have some licensing issue that need to be resolved but the upgrade from 3.0 to 3.5 resolved the underlying issue.

You can consider this a closed issue for us at this time.

I do recommend, however, that Source Gear get all the documentation, and multiple possible solutions to this particular item into a single post. That should include:

1. The description of the problem.
2. Which versions it is KNOWN to occur in.
2. When it may occur.
3. All possible solutions currently discussed on these forums.

Another poster had already suggested this step to you. Unfortunately, after the numerous message threads that end in off-board email discussions, this one issue significantly lowered my personal confidence in the Vault product. An entire 5 year history and two past choices to stick with this product over the evaluations of countless others was very nearly wiped out due to the lack of a single kb/fourm post of the above nature. Even if 5.0 has resolved this issue for all time, others continue to follow in their own searching and they may not make the same decision.

[jedrake]

4. Plus any that may be more generally applicable from the numerous private email discussions.

[Beth]

I can put in a feature request for the kind of responses you want. It would take some time though to find every issue and every possible answer to it. What it sounds like is that you want one troubleshooting guide with all the possibilities in it. Does that sound correct?

Currently, we have KB articles for some of the common things we run into. An index of those is found here: http://support.sourcegear.com/viewtopic.php?f=13&t=792.

[jedrake]

Not every issue, just this one.

I personally found what are likely the majority of them just by searching here on the board for the error text.

The problem as a customer is that there are 29 different postings about this issue, many of them ending in "Send us an email" and not in any sort of resolution that a customer can make use of, or even a note that a resolution occurred. Additionally there are numerous me too, and related issues, each with its own "I tried" X or Y or Z, but no where is there a listing of step 1., 2., 3. So I had to read through all 29 and try every suggestion in isolation, where in several instances it would have been much easier for me if I had tried suggestion X before moving to suggestion Y.

Reading the posts I got the distinct impression that the issue 1. Had existed for a long time. 2. Occurred in most versions of Vault. 3. Had never been successfully addressed at the root. It feels like to me that a KB article on the message would be an appropriate response.

Thank you.