FailDBInsert

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
epatrick@quandis.com
Posts: 3
Joined: Tue Aug 01, 2006 6:50 am

FailDBInsert

Post by epatrick@quandis.com » Tue Aug 01, 2006 6:56 am

We are using SourceVault 3.0.7.2863 with a SQL 2000 back end. We just started receiving an error message on some folders. The client reports an error "A database error has occurred (FailDBInsert).", and the message pane includes:

[8/1/2006 8:55:38 AM] Server unavailable for transaction end
[8/1/2006 8:55:38 AM] An exception was encountered during the transaction. Exception: Exception of type System.Exception was thrown. at VaultClientOperationsLib.ClientInstance.Commit(ChangeSetItemColl givenItems, Boolean keepCheckedOut, Boolean removeLocalCopy, Boolean bIsImport, DateTime dateImport, Int32 nUserIDImport, Int64& nRevID)
[8/1/2006 8:55:38 AM] Transaction failed
[8/1/2006 8:55:39 AM] Transaction failed

I've reviewed the forums and find references to sgvault.log files, but cannot find such a file on our server.

Suggestions?

Eric Patrick
CTO
Quandis

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Tue Aug 01, 2006 7:03 am

We would need to take a look at the Vault Server log file. It's sgvault.log, by default in %windir%\temp\sgvault. It's possible to reconfigure this location. Look in the Vault Admin Tools under Server Options->logging to see if a different location has been set.
Linda Bauer
SourceGear
Technical Support Manager

epatrick@quandis.com
Posts: 3
Joined: Tue Aug 01, 2006 6:50 am

sgvault.log file attached

Post by epatrick@quandis.com » Tue Aug 01, 2006 7:10 am

Log file is attached.
Attachments
sgvault.log.txt
(42.29 KiB) Downloaded 349 times

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Tue Aug 01, 2006 7:17 am

Try restarting IIS. Does that help? If you continue to experience this error email me at linda at sourcegear.com. We may need to take a look at your database.
Linda Bauer
SourceGear
Technical Support Manager

epatrick@quandis.com
Posts: 3
Joined: Tue Aug 01, 2006 6:50 am

IIS Restart and server reboot make no difference

Post by epatrick@quandis.com » Tue Aug 01, 2006 7:28 am

Tried a WWW Publishing Service restart to no avail, and a complete server reboot to no avail.

Log seems to indicate some perhaps "corrupt" data in the tblfsobjectversions table. Is there a way to flush such entries?

sgvault.log entries since server reboot are:

----8/1/2006 6:24:59 AM sgvaultsystem--()--
System Started
Version 3.0.7.2863
Cache Level = 1
DataBase Buffer Size (KB) = 256
LogFile Path = C:\WINDOWS\Temp\sgvault
Log Level = Quiet
Archive Log = Weekly
ReverseDNS Lookup = True
Maximum HTTP Request Length = 200000
Overwrite Log on Startup = False
Session Timeout = 4320
Active Directory Domain =
SGVault Working Directory = C:\WINDOWS\Temp
SGVault Server URL = http://dev.quandis.com/VaultService
Identity = CANCER\epatrick
----8/1/2006 6:25:20 AM epatrick--pool-71-162-111-235.bstnma.east.verizon.net(71.162.111.235)--SSL Disabled Login
----8/1/2006 6:25:38 AM epatrick--pool-71-162-111-235.bstnma.east.verizon.net(71.162.111.235)--SSL Disabled Cannot insert duplicate key row in object 'tblfsobjectversions' with unique index 'idxfsobjectversionversions'.
The statement has been terminated.
----8/1/2006 6:25:38 AM epatrick--pool-71-162-111-235.bstnma.east.verizon.net(71.162.111.235)--SSL Disabled Could not create bubble folders: Error in the application.
----8/1/2006 6:25:38 AM epatrick--pool-71-162-111-235.bstnma.east.verizon.net(71.162.111.235)--SSL Disabled VaultLib.VaultResponseCheckIn returned: Success
----8/1/2006 6:25:38 AM epatrick--pool-71-162-111-235.bstnma.east.verizon.net(71.162.111.235)--SSL Disabled EndTxFailDBInsert

