Merging Branches failes to due retrivieng history

roland · Post by **roland** » Mon Jul 30, 2007 1:41 am

Hi,

in the course of last 1/2 year i did a lot of branching and merging without any problem. Since Friday I can't merge anymore. Whatever i do i get a "Retrieving historical folder information from the server failed." on the "Moves and Shares" step of the Merge Wizard.

I don't really know what happened. We are using Version 3.5.2.5087 on Client and Server side.

I don't have a clue what's wrong now. I have to do 3 merges this week, the first today.

Any hint's are highly welcome.

Thanks,
Roland

lbauer · Post by **lbauer** » Mon Jul 30, 2007 5:42 am

Is there anything reported in the
Vault Server Log when the error is reported on the client side?

roland · Post by **roland** » Mon Jul 30, 2007 6:44 am

Thanks for immediate response,

now it's working!! the Log entry showed the following:

at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at VaultServiceSQL.VaultSqlSCC.GetRepositoryTreeFolderStructure(VaultSqlConn conn, Int32 nRepID, Int64 nRevID, Int64 nObjVerID, Int32 nTxAction, Boolean bTxDirectModified, Boolean bWithCurrentName, Int64 nPinFromObjVerID, HybridDictionary htTxModifiedItems, VaultFolder& vfBranch) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at VaultServiceSQL.VaultSqlSCC.GetRepositoryTreeFolderStructure(VaultSqlConn conn, Int32 nRepID, Int64 nRevID, Int64 nObjVerID, Int32 nTxAction, Boolean bTxDirectModified, Boolean bWithCurrentName, Int64 nPinFromObjVerID, HybridDictionary htTxModifiedItems, VaultFolder& vfBranch)
----7/30/2007 9:23:47 AM rwinkler--SCN001(10.0.1.36)--SSL Disabled GetFolderStructure returned: FailDBReader

what i did was increasing the SQL timeout setting on the server as suggested in another thread. Looks like that we also got a SQL-Timeout before he was finished.

To run the release this should be enough right now.

Thanks,
Roland

lbauer · Post by **lbauer** » Mon Jul 30, 2007 7:20 am

Yes, increasing the SQL timeout would help with operations that take a long time to complete.

This setting is found in the Vault.config file in the Vault service directory:

<SqlCommandTimeout>360</SqlCommandTimeout>

You can change the value on this line to 720, or even 3600.