Hi, we are running Vault 2.0.3. Some of our users have had problems where they will be working fine after their initial Vault setup but then they will get either get a "Object not set to an instance of an object" error or VS.NET just hangs. After that, when they try to log back in they keep getting prompted to login to the Vault repository and are never able to. When I go into the Vault Admin tool I see that they are setup in the proper project group, but they still don't have access. I then remove them from the group and add them back in and "poof" everything works fine again. I have had this problem with about 7 out or 20 people in our repository today.
Thanks,
Shane Henderson
Match.com
shane.henderson@match.com
Users Rights disappear
Moderator: SourceGear
-
- Posts: 14
- Joined: Wed Jun 23, 2004 9:36 am
- Contact:
Shane,
We've had another report of something like this, but I couldn't reproduce it here.
http://support.sourcegear.com/viewtopic.php?t=1257
Can you give me details about what you're doing, so that I can try to get this fixed before 2.0.4 comes out. If you want to, you can email me the details.
The questions I have are:
1. What's your security setup? Do users have rights given by group or by user?
2. Does deleting the client side cache fix the problem? See http://support.sourcegear.com/viewtopic.php?t=6
I want as much information as you can give me.
We've had another report of something like this, but I couldn't reproduce it here.
http://support.sourcegear.com/viewtopic.php?t=1257
Can you give me details about what you're doing, so that I can try to get this fixed before 2.0.4 comes out. If you want to, you can email me the details.
The questions I have are:
1. What's your security setup? Do users have rights given by group or by user?
2. Does deleting the client side cache fix the problem? See http://support.sourcegear.com/viewtopic.php?t=6
I want as much information as you can give me.
-
- Posts: 14
- Joined: Wed Jun 23, 2004 9:36 am
- Contact:
User Right disappear (more info)
Hi Jeremy,
Thanks for your reply.
Here's some more information:
All users are on Visual Studio.NET 2003 and Windows Server 2003. The main solution that we use contains one main web project and approx. 50 small class libraries. This project was imported into Vault last Friday and most users made the switch from VSS to Vault on Monday morning.
We are running Vault with Project level security and I am assigning people to groups that are then assigned to a specific set of projects.
I have talked to several people and can't seem to get a straight answer on exactly what they were doing when this problem happened. Some tell me that they were just working fine and the next time that they open Visual Studio they get prompted to Login to Vault over an over again and then they eventually get prompted to work disconnected. If we try to open the Vault GUI Client it says "Object Reference not set to an instance of an object" and then closes.
When I go into the Vault Admin client and remove then from their group and then add them back in the problem goes away.
If this happens again I'll try to get them to clear their Vault cache and see if that clears it up without having to reset their rights in the Administrator.
Thanks,
Shane
Thanks for your reply.
Here's some more information:
All users are on Visual Studio.NET 2003 and Windows Server 2003. The main solution that we use contains one main web project and approx. 50 small class libraries. This project was imported into Vault last Friday and most users made the switch from VSS to Vault on Monday morning.
We are running Vault with Project level security and I am assigning people to groups that are then assigned to a specific set of projects.
I have talked to several people and can't seem to get a straight answer on exactly what they were doing when this problem happened. Some tell me that they were just working fine and the next time that they open Visual Studio they get prompted to Login to Vault over an over again and then they eventually get prompted to work disconnected. If we try to open the Vault GUI Client it says "Object Reference not set to an instance of an object" and then closes.
When I go into the Vault Admin client and remove then from their group and then add them back in the problem goes away.
If this happens again I'll try to get them to clear their Vault cache and see if that clears it up without having to reset their rights in the Administrator.
Thanks,
Shane