Uploaded image for project: 'Sourcetree for Windows'
  1. Sourcetree for Windows
  2. SRCTREEWIN-6512

Not working with Team Services (former Visual Studio Online) via SSH

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • None
    • None
    • Severity 3 - Minor

      I try to clone a repository from Team Services (former Visual Studio online), but I receive the following error:

      System.ComponentModel.Win32Exception: The system cannot find the file specified
      FATAL ERROR: Server sent disconnect message
      type 2 (protocol error)
      "Invalid packet"

      I'm using Putty, I double-checked - the correct SSH key is loaded. SSH access to my BitBucket account using the same key is working. Another Git application (GitExtensions) works with this key and this repository. I tried several repositories from different Team Services accounts and the same error appears on all of them.

        1. Screenshot_1.png
          Screenshot_1.png
          14 kB
        2. Screenshot_2.png
          Screenshot_2.png
          19 kB

            [SRCTREEWIN-6512] Not working with Team Services (former Visual Studio Online) via SSH

            We are looking into this issue.

            Mukesh Kumar (Inactive) added a comment - We are looking into this issue.

            Seems the solution was already found, and is being implemented.
            See this issue:
            https://jira.atlassian.com/browse/SRCTREEWIN-8035

            Hans Gregersen Jensen added a comment - Seems the solution was already found, and is being implemented. See this issue: https://jira.atlassian.com/browse/SRCTREEWIN-8035

            I am thinking the problem can be solved by simply updating putty in the sourcetree installer.

            Original version:

            > plink.exe -V

            plink: Unidentified build, Apr 16 2013 12:55:41

            New version:

            > plink.exe -V

            plink: Release 0.70
            Build platform: 64-bit Windows
            Compiler: clang 5.0.0 (http://llvm.org/git/clang.git dba970f4d143480b964f77b363ec23f22cea0390) (http://llvm.org/git/llvm.git 52ebe03cb0a728134e66d04f85281bc5a60d7091), emulating Visual Studio 2013 / MSVC++ 12.0 (_MSC_VER=1800)
            Source commit: 3cd10509a51edf5a21cdc80aabf7e6a934522d47

            Hans Gregersen Jensen added a comment - I am thinking the problem can be solved by simply updating putty in the sourcetree installer. Original version: > plink.exe -V plink: Unidentified build, Apr 16 2013 12:55:41 New version: > plink.exe -V plink: Release 0.70 Build platform: 64-bit Windows Compiler: clang 5.0.0 ( http://llvm.org/git/clang.git dba970f4d143480b964f77b363ec23f22cea0390) ( http://llvm.org/git/llvm.git 52ebe03cb0a728134e66d04f85281bc5a60d7091), emulating Visual Studio 2013 / MSVC++ 12.0 (_MSC_VER=1800) Source commit: 3cd10509a51edf5a21cdc80aabf7e6a934522d47

            Hans Gregersen Jensen added a comment - - edited

            Hi @blloyd

            This has been bugging me for a long time.

            Finally found a usable workaround.

            1. Open the folder %appdata%\..\local\sourcetree\app-<version>\tools\putty
            2. Overwrite the files here, with appropriate files from c:\program files\putty (mine are version 0.70 x64)

            Hans Gregersen Jensen added a comment - - edited Hi @blloyd This has been bugging me for a long time. Finally found a usable workaround. Open the folder %appdata%\..\local\sourcetree\app-<version>\tools\putty Overwrite the files here, with appropriate files from c:\program files\putty (mine are version 0.70 x64)

            While the work-around works fine if this is the ONLY repository that must be accessed, or if all ssh access will be via SSH keys.  This work-around does not work when you have multiple ssh repositories to access including at least one that does not support ssh key access.  In that case, enabling OpenSSH breaks the password only ssh repo.  (And yes, this break is more than just academic for me.)

            Brian Alan Lloyd added a comment - While the work-around works fine if this is the ONLY repository that must be accessed, or if all ssh access will be via SSH keys.  This work-around does not work when you have multiple ssh repositories to access including at least one that does not support ssh key access.  In that case, enabling OpenSSH breaks the password only ssh repo.  (And yes, this break is more than just academic for me.)

            I have the same issue, this happens when you use PuTTY as you SSH manager

            Change it to OpenSSH and it works

            Youssef Shahin added a comment - I have the same issue, this happens when you use PuTTY as you SSH manager Change it to OpenSSH and it works

              Unassigned Unassigned
              jyowell Jesse Yowell (Inactive)
              Affected customers:
              8 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated: