You have no rights to view items in this repository

[AdrianLC]

We are getting an error when a specific user logs in with the Fortress client. Error comes in the form of a message box just after entering the login credentials. We are able to see all source code folder with the web based client. We are getting the error at least in two different computers.

Thanks for your help

I have extracted part of the sgvault.log for reference

----1/16/2008 3:54:28 PM JR--adrianl-mobile.corp.monavie.com(172.20.3.23)--SSL Disabled Logout
----1/16/2008 3:54:28 PM JR--adrianl-mobile.corp.monavie.com(172.20.3.23)--SSL Disabled Login
----1/16/2008 3:54:28 PM JR--adrianl-mobile.corp.monavie.com(172.20.3.23)--SSL Disabled System.NullReferenceException: Object reference not set to an instance of an object.
at VaultServiceSQL.VaultSqlSCC.GetLastTreeSecurityChange(VaultSqlConn conn, Int32 nRepID, Int32 nUserID, VaultDateTime& dtLastChange) at VaultServiceSQL.VaultSqlSCC.GetLastTreeSecurityChange(VaultSqlConn conn, Int32 nRepID, Int32 nUserID, VaultDateTime& dtLastChange)
----1/16/2008 3:54:28 PM JR--adrianl-mobile.corp.monavie.com(172.20.3.23)--SSL Disabled FailDBFault
----1/16/2008 3:54:28 PM JR--adrianl-mobile.corp.monavie.com(172.20.3.23)--SSL Disabled System.NullReferenceException: Object reference not set to an instance of an object.
at VaultServiceSQL.VaultSqlSCC.GetLastTreeSecurityChange(VaultSqlConn conn, Int32 nRepID, Int32 nUserID, VaultDateTime& dtLastChange) at VaultServiceSQL.VaultSqlSCC.GetLastTreeSecurityChange(VaultSqlConn conn, Int32 nRepID, Int32 nUserID, VaultDateTime& dtLastChange)
----1/16/2008 3:54:28 PM JR--adrianl-mobile.corp.monavie.com(172.20.3.23)--SSL Disabled FailDBFault

[AdrianLC]

I should add that we have this problem as a result of an upgrade from Vault/Dragnet to Fortress.

[lbauer]

The first thing I would suggest is to delete your client-side cache files and flush out the server cache. There may be info cached that's out of sync with the database.

http://support.sourcegear.com/viewtopic.php?t=6

I'd suggest renaming the Fortress_1 file and allow a new to be created.

So the steps would be:

Close any open clients.
Delete the client-side cache
Restart IIS, which restarts the Vault Server
Then open your client and re-connect.
You'll need to reset working directories.

[AdrianLC]

Thanks for the fast response...

After following the process described, I'm still unable to see the repository.

I can see it perfectly if I log in with another user.

What's next?

[lbauer]

Perhaps the database was not properly upgraded.

These queries will give us more information. Run these and let me know the results:

SELECT * FROM sgvault.dbo.tblschemaversions;


A) Get the repository id:
SELECT repid, name FROM sgvault.dbo.tblrepositories

B) get the id of the user who can't see the repository:
SELECT userid, login FROM sgmaster.dbo.users

C) Using the info from above what does the following return:

SELECT treelastsecuritychange FROM sgvault.dbo.tblusersecuritychanges
WHERE repid = RESULTS_FROM_A AND userid = RESULTS_FROM_B