Copy rights fails and Group security not working on new user
Moderator: SourceGear
-
- Posts: 18
- Joined: Thu Jan 15, 2004 12:56 pm
Copy rights fails and Group security not working on new user
I created a new user and I went to copy the rights from another user to this user. I select the user and click 'Copy Rights' button, then I select the user to copy rights from and click 'Copy'. I then get an error message.
1100: FailDBFault
So, I manually edit the new user and add it to the group of the other user I was going to copy the rights from. Well, when I log in with the new user I get the following message.
You do not have the permission to perform the operation.
The new user is part of the same group as other users. I don't even appear to be able to set the user permissions explictly on the user.
All of my current users are working fine, but I cannot get this new user added and working.
Brad
1100: FailDBFault
So, I manually edit the new user and add it to the group of the other user I was going to copy the rights from. Well, when I log in with the new user I get the following message.
You do not have the permission to perform the operation.
The new user is part of the same group as other users. I don't even appear to be able to set the user permissions explictly on the user.
All of my current users are working fine, but I cannot get this new user added and working.
Brad
Brad W. Young
DevSource LLC
DevSource LLC
What version of Vault are you using?
Is that user denied access to any repositories?
To check this select that user from the users tab and choose Security Rights and make sure that all the repositories are selected that the user should have access to. You can also edit the list of users denied repository access from the Repository Properties dialog.
I was able to reproduce an 1100 error when I tried to copy rights from a user who had repository access to a user who did not (we should probably give a more informative error message in that case).
Is that user denied access to any repositories?
To check this select that user from the users tab and choose Security Rights and make sure that all the repositories are selected that the user should have access to. You can also edit the list of users denied repository access from the Repository Properties dialog.
I was able to reproduce an 1100 error when I tried to copy rights from a user who had repository access to a user who did not (we should probably give a more informative error message in that case).
Mary Jo Skrobul
SourceGear
SourceGear
Does the Vault server log file give any hints as to the reason for the faildbfault?
-
- Posts: 18
- Joined: Thu Jan 15, 2004 12:56 pm
We are running version 2.0.6
We only have one repository and the new user does have rights to it.
This is from the log file.
---9/30/2004 8:13:33 AM brad.young--dev-youngb-nb.dev-source.net(192.168.90.103)--SSL Enabled
Cannot insert the value NULL into column 'repid', table 'sgvault.dbo.tblsecurityassignments'; column does not allow nulls. INSERT fails.
The statement has been terminated.
----9/30/2004 8:17:11 AM testuser--dev-youngb-nb.dev-source.net(192.168.90.103)--SSL Enabled
Logout
----9/30/2004 8:17:12 AM testuser--dev-youngb-nb.dev-source.net(192.168.90.103)--SSL Enabled
Login
----9/30/2004 8:17:12 AM testuser--dev-youngb-nb.dev-source.net(192.168.90.103)--SSL Enabled
GetRepositoryStructure returned: FailPermissionDenied
We only have one repository and the new user does have rights to it.
This is from the log file.
---9/30/2004 8:13:33 AM brad.young--dev-youngb-nb.dev-source.net(192.168.90.103)--SSL Enabled
Cannot insert the value NULL into column 'repid', table 'sgvault.dbo.tblsecurityassignments'; column does not allow nulls. INSERT fails.
The statement has been terminated.
----9/30/2004 8:17:11 AM testuser--dev-youngb-nb.dev-source.net(192.168.90.103)--SSL Enabled
Logout
----9/30/2004 8:17:12 AM testuser--dev-youngb-nb.dev-source.net(192.168.90.103)--SSL Enabled
Login
----9/30/2004 8:17:12 AM testuser--dev-youngb-nb.dev-source.net(192.168.90.103)--SSL Enabled
GetRepositoryStructure returned: FailPermissionDenied
Brad W. Young
DevSource LLC
DevSource LLC
Brad:
Apparently copy rights has a bug. I've created a bug to be fixed in the upcoming release of Vault.
As for manually configuring the user:
1) What is the user's default rights?
2) When the user logs in, does she see the repository in the repository listing?
3) Does the user belong to multiple groups? Double check each group for user's belonging to the groups.
Apparently copy rights has a bug. I've created a bug to be fixed in the upcoming release of Vault.
As for manually configuring the user:
1) What is the user's default rights?
2) When the user logs in, does she see the repository in the repository listing?
3) Does the user belong to multiple groups? Double check each group for user's belonging to the groups.
Jeff Clausius
SourceGear
SourceGear
-
- Posts: 18
- Joined: Thu Jan 15, 2004 12:56 pm
The user is only a member of one group. I tried creating a new group and using an existing group. The user had no default permisions. I have other existing users that are configured this way and they log in fine. I have tried setting default permisions. I have tried setting permisions explicitly on the user. Nothing appears to work. The user does not see the repository folder listing, I just get the following message when I try to login with the user.
---------------------------
SourceGear Vault
---------------------------
You do not have permission to perform the operation.
---------------------------
OK
---------------------------
---------------------------
SourceGear Vault
---------------------------
You do not have permission to perform the operation.
---------------------------
OK
---------------------------
Brad W. Young
DevSource LLC
DevSource LLC
-
- Posts: 18
- Joined: Thu Jan 15, 2004 12:56 pm
-
- Posts: 18
- Joined: Thu Jan 15, 2004 12:56 pm
This is getting stranger by the minute. OK... Let's try this. Since the user has never been able to log in, they haven't been able to make a change. Is that correct?
If so, let's delete the user and then re-create the user. Don't change any of the default security rights, or assign them to any group. Once you've done that, try to log in. Can the newly created user account access the repository?
If so, let's delete the user and then re-create the user. Don't change any of the default security rights, or assign them to any group. Once you've done that, try to log in. Can the newly created user account access the repository?
Jeff Clausius
SourceGear
SourceGear
-
- Posts: 18
- Joined: Thu Jan 15, 2004 12:56 pm