Import Errors on Repositories Requiring Check-in Comments

[Chiramisu]

My company has a LOT of code to maintain, many of it is currently being updated to run on a new server and thus the code must be drastically changed to support the new environment. We would like to use the new Vault 6 feature and move projects like these to a new "Archives" repository. I so far had no issues with with the Export but I'm getting errors with almost every Import attempt to the new repository. Here's the most common one:



Some additional minor complaints with the Export / Import utility:
- It doesn't remember the last browsed to location for either function.
- The comments are locked on the Import function.
- The comments are not visible in the Vault client (more on this here).

[lbauer]

The best way to troubleshoot this is to get a copy of your .vfe file. Email support at sourcegear.com attn: inda. Include a link to this forum post and we'll provide an NDA and info on getting the file(s) to us.

[Chiramisu]

Thank you Linda for helping me get this fixed.

It seems the issue was that the repository I was trying to Import into had the "Require check in comments" option ticked and since only some of the files in the project had check in comments, it failed.

The solution was to un-tick this option, then recycle the VaultAppPool Application Pool on the server. Finally, restart the Export Import tool and it should work. This solved my problem.

[lbauer]

You're welcome. Glad it's working now.