Search:     Advanced search

Helix ALM Visual SourceSafe Integration

Article ID: 549  |  Last updated: 17 Jul, 2017

Helix ALM supports integration with Microsoft Visual SourceSafe (VSS).


  • The following information also applies to TestTrack 2016.1 and earlier. TestTrack was renamed to Helix ALM starting with version 2017.1.
  • VSS support is deprecated and will be discontinued in a future release. Consider using a different source control application.

This article includes information about integration requirements, configuring the integration, performing VSS actions, and troubleshooting.


  • Make sure you are using a supported VSS version.
  • The 32-bit Helix ALM Client must be installed. 
  • The VSS client must be installed and able to connect to the VSS database. The same connection as the client is used when setting up the connection information in Helix ALM.
  • If the VSS database is on another computer, you must be able to access it via My Computer. When setting up the connection information, you need to browse to the folder that contains the database folder. VSS must also be set as an SCC provider in the system registry.

Configuring the integration

Helix ALM

See the help for information about configuring the integration.

TestTrack 2016.1 and earlier

  1. In TestTrack, choose Tools > Source Control Integration. The Source Control Integration dialog box opens with the Provider category selected.
  2. Select Microsoft Visual SourceSafe and click Make Current.
  3. Select the Connection category.
  4. Click Browse and locate the srcsafe.ini file. This file contains the path to the 'data' folder, which is where the database is located. Usually this is a relative path to the srcsafe.ini file. For example, your srcsafe.ini file may specify Data_Path = data. This means the database is in a folder named data, which is located in the same directory as the file.
  5. Enter the VSS project Username and Password.
  6. Click Validate Connection to test the connection to the VSS database.
  7. Select the Project Options category.
  8. Enter any Default check in comments. You can use field codes to automatically add issue-related information to check in comments.
  9. Select the Project Paths category.
  10. Select the projects to attach files from and click Add.
  11. Click OK to save the changes.

Performing VSS actions

You can access the following VSS actions on the Source Files tab when editing items:

  • Attach File—Attaches VSS files to the item.
  • Detach—Removes attached VSS files from the item.
  • Get—Retrieves a read-only copy of the latest file version.
  • Check Out—Retrieves a writable copy of the file to the working directory for editing.
  • Undo Check Out—Removes the check out lock from VSS.
  • Check In—Submits changes to a checked out file to the VSS database. The version created by the check in is displayed in the Fixed Revision column on the item Source Files tab.
  • View Local Copy—Displays the content of the file in the working directory.
  • History—Displays the entire file history.


VSS not in the Available Providers list in TestTrack 2016.1 or earlier

TestTrack cannot locate VSS as an installed source control provider.

Check the registry to see if this VSS key exists:

  • 64-bit Windows—HKEY_LOCAL_MACHINE\Software\Wow6432Node\SoureCodeControlProvider\InstalledSCCProviders\Microsoft Visual SourceSafe
  • 32-bit Windows—HKEY_LOCAL_MACHINE\Software\SourceCodeControlProvider\InstalledSCCProviders\Microsoft Visual SourceSafe

If the key does not exist, reinstall VSS to add it.

If the key already exists, make sure the SCCServerName and SSCServerPath values are correct.

  1. Using the Registry Editor (regedit), browse to the VSS registry key.
  2. Note the key’s string value. For example, Software\MicrosoftSourceSafe.
  3. Browse to the registry entry you noted.
  4. Make sure the following strings exist and point to the correct location:
    • SCCServerName—String value is ‘Microsoft Visual SourceSafe’
    • SCCServerPath—String value is the location of the VSS SCCI interface .dll on local hard drive. For example, C:\Program Files\Microsoft Visual Studio\Common\VSSwin32SSSCC.DLL.
Article ID: 549  |   Last updated: 17 Jul, 2017
Visual SourceSafe VSS

Prev   Next
Surround SCM Not an Available Provider for Source Control...     TestTrack Cannot Load the Surround SCM SCCI Library on Linux