Critical Migration Errors
If analysis or migration is interrupted, you will receive a critical error that indicates what caused analysis or migration to fail. The converter lets you restart the migration from the point at which migration was interrupted. For more information about incremental migration, see the note at the top of the topic How to: Migrate from Visual SourceSafe to Team Foundation.
The following are the most common reasons why you would receive a critical error during migration:
You cancel migration During migration or analysis, you stopped migration forcefully by ending the application process. You can restart migration from the point it stopped using incremental migration. For more information about incremental migration, see How to: Migrate from Visual SourceSafe to Team Foundation.
Migration stopped due to an error with the SQL database used by the converter The VSS Converter uses SQL Express or SQL Server for processing data during migration. When you receive this error, the migration stopped because of a fatal error that occurs with the SQL database. The error message received by the converter is appended to the description of the critical error. By using information from the error message, fix the problem and restart migration from the point it stopped using incremental migration. For more information about incremental migration, see How to: Migrate from Visual SourceSafe to Team Foundation.
Application is unable to handle exception The VSS Converter is unable to handle a fatal exception during analysis or migration. The error message received by the converter is appended to the description of the critical error. Using the error message, try to fix the problem. As soon as the problem is fixed, analysis must be started from the beginning; however, if you were migrating, you can restart migration from the point it stopped using incremental migration. For more information about incremental migration, How to: Incrementally Migrate to Team Foundation