Access denied to repository for which user has access
Moderator: SourceGear
Access denied to repository for which user has access
I have a user who has been trying to get into a particular repository and keeps getting the message that she has no rights to access the repository, but in fact she does. She has been using the repository just fine for months, then all of a sudden, she was denied access.
I checked the security settings through the admin page and it shows she has access. To be sure, I revoked her access and then added it back. No change. She still has access to other repositories, it's just one that is keeping her out.
I have also noticed that I can access the repository using her vault login if I am signed in to the network using my network login. I can also access the repository if I use my vault login on her computer. It's just the combination of her network login and her vault login that doesn't work.
I have recently upgraded the server and clients to the latest version (4.1) and I have uninstalled and reinstalled her vault client application.
Any suggestions?
I checked the security settings through the admin page and it shows she has access. To be sure, I revoked her access and then added it back. No change. She still has access to other repositories, it's just one that is keeping her out.
I have also noticed that I can access the repository using her vault login if I am signed in to the network using my network login. I can also access the repository if I use my vault login on her computer. It's just the combination of her network login and her vault login that doesn't work.
I have recently upgraded the server and clients to the latest version (4.1) and I have uninstalled and reinstalled her vault client application.
Any suggestions?
What is the exact error message this user is getting?
Can she connect if you change her account to use Vault authentication rather than AD authentication?
Could you send me a copy of the Vault Server log that covers the time period of her unsuccessful login? Email it to support@sourcegear.com ATTN: Linda
Can she connect if you change her account to use Vault authentication rather than AD authentication?
Could you send me a copy of the Vault Server log that covers the time period of her unsuccessful login? Email it to support@sourcegear.com ATTN: Linda
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
What is the exact error message this user is getting?
Can she connect if you change her account to use Vault authentication rather than AD authentication?
Could you send me a copy of the Vault Server log that covers the time period of her unsuccessful login? Email it to support@sourcegear.com ATTN: Linda
Can she connect if you change her account to use Vault authentication rather than AD authentication?
Could you send me a copy of the Vault Server log that covers the time period of her unsuccessful login? Email it to support@sourcegear.com ATTN: Linda
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
What is the exact error message this user is getting?
Can she connect if you change her account to use Vault authentication rather than AD authentication?
Could you send me a copy of the Vault Server log that covers the time period of her unsuccessful login? Email it to support@sourcegear.com ATTN: Linda
Can she connect if you change her account to use Vault authentication rather than AD authentication?
Could you send me a copy of the Vault Server log that covers the time period of her unsuccessful login? Email it to support@sourcegear.com ATTN: Linda
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Count Me In...
Upgraded to 4.1.016216 this past weekend. no users have had problems until today a user contacted me with a problem accessing a specific respository. folder security is disabled on the repository and he was given "Access" rights as part of a group. other users have had no issues. he stated there were no issues earlier this week when he upgraded the vault client.
i tried removing permissions and re-adding them to no avail. i made him a global admin and he continued to have problems.
he is able to access use the web client with no problems. the log file does not show any information beyond login and logout. i have attached the relevant portions of the iis log and sgvault log.
the error message is "You have no rights to view any items in this repository."
i tried removing permissions and re-adding them to no avail. i made him a global admin and he continued to have problems.
he is able to access use the web client with no problems. the log file does not show any information beyond login and logout. i have attached the relevant portions of the iis log and sgvault log.
the error message is "You have no rights to view any items in this repository."
- Attachments
-
- sgvaultlog.txt
- sgvault log
- (81 Bytes) Downloaded 211 times
-
- iislog.txt
- iis log
- (2.55 KiB) Downloaded 218 times
-
- error message
- image001.jpg (7.83 KiB) Viewed 6280 times
This could be a cache issue. You could clear out your Client Side Cache. You will want to keep the cachemember_workingfolderassignments though.
EDIT:
What will be better here is if any user who runs into this, please start up Client Side Logging, reproduce the scenario, then send us the client log along with the Vault Server Log. Send that to support at sourcegear.com with a link to this thread. We will help you through this. Also, the additional information will help us see if we can't prevent this from happening in the first place.
EDIT:
What will be better here is if any user who runs into this, please start up Client Side Logging, reproduce the scenario, then send us the client log along with the Vault Server Log. Send that to support at sourcegear.com with a link to this thread. We will help you through this. Also, the additional information will help us see if we can't prevent this from happening in the first place.
Last edited by Beth on Wed May 21, 2008 8:43 am, edited 1 time in total.
I just had the same issue. It was very frustrating to have Vault just all of a sudden think a user does not have access.
Clearing the cache worked, but many changes had renames\moves\deletions had been made that vault has now forgotten about and we have to track down.
Just thought you should know its not an isolated issue, and is something that needs fixed.
Brian
Clearing the cache worked, but many changes had renames\moves\deletions had been made that vault has now forgotten about and we have to track down.
Just thought you should know its not an isolated issue, and is something that needs fixed.
Brian
-
- Posts: 34
- Joined: Wed Sep 12, 2007 8:17 pm
FYI - I just experienced exactly the same error message with Vault Client 41.1.18060. I was also experiencing numerous issues with VS.Net 2008 - inability to commit checkins and inability to connect to the Vault server after closing and reopening VS.
Clearing out the client cache fixed the problem, and I was able to straighten out the checked-out file situation in VS.net within a minute or two.
I'd like to suggest two things:
1) Post this solution somewhere as a sticky top-level note in the forum (maybe you've already done that and I just haven't found it)
2) It would be very helpful if you could list the corresponding GUID for each repository in the Repository section of the Vault admin console. I connect to three different repositories from my workstation and it took some digging around before I was finally able to figure out which repository cache was the one I needed to clear out.
Clearing out the client cache fixed the problem, and I was able to straighten out the checked-out file situation in VS.net within a minute or two.
I'd like to suggest two things:
1) Post this solution somewhere as a sticky top-level note in the forum (maybe you've already done that and I just haven't found it)
2) It would be very helpful if you could list the corresponding GUID for each repository in the Repository section of the Vault admin console. I connect to three different repositories from my workstation and it took some digging around before I was finally able to figure out which repository cache was the one I needed to clear out.
What will be better here is if any user who runs into this, please start up Client Side Logging, reproduce the scenario, then send us the client log along with the Vault Server Log. Send that to support at sourcegear.com with a link to this thread. We will help you through this. Also, the additional information will help us see if we can't prevent this from happening in the first place.