Vault 4.0.2 export issues

DennisPaisley · Post by **DennisPaisley** » Wed Aug 01, 2007 7:20 am

During an export of a folder (approx. 50% through) an error occurs. The export than aborts. Is there a way to continue or correct the error within the repository?

lbauer · Post by **lbauer** » Wed Aug 01, 2007 7:42 am

To diagnose this we would need more information. What errors are in the export log? It's in the export/import client directory.

Also, are there any corresponding errors in the
Vault Server Log

DennisPaisley · Post by **DennisPaisley** » Wed Aug 01, 2007 7:47 am

Here is the information in the log file. Would you like for me to snapshot the message box again?

7/31/2007 5:59:23 PM <generic>: [<No Name>:5340] Folder Export: File, $/Next Gen/Iteration 1/Designer/XML/MerchTransaction_Don'tUsePerChris.xml (ObjVerID: 1148745) encountered a problem with the cyclical redundancy check (CRC) of the pysical network transfer (2343317716). It did not match the CRC as calculated by the Vault server (212). It is possible an error occurred in the network stream. The export cannot continue.

DennisPaisley · Post by **DennisPaisley** » Wed Aug 01, 2007 11:12 am

Screen Snapshot of error

lbauer · Post by **lbauer** » Wed Aug 01, 2007 12:26 pm

The CRC errors are generally because the Export\Import tool and the server are experiencing communication problems -- what the client is sending isn't complete, for instance, or if the Server downloads files to the export file faster than the operating system can handle it.

If you're using two machines for the export, there could be a network glitch that gets in the way of communication. If you haven't done so already, you can try doing the import with an Export\Import Tool on the Vault Server itself, connecting to "localhost" for the server name.

There could be a disk error where that portion of the disk can't be read. Check out how fragmented your disks are or run a check disk.

Some other things that help with exporting:
--Don't export deleted items
--Export in smaller chunks
--Run the export on a machine separate from the production server. Restore a backup of the Vault server to a different machine and install Vault on it and run the export there instead.

We are working on optimizing Folder Export\Import, but it may be a few months before these improvements are available.

Another possibility is to send your database to SourceGear, and we can attempt the export on our machines.

DennisPaisley · Post by **DennisPaisley** » Wed Aug 01, 2007 12:42 pm

I am running the export on the Vault server as localhost, so it should be ok. The issue with sending you the DB is that the MDF is approx. 26 GB and the LDF is 50 GB.

Is there anything I can do to assist locating the issue on my end?

lbauer · Post by **lbauer** » Wed Aug 01, 2007 3:40 pm

Is there anything I can do to assist locating the issue on my end?

The main thing would be to try the tips above, especially try using different machines.

If you put your database into Simple Recover model, then you should be able to significantly shrink the .ldf file. You may be able to shrink the data file (.mdf) as well. After a shrink operation, backing up the database should result in a smaller backup file.

If it's still too big to upload, we have a removeable drive we can send you.

SourceGear Support