Sourcesafe-related Error when opening project in BIDS - VSS bindings are lost

  • I have been getting this error lately, and I don't know what to make of it.

    My project's bindings to VSS seem to be lost.

    How can I fix this?

    Here is the error (also attached):

    The source control provider associated with this solution cannot be found. The projects will be treated as not under source control. Do you want to permanently remove the source control bindings from the projects?

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • Sounds like perhaps your VSS database has been corrupted. Do you have admin rights to your VSS database? Can you log into it with the VSS Admin tool and analyze your database?

    Open the VSS database directly with SourceSafe and see if your project is still there. If not consider the following...Do you share this VSS database with other users who may have deleted your project from the VSS db?

    -Luke.

    To help us help you read this[/url]For better help with performance problems please read this[/url]

  • I found the problem.

    I was somehow missing the following 2 registry entries. After adding, the VSS bindings are restored.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SourceSafe\SCCServerName - value: Microsoft Visual SourceSafe

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SourceSafe\SCCServerPath - value: path for file ssscc.dll

    See http://msdn.microsoft.com/en-us/library/bb166193(VS.80).aspx for more info.

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

  • Luke L (12/31/2008)


    Sounds like perhaps your VSS database has been corrupted. Do you have admin rights to your VSS database? Can you log into it with the VSS Admin tool and analyze your database?

    Open the VSS database directly with SourceSafe and see if your project is still there. If not consider the following...Do you share this VSS database with other users who may have deleted your project from the VSS db?

    -Luke.

    Thank you, thankfully, my db does not appear to be corrupted.

    __________________________________________________________________________________
    SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
    Persisting SQL Server Index-Usage Statistics with MERGE[/url]
    Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply