Vault 3.5.1 Eksport attempt fails

Hans Olav Nymand · Post by **Hans Olav Nymand** » Thu Oct 12, 2006 3:13 pm

Hi,

We've just upgraded til 3.5.1 and after that I tried to use the Export tool.

But it terminates with the following error in the VaultFolderExportImport.txt:

12-10-2006 23:05:49 <generic>: [<No Name>:2824] Folder Export: Error in ProcessResults_ProcessTransaction() An exception was encountered retrieving the Tx Information for $/Argos/Source/Argos/Work/Src/eMapServerSolution/eMapServer/MapComm. Tx: 10955 Previous Tx: 10892 [1108 : FailDBInvalidTreeRecords] [System.Web.Services.Protocols.SoapException: 1108 : FailDBInvalidTreeRecords
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at VaultClientNetLib.AdminService.VaultAdminService.GetRepositoryDeltaForFolderExport(Int32 nRepID, Int64 nBaseRevision, Int64 nTargetRevision, VaultRepositoryDelta& rd)
at VaultClientNetLib.VaultConnection.GetRepositoryDeltaForFolderExport(Int32 nRepID, Int64 nSrcRevision, Int64 nDestRevision, VaultRepositoryDelta& rd)
at VaultClientOperationsLib.ClientInstance.GetRepositoryDeltaForFolderExport(Int32 repid, Int64 srcrevision, Int64 destrevision, VaultRepositoryDelta& rd)
at VaultFolderExportImport.ExportWorkerThread.ProcessTransaction(String strProcessMsgType, Int64 nTxID, Int64 nPrevTxID)]1108 : FailDBInvalidTreeRecords
[System.ApplicationException: An exception was encountered retrieving the Tx Information for $/Argos/Source/Argos/Work/Src/eMapServerSolution/eMapServer/MapComm. Tx: 10955 Previous Tx: 10892 ---> System.Web.Services.Protocols.SoapException: 1108 : FailDBInvalidTreeRecords
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at VaultClientNetLib.AdminService.VaultAdminService.GetRepositoryDeltaForFolderExport(Int32 nRepID, Int64 nBaseRevision, Int64 nTargetRevision, VaultRepositoryDelta& rd)
at VaultClientNetLib.VaultConnection.GetRepositoryDeltaForFolderExport(Int32 nRepID, Int64 nSrcRevision, Int64 nDestRevision, VaultRepositoryDelta& rd)
at VaultClientOperationsLib.ClientInstance.GetRepositoryDeltaForFolderExport(Int32 repid, Int64 srcrevision, Int64 destrevision, VaultRepositoryDelta& rd)
at VaultFolderExportImport.ExportWorkerThread.ProcessTransaction(String strProcessMsgType, Int64 nTxID, Int64 nPrevTxID)
--- End of inner exception stack trace ---]An exception was encountered retrieving the Tx Information for $/Argos/Source/Argos/Work/Src/eMapServerSolution/eMapServer/MapComm. Tx: 10955 Previous Tx: 10892

Is this an inconsistency in my database OR is it a bug in the Export tool OR is it something else?

Best regards,
Hans Olav Nymand

lbauer · Post by **lbauer** » Fri Oct 13, 2006 7:29 am

This is probably an inconsistency in the database. In earlier versions of Vault, information on some transactions may not have been properly recorded in the database. An export, which must recreate all history, can expose these inconsistencies.

We still have a copy of your database from a previous support issue, so we can do some tests.

What repository folder were you trying to export? Can you send us the export log? It's in the Export\Import tool directory. A copy of the Vault server log that covers the time of the export would be helpful, too. It's sgvault.log from %windir%\temp\sgvault.

Email to support@sourcegear.com