jkp*74
Posts: 147
Joined: Wed Dec 15, 2004 9:42 pm
Contact:

Re: FailDBInsert

Post by jkp*74 » Wed Mar 17, 2010 4:19 am

I face this problem after moving the database to a new server. DB restore ended successfully. However, when i want to add new files into this repository, this error appear. (see attachment) It only happens to this particular repository.
Strange observation:
1) When show history on any folders in the repository, it returns blank.(see attachment) When apply on files, it was OK.
2) One particular file shows version 6 in history explorer but display as version 7 in the file list panel. (see attachment).

Any solution to fix this problem?

I am using Fortress version 1.1.4(18402), SQL Server 2000 on Windows Svr 2003.
Attachments
blank history.jpg
Blank history
blank history.jpg (28.32 KiB) Viewed 6462 times
History - version.jpg
Different version information
History - version.jpg (90.53 KiB) Viewed 6462 times
fortress log.txt
Fortress log showing the exception
(6.35 KiB) Downloaded 296 times
Joel
Micro Modular System
http://www.mmsis.com

jkp*74
Posts: 147
Joined: Wed Dec 15, 2004 9:42 pm
Contact:

Re: FailDBInsert

Post by jkp*74 » Wed Mar 17, 2010 4:28 am

When trying to get latest file "Hour-PH Teoh.ods", this error was recorded in client Message pane:

[3/17/2010 5:53:48 PM] Getting latest version of $/Project Track/PH Teoh
[3/17/2010 5:53:49 PM] Fetched $/Project Track/PH Teoh/Hour-PH Teoh.ods
[3/17/2010 5:53:49 PM] Fetched $/Project Track/PH Teoh/Hour-PH Teoh.ods
[3/17/2010 5:53:49 PM] An error was found with the baseline file for $/Project Track/PH Teoh/Hour-PH Teoh.ods. Refetching baseline and retrying get operation...
[3/17/2010 5:53:49 PM] Finished get latest of $/Project Track/PH Teoh
[3/17/2010 5:53:49 PM] Get latest version failed for $/Project Track/PH Teoh/Hour-PH Teoh.ods: Invalid object version specified.

No error recorded in the server log.

When view version 7 of the file, it shows entirely different content: (see attachment - version 7)
When view version 6 from history explorer, it shows the correct content (see attachment - version 6)
Attachments
version 6.jpg
Correct content - view from history explorer
version 6.jpg (25.61 KiB) Viewed 6461 times
version 7.jpg
Wrong content - view direct from file panel
version 7.jpg (51.71 KiB) Viewed 6461 times
Joel
Micro Modular System
http://www.mmsis.com

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: FailDBInsert

Post by lbauer » Wed Mar 17, 2010 9:09 am

This could be a database issue or it could simply be the client cache out of sync with the database. So the first suggestion would be to delete the client-side cache while all your clients are closed, then restart IIS.

You can reset the cache with the following steps:

Find the path %USERPROFILE%\Local Settings\Application Data\SourceGear\Vault_1 and delete or rename the entire Vault_1 folder. Next,restart IIS with the "iisreset" command from the command line.

When you open you client after the IIS restart, reset working folders and perform a Get Latest with Do Not Overwrite/MergeLater to re-establish baselines, rebuild the cache files and reset file status.

Let me know if this does not resolve the problem.
Linda Bauer
SourceGear
Technical Support Manager

jkp*74
Posts: 147
Joined: Wed Dec 15, 2004 9:42 pm
Contact:

Re: FailDBInsert

Post by jkp*74 » Wed Mar 17, 2010 6:17 pm

It WORKS !!! :D
I had deleted the cache earlier on but did not perform iisreset.
Thanks.
Joel
Micro Modular System
http://www.mmsis.com

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: FailDBInsert

Post by lbauer » Thu Mar 18, 2010 7:25 am

Thanks for the update. That's good news. : )

The server has its own in-memory cache, which can also get out of sync, especially if you restore a copy of the database.
Linda Bauer
SourceGear
Technical Support Manager

Post Reply