If you receive error messages during analysis or migration, it means that some files or folders were not migrated. It does not mean that the migrated database is unusable. You can choose to ignore the files that were not migrated and start using the migrated sources in Team Foundation.
File and folder migration errors are generated when the converter cannot migrate or analyze versions of files or folders because there is an unhandled case in the Visual SourceSafe Converter. This section contains information about unmigrated files and folders that the converter could not warn about during analysis. Each error message gives a brief description of the error that was encountered during migration or analysis.
The following are common errors and solutions:
Unable to migrate The converter detected a version history scenario that is not supported. Therefore, the files and folders in the version history scenario might not have migrated correctly. Use a file compare utility, such as the WinDiff too, to look for differences between the latest versions of the files and folders in Visual SourceSafe and the latest versions of the migrated files and folders in Team Foundation version control. If there are differences between the files, folders, or their versions, migrate the latest version of the files and folders manually.
You can migrate a file or folder manually by getting the latest version from Visual SourceSafe and adding it to Team Foundation version control using Source Control Explorer or the tf command-line client.
Unable to migrate folder recursively due to IO Error During migration, the converter could not add a folder to Team Foundation because of an Input/Output error. The error message is appended to the brief description of the error. After migration, you can add the most current version of the folder by doing a get latest version of files and folders in Visual SourceSafe and then doing a single check-in of these versions.
Unable to migrate due to Team Foundation Error The converter cannot migrate a version of the file or folder due to known, or unknown, problems with Team Foundation. The error message received by the converter from Team Foundation is appended to the brief description of the error. Try to fix the problem by getting a copy of the file or folder from Visual SourceSafe and manually checking it in to Team Foundation.
Unable to migrate label due to Team Foundation Error The converter cannot apply a Team Foundation version control label. The error message received by the converter from Team Foundation is appended to the brief description of the error.
Unable to migrate. The path contains more than the allowed 260 characters The maximum server path length supported by Team Foundation version control is 260 characters. The converter cannot migrate the version of the file or folder because of this constraint.