Changed user's groups & now they can't use the history t

montek · Post by **montek** » Wed Oct 27, 2004 10:28 am

Yesterday, I added a new security group to break apart my developers into two groups. The new group has full rights on folderA, just as the old group had. Now, however, the developers in the new group can't use the history tool on folderA. When they try, they get an error message: "A database error has occured (FailDBFault)". Looking in the Vault log (on the server), I see these types of entries:

Code: Select all


----10/27/2004 12:17:19 PM   kevin--10.1.2.44(10.1.2.44)--SSL Disabled
	Violation of PRIMARY KEY constraint 'PK__@@securityrights__54924B7D'. Cannot insert duplicate key in object '#539E2744'.
----10/27/2004 12:17:19 PM   kevin--10.1.2.44(10.1.2.44)--SSL Disabled
	BeginHistoryQuery returned: FailDBFault
----10/27/2004 12:17:27 PM   kevin--10.1.2.44(10.1.2.44)--SSL Disabled
	Logout
----10/27/2004 12:19:29 PM   kevin--10.1.2.44(10.1.2.44)--SSL Disabled
	Login
----10/27/2004 12:19:51 PM   kevin--10.1.2.44(10.1.2.44)--SSL Disabled
	Violation of PRIMARY KEY constraint 'PK__@@securityrights__7F12952E'. Cannot insert duplicate key in object '#7E1E70F5'.
----10/27/2004 12:19:51 PM   kevin--10.1.2.44(10.1.2.44)--SSL Disabled
	BeginHistoryQuery returned: FailDBFault

We are using Vault 2.0.1 (2137).

montek · Post by **montek** » Wed Oct 27, 2004 10:30 am

Also, I did try to put him back into the old group and that did not fix the problem.

Post by **jclausius** » Wed Oct 27, 2004 11:51 am

Monte:

What is the version of your Vault server?

montek · Post by **montek** » Wed Oct 27, 2004 1:18 pm

Hey Jeff. It's 2.0.1.2137.

Post by **jclausius** » Wed Oct 27, 2004 1:55 pm

Any chance of upgrading the server to 2.0.6? I believe that bug was fixed in a later version of Vault server.

I'll check our bug logs to see if that is the case.

montek · Post by **montek** » Wed Oct 27, 2004 2:01 pm

Well, I've been wanting to upgrade; however, I have a custom build tool that uses the API and I wasn't sure if it had changed and would cause problems. I was hoping to make it through another development iteration or two before doing it. At any rate, if it's a bug that's fixed, that's great. I know what my options are. Thanks, as always.

Post by **jclausius** » Wed Oct 27, 2004 2:06 pm

Yes, it appears a bug similar to this was fixed in Vault 2.0.3. In your repository, is one of the folders which have security a shared folder?

See "FailDBReader problem when invoking history on a shared folder with security turned on has been fixed." in http://support.sourcegear.com/viewtopic.php?t=1016

montek · Post by **montek** » Wed Oct 27, 2004 2:16 pm

Thanks a lot, Jeff. I'll have to plan an upgrade.

Post by **jclausius** » Wed Oct 27, 2004 2:34 pm

montek wrote:Well, I've been wanting to upgrade; however, I have a custom build tool that uses the API and I wasn't sure if it had changed and would cause problems. I was hoping to make it through another development iteration or two before doing it. At any rate, if it's a bug that's fixed, that's great. I know what my options are. Thanks, as always.

The API has not changed within the Vault 2.0.x family.