Error moving a folder

Igor.Samoylenko · Post by **Igor.Samoylenko** » Mon Dec 05, 2005 5:23 am

I cannot move a folder in our source database. It is a branch I have created several weeks ago.

This is not the first time I am doing this; never had any problems.

Please advise. Thanks a lot.

Igor.

Below is the log:

[05/12/2005 11:09:51] Beginning transaction
[05/12/2005 11:09:51] Move $/Solutions/CCATS/CCATS_MBU/TaskBranches/v1.7
[05/12/2005 11:09:51] Ending the transaction
[05/12/2005 11:09:53] An error occurred while trying to end a transaction.
[05/12/2005 11:09:53] 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)
[05/12/2005 11:09:53] Transaction failed
[05/12/2005 11:09:53] Item $/Solutions/CCATS/CCATS_MBU/TaskBranches/v1.7 caused the transaction to fail: A database error has occured (FailDBReader)
[05/12/2005 11:09:53] Transaction failed

Igor.Samoylenko · Post by **Igor.Samoylenko** » Mon Dec 05, 2005 5:24 am

A few more things:

No files are checked out in the folder.

I also cannot rename the folder with the same error.

Regards,

Igor.

lbauer · Post by **lbauer** » Mon Dec 05, 2005 8:04 am

What version of Vault client and server are you using? Are you experiencing the database error only on this particular folder?

Igor.Samoylenko · Post by **Igor.Samoylenko** » Mon Dec 05, 2005 8:26 am

The versions are:

[05/12/2005 11:09:41] Version Check: This Vault client is version 3.1.2.3511
[05/12/2005 11:09:41] Version Check: Your Vault server is version 3.1.0.3494

I haven't tried to move any other folder recently but I have done that in the past without any errors.

Thanks.

Igor.

Post by **jclausius** » Mon Dec 05, 2005 8:55 am

Let's see what the server has recorded in the Vault server log.

Post or email any log entries related to the move.

Igor.Samoylenko · Post by **Igor.Samoylenko** » Mon Dec 05, 2005 12:19 pm

Here you are:

----05/12/2005 15:13:06 ISamoylenko--ukwkstn93.friskman.com(192.168.64.245)--SSL Disabled Login
----05/12/2005 15:13:14 ISamoylenko--ukwkstn93.friskman.com(192.168.64.245)--SSL Disabled System.Data.SqlClient.SqlException: Violation of PRIMARY KEY constraint 'PK__@@tblfsobjectsha__02D28703'. Cannot insert duplicate key in object '#01DE62CA'.
The statement has been terminated.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at VaultServiceSQL.VaultSqlSCC.GetItemsForPathChange(VaultSqlConn conn, Int32 nRepID, Int64 nObjID, Int64 nOwnerFolderObjID, String strXml, String strXmlShares, VaultCloakedFolder[]& vcf, VaultFolderRightsItem[]& vfri, VaultShareHint[]& vsh) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at VaultServiceSQL.VaultSqlSCC.GetItemsForPathChange(VaultSqlConn conn, Int32 nRepID, Int64 nObjID, Int64 nOwnerFolderObjID, String strXml, String strXmlShares, VaultCloakedFolder[]& vcf, VaultFolderRightsItem[]& vfri, VaultShareHint[]& vsh)
----05/12/2005 15:13:14 ISamoylenko--ukwkstn93.friskman.com(192.168.64.245)--SSL Disabled (db203a86-ea7a-4b4c-9a0b-c286f154f1d1) EndTx (Revision - 0) returned: FailDBReader
----05/12/2005 15:13:14 ISamoylenko--ukwkstn93.friskman.com(192.168.64.245)--SSL Disabled (db203a86-ea7a-4b4c-9a0b-c286f154f1d1) Move: $/Solutions/CCATS/CCATS_MBU/TaskBranches/v1.7 to $/Solutions/CCATS/CCATS_MBU/Archive returned: FailDBReader
----05/12/2005 15:15:38 ISamoylenko--ukwkstn93.friskman.com(192.168.64.245)--SSL Disabled Logout

Post by **jclausius** » Mon Dec 05, 2005 1:26 pm

To resolve this issue, we're going to have to take a look at some of the database internals.

The easiest / fastest to resolve this issue is to upload a copy of the sgvault database. We can provide NDA assurances if that is an issue. Otherwise, we'll need to run SQL queries back and forth while investigating the problem.

Please let me know how you would like to proceed.

Igor.Samoylenko · Post by **Igor.Samoylenko** » Tue Dec 06, 2005 3:24 am

Jeff,

Thanks for your quick reply.

I don't mind sending you the database backup; I will need NDA assurances for that please.

Please send me the instructions (where to send/upload the file, what else you need etc).

My slight worry is the state of our source database. Have you seen this sort of problem before? Is it likely to be isolated to that folder or could it also affect others (or all folders)?

Is there anything we should not do while you are investigating?

Thanks a lot.

Regards,

Igor.

Post by **jclausius** » Tue Dec 06, 2005 9:18 am

Igor.Samoylenko wrote:I don't mind sending you the database backup; I will need NDA assurances for that please.

No problem. We'll make sure this in place before uploading

Igor.Samoylenko wrote:Please send me the instructions (where to send/upload the file, what else you need etc).

When we are reading, make a complete backup of the sgvault database. If it is rather large file or you have a slow Internet connection, compress the file (.rar, .tar, or .zip). Then anonymously upload the file to ftp.sourcegear.com. Place the file in the /incoming directory, and then send me an email of the file's name. You can use the email button below this post to contact me. I'll also need to know what repository you are working with, as well as any relevant information related to the folder.

Igor.Samoylenko wrote:My slight worry is the state of our source database. Have you seen this sort of problem before? Is it likely to be isolated to that folder or could it also affect others (or all folders)?

We don't have any record of this kind of thing. I'll make sure I give the repository a thorough inspection, and provide SQL to fix anything that needs attention.

Igor.Samoylenko wrote:Is there anything we should not do while you are investigating?

I know it i a lot to ask, but if you could try to hold off on any changes within the folder (or if the folder is shared or contains shared files do not change those), until I can diagnose things, that would be helpful.

We'll make sure everything is OK.