Import/Export tool failing

[avonwyss]

We have a Vault 4.0 server (upgraded from 3.1.9) and I would like to reorganize the repositories. Therefore, I tried to export parts of some repositories with the Import/Export tool, but it always fails:

"An error occured downloading one of the deltas for (TxID: 28176 on 25.1.2006 17:23 by username [36]). The export cannot continue."

The VFE file is then lying around, about 38MB in size, but it cannot be imported (fails with an exception). It does not matter whether I choose to download deleted files or not. The server works fine otherwise, and this error is reproducible. Is there a log or something that could help troubleshooting this issue?

Also, do the export files stay compatible across different versions of Vault (e.g. 3.5, 4.0, future versions)?

[lbauer]

There should be an export log in the export/import tool directory.

What errors does it report?

We've had some reports of users exporting from 3.5 and importing into Vault 4.0, but we don't recommend this. For best results, export from the same version you are importing into.

[avonwyss]

The error line says (don't worry, time is European Daylight Saving):
"18.07.2007 17:08:48 <generic>: [<No Name>:752] Folder Export: File, $/filename.xxx (ObjVerID: 139973) encountered a problem with the cyclical redundancy check (CRC) of the pysical network transfer (1239949464). It did not match the CRC as calculated by the Vault server (8344). It is possible an error occurred in the network stream. The export cannot continue."

I get this for each aborted export, but on different files. However, I can assure you that the network is fine, this server and network setup has been in use for months and has never shown any irregularities. Could it maybe be that there is some race condition or such, making the CRC appear wrong in rare cases (probably on the client side)?

[lbauer]

We've had reports of CRC errors during export, and have been able to reproduce this on certain machines. It seems to happen more commonly on Windows 2003 server machines. This is a bug that we plan to fix in Vault 4.0.4, due out within the next several weeks.

In the meantime, you can try running the export on a different machine, or even installing a test Vault server on a different machine to see if that makes a difference.

[avonwyss]

Just for the record, the Vault Server is running on Windows 2003 on a 2-processor SMP machine (in case this matters). However, I ran the export tool from an XP machine so far. I'll try if it works locally on the server.

[avonwyss]

Okay, tried with another client (no success) and now with another server (success exporting).

However, when trying to import the freshly exported file on a different repository with the same client/server setup, I always get an abort, this time consistently on the same transaction.

The log shows this (anonymized file and user names):
23.07.2007 13:59:47 <generic>: [<No Name>:5640] Folder Import: Importing Transaction for user on 22.12.2005 09:26:09 TxID = 27224
23.07.2007 13:59:47 <generic>: [<No Name>:5640] Folder Import: An unexpected error was encountered during Import in ProcessResults_ProcessTransaction(): 27224 on 22.12.2005 09:26:09 Change Set Items (Modified File) $/aaa/bbb/ccc/ddd/eee.xxx (Modified File) $/aaa/bbb/ccc/ddd/fff.xxx. Failure
23.07.2007 14:01:50 <generic>: [<No Name>:5640] Folder Import: Closing the Import Dialog with Dialog Result: Cancel

[lbauer]

Are there any error messages in the Vault Server log that correspond to the import error?

[steblewl]

When attempting to export (version 4.0.2), I get the following error (see attached error log text file for more details):

[System.Web.Services.Protocols.SoapException: VaultServiceAPILib.VaultSoapException: 1108 : FailDBInvalidTreeRecords
at VaultService.VaultAdminService.GetRepositoryDeltaForFolderExport

[jclausius]

Can you check for the corresponding errors for
Vault Server Log .