Visual SourceSafe 2005 Solution Center

Troubleshooting - Visual SourceSafe 2005

• PRB: How to Handle the "invalid serial number" Error
  The error "invalid serial number" occurs when a DEMO serial number has expired. Issue a updated serial number by following these steps: Run SERIALIZ on the computer with outdated serial number. For example: C:\SS\ADMIN\SERIALIZ <data directory>...
• BUG: SourceSafe Update Command Fails on Large Binary File
  A large binary file cannot be updated in SourceSafe. Insufficient resources to create the difference file. If it is not possible to increase the HMA by decreasing the number of drivers necessary for a given system, try putting all binary files in...
• PRB: Corrupt Binary File After Merging with SourceSafe
  A Binary file is corrupted after a merge is attempted. There are two scenarios where a merge can occur: Multiple_Checkouts = Yes in the SRCSAFE.INI or SS.INI file. -or-A binary file is separated and later merged. Binary files will become corrupt...
• Some paths that are not valid cannot be migrated from Visual SourceSafe to Visual Studio Team Foundation Server
  Describes a problem in which some paths that exist in VSS cannot be used in Visual Studio Team Foundation Server.
• List of bugs that are fixed in the Visual SourceSafe 2005 Update
  Provides a list of the bugs that are fixed in the Visual SourceSafe 2005 Update.
• List of bugs that are fixed in the Visual SourceSafe 2005 Update Community Technology Preview
  Provides a list of the bugs that are fixed in the prerelease version of the Visual SourceSafe 2005 Update.
• BUG: Error message when you use Visual SourceSafe Automation to access the VSSVersion.VSSItem property for a branched file in Visual SourceSafe 2005: "File or project not found"
  Describes a problem that occurs when you use Automation code to access the VSSVersion.VSSItem property of an object.
• FIX: The "ss Diff" command may incorrectly report file differences when you use the "ss Diff" command on certain file types in Visual SourceSafe 2005
  Fixes a problem in Visual SourceSafe 2005 in which the "ss Diff command" may incorrectly report file differences even though the files are identical.
• Data loss occurs when you use the VSSConverter.exe tool to migrate source code from Visual SourceSafe 2005 to Visual Studio Team Foundation Server
  Describes a problem in which data loss occurs when you use the VSSConverter.exe tool to migrate source code from Visual SourceSafe 2005 to Visual Studio Team Foundation Server.
• You cannot perform a project-level file check-in operation when you use a Visual SourceSafe 2005-based Automation program that uses OLE technology
  Fixes a problem in Visual SourceSafe 2005 in which you cannot perform a project-level file check-in operation when you use an Automation program that uses OLE technology.
• FIX: Error message when you try to add files to a Visual SourceSafe 2005 database or when you try to retrieve files from a Visual SourceSafe 2005 database by using Web access through HTTP: "Operation timed out"
  Describes a problem in which you may encounter a time-out issue when you try to add files to or retrieve files from a Visual SourceSafe 2005 database by using Web access through HTTP. Provides a hotfix that resolves the problem.
• FIX: Error message when you use the Get Latest Version option in Visual SourceSafe 2005 to try to obtain the latest version of an XML file: "SourceSafe was unable to finish writing a file"
  Fixes a problem that also occurs when you run an analysis report on the Visual SourceSafe database.
• Visual InterDev does not update Web pages in "Local mode" when you use Visual Source Safe 2005 to check out, update, and then check in the Web pages
  Describes an error that occurs when you use Visual InterDev in "Local mode." When you check out, update, and then check in Web pages by using Visual Source Safe 2005, the pages are not updated. Provides a resolution.
• BUG: The History dialog box does not appear in Visual SourceSafe Explorer when you use Visual SourceSafe 2005 on Windows 2000
  Discusses an issue that occurs when you right-click a file or a project. The Show History menu item does not work. Describes a workaround for this issue.
• FIX: You may receive an error message when you use Ole Automation to programmatically retrieve a specific version of a file from the history in Visual SourceSafe 2005
  Fixes a problem in Visual SourceSafe 2005 that causes an error message when you try to use the Get command to retrieve a specific version of a file from the history. This hotfix is not scheduled to be included in a service pack.
• You cannot host a Visual SourceSafe 2005 Web service on a computer that is running Windows Vista
  Discusses behavior that occurs because IIS 7.0 does not include the WebDAV component. You can put the Web service in an IIS virtual folder to work around this limitation.
• FIX: Visual SourceSafe 2005 may stop responding (hang) when you check in a large binary file
  Describes a problem in Visual SourceSafe 2005. It takes a long time for you to check in large binary files, and Visual SourceSafe 2005 may stop responding. A hotfix is described.