Reestablishing Vault Connection.

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

Moderator: SourceGear

Post Reply
Dhominator
Posts: 35
Joined: Tue Mar 14, 2006 12:33 pm

Reestablishing Vault Connection.

Post by Dhominator » Tue May 30, 2006 11:51 am

3.1.8
In the import tool, Import In Progress page, I see "Reestablishing Vault Connection" flashing a lot (alternating with "uploading change"). Is this normal operation as in once per file/revision?

Best,
/jhd

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

Post by lbauer » Wed May 31, 2006 7:54 am

It is normal to see this from time to time, perhaps after 50 versions or so. If you're seeing it very frequently, it could be because of errors. Check the import log file in the Import Tool directory to see what the errors might be.
Linda Bauer
SourceGear
Technical Support Manager

Dhominator
Posts: 35
Joined: Tue Mar 14, 2006 12:33 pm

Post by Dhominator » Thu Jun 08, 2006 8:59 am

was importing a big project one solution at a time. 4th solution ran fine until it appeared to be finishing (full progress bar). then it started doing the reconnect mambo. sgvault.log appears to contain one of the messages below for every file it is trying to process. Progress bar shows complete, time remaining 00:00:00 after these errors start happening.

What does this mean? Unsure how to proceed at this point. Kill the import? Delete the solution tree? Is the repo corrupt?

[edit]
I am remapping 3 vss accounts during the import. Appeared to work for the previous 3 imports. Could this be related?

/jhd

----6/8/2006 7:19:17 AM USERNAME--MACHINENAME (10.5.146.74)--SSL Disabled System.Data.SqlClient.SqlException: Cannot insert duplicate key row in object 'tblusers' with unique index 'idxuserlogins'.
The statement has been terminated.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at VaultServiceSQL.VaultAdminSQL.AddUser(VaultSqlConn conn, Int32 nUserID, VaultUser& vUser) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at VaultServiceSQL.VaultAdminSQL.AddUser(VaultSqlConn conn, Int32 nUserID, VaultUser& vUser)

Dhominator
Posts: 35
Joined: Tue Mar 14, 2006 12:33 pm

Post by Dhominator » Thu Jun 08, 2006 9:22 am

Riddle me this... the import finally completed with the following messages.

The import is complete. There wer 23340 errors, which are described in the final report below.

drumroll

No errors occurred during import.

[edit]
ok, the above text must be the control default as the import screen is frozen atm. will probably get the real message in a few minutes.

please change the default text to something more like "processing final report, please wait...".

/jhd

Dhominator
Posts: 35
Joined: Tue Mar 14, 2006 12:33 pm

Post by Dhominator » Thu Jun 08, 2006 9:42 am

The final error report messages don't really track with the log errors.?.?

It is crucial that the state of this repo be determined. Confidence level is waning due to previous vault service, db schema problem, and repo corruption.
  • * what causes the tbluser type errors?
    * do the errors below track with the log file errors?
    * how do i confirm the repo is in tact and integral?
    * how do i confirm the db is in tact and integral?
    * is there any way to create a new db and migrate sources with history?
bunches of these errors...

Item
$/Trunk/somepath/somefile.cs caused the transaction to fail: Invalid object version specified.
Transaction failed

even more of these... actually, mostly these...

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)
Transaction failed
Transaction failed
An error occurred while trying to end a transaction.

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Thu Jun 08, 2006 9:51 am

It does seem like something is going on here. Can you look at your Vault server log file to check if there are serious errors logged?

Dhominator
Posts: 35
Joined: Tue Mar 14, 2006 12:33 pm

Post by Dhominator » Thu Jun 08, 2006 10:12 am

Have hundreds of errors like the one posted above (tbluser error).

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Thu Jun 08, 2006 10:20 am

Email me your phone number using the button below this post, and I'll see if I can figure out what is going on.

Dhominator
Posts: 35
Joined: Tue Mar 14, 2006 12:33 pm

Post by Dhominator » Thu Jun 08, 2006 11:25 am

will do.

update: same solution imported in 19 minutes, clean, to a new repo.

p.s. previous attempt was also to a new repo. :?

question: is it ok for a user to access another repo during import? should the db be off limits or just the repo?

/jhd

Post Reply