Protocol error running ScmBackup.exe

[fgonzalez-techmatters]

Hi!

We are having an issue while running the ScmBackup.exe:

The repositories that we are trying to backup are in Bitbucket. The software is running on Windows Server 2019, with .NET core 3.1 and Git installed by default. We tried to add the git.exe path to "scms" in setting.yml but the issue still persists.

Could you help us with this error? Thanks! Regards.

[krzysztofmajewski]

I have the same problem. Similar environment as @fgonzalezflx except for the Git version:

Found Git 2.26.0.windows.1

Note that this is a 32-bit version of Git.

[krzysztofmajewski]

Installed the latest 64-bit Git (2.27.0), configured scm-backup to use it: same error.

[christianspecht]

@krzysztofmajewski: Bitbucket as well?

---

It's interesting, together with #57 there are now 3 different people who all have the same problem, apparently all on Bitbucket.

• Did it work before and stopped working, or are you new SCM Backup users and it never worked?
• Can you try the steps SCM Backup does directly in Git, with the repo where the problem occured?

[fgonzalez-techmatters]

@krzysztofmajewski: Bitbucket as well?

It's interesting, together with #57 there are now 3 different people who all have the same problem, apparently all on Bitbucket.

• Did it work before and stopped working, or are you new SCM Backup users and it never worked?
• Can you try the steps SCM Backup does directly in Git, with the repo where the problem occured?

Thanks for you answers guys. Responding to @christianspecht , in my case im a new user. Following the steps in the link that you shared seems to work without issues:

If is not git, what might be causing the issue?

Regards!

[krzysztofmajewski]

@krzysztofmajewski: Bitbucket as well?

Yes, Bitbucket.

• Did it work before and stopped working, or are you new SCM Backup users and it never worked?

I'm a new SCM Backup user.

• Can you try the steps SCM Backup does directly in Git, with the repo where the problem occured?

Yes, will do.

[krzysztofmajewski]

Yes, will do.

Confirmed that the steps SCM Backup does directly in Git do succeed.

[krzysztofmajewski]

Update: I excluded the offending repo with ignoreRepos, and SCM Backup was able to process 11 other repos, before failing on the 12th one (not the same as the original offending repo).

[krzysztofmajewski]

Update: I repeatedly exluded all the repos that failed with the above error, until the backup completed. Out of 39 discovered repos, 17 failed with this error. The remaining 22 succeeded. These are private repos, but on request (and with your hints) I could poke around and try to see if there are any common differences between the failing repos and the others...

[christianspecht]

Sorry for the long delay - so far, I have no clue what could cause the problem, so I was not sure which questions to ask you.

Some ideas:

1. The Bitbucket account that you're backing up: user or team?
   I know it's somehow unified now with Bitbucket's move to workspaces, but was it a user or a team before?

2. Are you using Git only or did you have Mercurial repos until Bitbucket dropped support at July 1st?
   If you had Mercurial repos, did you delete them and then created new Git repos under the same name/URL? (and are those the ones that are failing now?)

3. I already asked you to try the steps SCM Backup does directly in Git, with the repo where the problem occured.
   Can you try this again, but this time from the directory where your local SCM Backup installation is?

[fgonzalez-techmatters]

Hi @christianspecht. Thanks for following this up. Answering your questions:

1. The Bitbucket account that you're backing up: user or team? It was a team account before.

2. Are you using Git only or did you have Mercurial repos until Bitbucket dropped support at July 1st? We only have git installed, never used Mercurial.

3. Can you try this again, but this time from the directory where your local SCM Backup installation is? We tried and seems to be working ok too:

[krzysztofmajewski]

In my case it's also a team account, and only using Git (not Mercurial). Less urgency on my end for this issue now as we have deployed a workaround (just cloning a fixed set of repos in a nightly script). Would be nice to have this ScmBackup working for the discovery part, though.