Mercurial/Python process ends with return code 128

SCM-Manager Bug Reports SCM-Manager
1

Our legacy software uses SCM Manager v1.20 that is hosted using Windows Server 2003.

Recently, we are seeing the following error: “Mercurial/Python process ends with return code 128.”

The error typically shows up after a push/pull to SCM. The error occurs in both command line and a mercurial GUI such as TortoiseHg.

The error takes a minute or two to clear. Once it clears, we can typically perform one or two push/pulls before the error pops up again.

I’m thinking that we may be overloading the port socket and the server is forcibly closing the port? Is there any way to fix this error?

We are already planning an upgrade to a newer server and version of SCM. However, some of our legacy software requires the SCM v1.20.

2

Thank you for reaching out! Unfortunately, we no longer support version 1.x. We kindly recommend upgrading to the latest version. If possible, we also suggest migrating to a Linux system for the best experience.

Here’s a migration guide from v1 to v3 https://scm-manager.org/docs/3.7.x/en/migrate-scm-manager-from-v1/