VSS-2005 access permission problem via HTTP

Hi,

I'm having a problem using VSS-2005 access via HTTP when the remote developer is simply a domain user. They can connect OK and navigate through the VSS folder structure, but when they try to open a project file, the following errors are produced:

 "The current source control operation cannot be completed. The Visual SourceSafe Web Service returned the following error: Attempted to perform an unauthorized operation"

 "The current source control operation cannot be completed. The source control plug-in returned the following error: Access failure."

The whole process works fine if I elevate the user up to domain admin. Also, when the user is on the local network, they have the same problem via HTTP access, but all is OK through normal fileshare access.

I have checked NTFS and web permissions on both the VSS web service and SourceSafe share and all seems OK to me (i.e. accessible from domain users), so can anyone let me know what I might have missed Is there a document or something which details each permission required here

Thanks

Simon



Answer this question

VSS-2005 access permission problem via HTTP

  • izm_ka

    I'm getting a similar error, but I don't get the VssWebUpload/Download in the URL.  I don't have the two virtual directories under the SourceSafe.  My error message is:

    There was a failure in uploading the URL
    http://192.168.0.150/SourceSafe//325e8...........

    Can you say why the upload/download stuff was not created


     Alfredo Mendez MSFT wrote:

    Hi Simon,

    I suspect this has something to do with the permissions of the virtual directories.

    On your default website, under SourceSafe you will see two virtual directories created, with names like: VssUpload_dbN & VssDownload_dbN

    Please bring up the properties for each and verify the following:
    * VssUpload allows writes and VssDownload allows reads.
    * VssUpload correctly points to your database location (e.g. \\server\vss\VssWebUpload) and that users of the database have r/w permissions to share, and r/w permission to the folder on disk
    * VssDownload correctly points to your database location (e.g. \\server\vss\VssWebDownload). and that users of the database have r/w permissions to share, and r/w permission to the folder on disk

    Let me know if that works for you,

  • Christian Warren

    I have exactly the same problem on my machine.

    I tried creating the directories, and VSS has placed the crazy guid files into them (I can see them in IIS Admin) but VS.NET still tries to download from http://my_server/SourceSafe//crazy_guid_here...

    How do I get the VssUpload_MyDbName into the url


  • Mark d Henning


    Hi Simon,

    I suspect this has something to do with the permissions of the virtual directories.

    On your default website, under SourceSafe you will see two virtual directories created, with names like: VssUpload_dbN & VssDownload_dbN

    Please bring up the properties for each and verify the following:
    * VssUpload allows writes and VssDownload allows reads.
    * VssUpload correctly points to your database location (e.g. \\server\vss\VssWebUpload) and that users of the database have r/w permissions to share, and r/w permission to the folder on disk
    * VssDownload correctly points to your database location (e.g. \\server\vss\VssWebDownload). and that users of the database have r/w permissions to share, and r/w permission to the folder on disk

    Let me know if that works for you,

  • ddwby

    Found a solution on the forums.

    http://forums.microsoft.com/msdn/ShowPost.aspx PostID=4906

    VSS had already created the folders in my database. It just hadn't set up the virtual directories in IIS or the entries in srcsafe.ini.

  • Baolin Ren

    Yes. Web service reset ACLs on these GUID named folders so that only this particular user has access to the files uploaded/downloaded. This is why it needs Full Access on the share.
  • Hamid Mahmood - MSFT

    Alfredo, the permissions were already as you stated, but while checking these, I noticed that the VSS share needs to have 'Full Control' permissions for the user, rather than just 'Change'. Seems strange that this was not required when opening the project directly on the share, rather than through http (maybe something to do with the guid-like directory created under VssWebDownload ).

    Anyway, thanks for your help.
    Simon

  • VSS-2005 access permission problem via HTTP