FailDBFault

[Sridhar]

We started getting the message $/<file> caused the transaction to fail: You must merge your working copy with the newest version before Check In can succeed.
It happens with all the users for the specific file. We cleared the cache and tried, still the problem persists. When I try to view history, I get the error

A database error has occured (FailDBFault)

[Sridhar_TR]

Here is the log file extract.

----4/13/2005 1:59:03 AM Sridhar--SRIDHAR2(10.43.64.109)--SSL Disabled Login
----4/13/2005 1:59:58 AM Sridhar--SRIDHAR2(10.43.64.109)--SSL Disabled BeginTx returned: FailOutofDateObjVerID
----4/13/2005 1:59:58 AM Sridhar--SRIDHAR2(10.43.64.109)--SSL Disabled VaultLib.VaultRequestCheckIn returned: FailOutofDateObjVerID
----4/13/2005 2:00:18 AM Sridhar--SRIDHAR2(10.43.64.109)--SSL Disabled Cannot insert the value NULL into column 'objprops', table 'tempdb.dbo.#tmpresults_________________________________________________________________________________________________________00010000001F'; column does not allow nulls. INSERT fails.
----4/13/2005 2:00:18 AM Sridhar--SRIDHAR2(10.43.64.109)--SSL Disabled BeginHistoryQuery returned: FailDBFault

[Sridhar_TR]

Vault started slowing down when I had switched on folder security based on groups. I switched it off and some users had problems in getting the correct status. By cleaning out the cache, they were solved. The problems showed up in Version 3.0.1.

On getting the FailedDBFault error, I decided to upgrade to 3.0.6. Still no luck.

[jclausius]

Do you have a server log where the Transaction / History Queries are not intermingled?

If not, can you quickly run the History Query one more time, and then post the new entries from the server log?