When you use the Vssconverter.exe utility in Microsoft Visual Studio 2005, you may receive an error message that resembles the following:
TF60047: Converter is retrying to migrate the action that was failed to migrate. This could be due a temporary problem with network or server. In case this problem persists then please check your network connection or Team Foundation Server.
Additionally, an error message that resembles the following may be logged in the Vssconverter.exe log file:
"BaseExceptionMessage: '', hexadecimal value 0x1A, is an invalid character."
This issue occurs when you try to use the Vssconverter.exe utility to migrate a Microsoft Visual SourceSafe database to Microsoft Visual Studio 2005 Team Foundation source control.
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Visual Studio 2005 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note
In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone
tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
|File name||File version||File size||Date||Time|
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Before you migrate the Visual SourceSafe databases to Team Foundation source control, you can use the Vssconverter.exe command-line utility to analyze and prepare the databases.
The Vssconverter.exe file is located in the Drive
:\Program Files\Microsoft Visual Studio 8\Common7\IDE folder. You can also start the Vssconverter.exe command-line utility at the Visual Studio 2005 command prompt.
This issue occurs because the Vssconverter.exe utility does not remove XML characters that are not valid characters from Visual SourceSafe labels or label comments. For example, Visual SourceSafe labels or label comments may contain XML characters that are not valid if you use a copy and paste operation to copy data from Microsoft Word or from Microsoft Excel.
After you install the hotfix that is described in this article, the Vssconverter.exe file uses a period (.) character to replace incorrect control characters from the labels and from the label comments. The following control characters are not replaced:
- Tab (\t)
- CR (\r)
- LF (\n)
- 0xFFFE and 0xFFFF
When the Vssconverter.exe utility uses the period character to replace a character, a warning message is logged to the Vssconverter.exe utility log file. This warning message states that a comment that was not valid was changed to a valid comment.
For more information about how to use the Vssconverter.exe command-line utility, visit the following Microsoft Developer Network (MSDN) Web site:
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the standard terminology that is used to describe Microsoft software updates