Formula una domandaFormula una domanda
 

Con rispostaError 0x80072F7D

  • venerdì 31 agosto 2007 14.25eheath Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     

    Hello.

     

    I am getting the following error from VS 2005 when using Internet Connection to VSS 2005.

     

    The server returned the following error: An error occurred in the secure channel support (0x80072F7D)

     

    I have read the other posts but they have not helped.

    Re: Test install on Sharepoint...  

    Using VSS on a different port 

     

    Re: Test install on Sharepoint...  

    Using VSS on a different port 

     

    I am not using SSL.

    I am using Share Point on the same server.

    Windows 2003

     

    1. VSS Admin - Server - Config

    Enable SourceSafe Internet for this computer

    Enable SourceSafe Internet for this database

    xxx.xxx.xxx.xxx:777

    2. VSS Admin - Tools - Options

    Use network name for automatic login

     

    3. IIS

    Virtual Application

    Path: C:\Program Files\Microsoft Visual SourceSafe\VssWebService

    Read Access

    Application Name: SourceSafe

    Script Only

    ASP.NET 2.0

    Directory Security is Integrated Security

    Two virtual directories

    VssUpload_db1   \\grant\vss\VssWebUpload

    VssDownload_db1  \\grant\vss\VssWebDownload

     

    4. Web.config

    <?xml version="1.0"?>
    <configuration>
     <system.web>
      <customErrors mode="Off"/>
      <authentication mode="Windows"/>
      <identity impersonate="true"/>
      <authorization>
       <allow users="*"/>
      </authorization>
      <trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true"/>
      <sessionState mode="Off"/>
      <globalization requestEncoding="utf-8" responseEncoding="utf-8"/>
      <httpRuntime executionTimeout="1800"/>
      <webServices>
       <protocols>
        <!-- This disables the service help and generated WSDL pages. -->
        <!-- <remove name="Documentation"/>  -->
       </protocols>
      </webServices>
     </system.web>
     <appSettings><add key="\\grant\vss" value="DatabasePath"/></appSettings></configuration>

     

    5. srcsafe.ini

     

    Has the following specified
    DownloadVDir = VssDownload_db1
    UploadVDir = VssUpload_db1

    Web_Service = http://xxx.xxx.xxx.xxx:777/SourceSafe/VssService.asmx

     

    6. Permissions are set on the vss share

     

    I am able to see all the web service methods locally and remotely

    http://localhost:777/sourcesafe/vssservice.asmx

     

    7. Visual Studio 2005

    Is unchecked to use SSL.  If this is checked I get the same error when connecting but it gives me the extra information about checking this setting.

     

    Does anybody have any suggestions?  What does this error really mean?

     

    Thanks!

Risposte

  • martedì 4 settembre 2007 0.27eheath Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     Con risposta

    Thanks for the suggestion about Sharepoint. 

     

    Come to find out the problem is related to the application pool settings. 

     

    The SourceSafe Virtual Directory was using an application pool called "fogbugz" that I had created to run a web based bug tracking system.  I assume this application pool was using an user account that did not have access to VSS.

     

    I created a new application pool called "ASP.NET V2.0" using the Indentity of predefined "Network Service" and now I am able to connect from the client.

     

    Hope this helps someone else.

Tutte le risposte

  • sabato 1 settembre 2007 19.31Alin ConstantinMSFT, ModeratoreMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     
    There was a known issue with Sharepoint + VSS on the same server, if Sharepoint is incorrectly configured/installed into the root of the website (but I don't remember if 0x80072F7D was the error message we saw in that case)

     

    The problem was that Sharepoint had its own web.config in the root of the website, and the setting there were inherited by child nodes (like /SourceSafe), interacting badly with SourceSafe's settings.

     

    The recommended solution was to reinstall/configure Sharepoint to run in it's own subfolder instead of the root of the website.

     

    Alin

  • martedì 4 settembre 2007 0.27eheath Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     Con risposta

    Thanks for the suggestion about Sharepoint. 

     

    Come to find out the problem is related to the application pool settings. 

     

    The SourceSafe Virtual Directory was using an application pool called "fogbugz" that I had created to run a web based bug tracking system.  I assume this application pool was using an user account that did not have access to VSS.

     

    I created a new application pool called "ASP.NET V2.0" using the Indentity of predefined "Network Service" and now I am able to connect from the client.

     

    Hope this helps someone else.

  • mercoledì 15 aprile 2009 14.31Ross Holder Medaglie utenteMedaglie utenteMedaglie utenteMedaglie utenteMedaglie utente
     

    In fact, it did!  Thanks so much!  (Too often, people will solve the problem they post about and then either not post a reply - or even more frustrating - post a reply like "Solved it!  Thanks!" without advancing any further details; leaving us all with the knowledge that there is a solution, that someone else has it, but simply didn't share it....)


    Ross is a .NET developer based in Ottawa, Canada, working for Cactus Commerce with Microsoft.