Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved Cannot connect to the repository (2)

  1. Issue
0
Votes
Undo
  1. Bas Oversteegen
    Bas Oversteegen
  2. PowerBuilder
  3. Monday, 14 February 2022 13:32 PM UTC

I have the same problem as described in https://community.appeon.com/index.php/qna/q-a/cannot-connect-to-the-repository , that is I can't connect to my repository specified in the Workspace Source Control Properties for Git. I get the same 2 error messages. But in my case it is not a proxy problem because I have no proxy specified.

Used products:

Windows 10, BitBucket, PowerBuilder 2021 build #1288, Git-2.35.1.2-64-bit, TortoiseGit-2.13.0.1-64bit

What I did to try to solve the problem:

(A)

- Initial situation is with TortoiseGit, Git and PowerBuilder installed (versions mentioned above)

- Deinstall TortoiseGit, Git and PowerBuilder

- Cleanup registry and temporary files with CCleaner

- Install PowerBuilder

In Source Control properties of workspace the User ID and Password are now empty, but when specifying them with the correct values of my BitBucket account I get the same error as before, and the properties won't save these newly specified values.

(B)

Starting with situation after (A), I installed Git and TortoiseGit. Pull and push with TortoiseGit work fine, but still the same problem with the PowerBuilder workspace source control properties.

(C)

I tried (A) and (B) with different versions of Git and TortoiseGit with the idea that it might be a credential manager issue (Windows Credential Manager versus Credential Manager Core). In my Windows settings I deleted the 'Git:' references used by the now outdated Windows Credential Manager. I also updated to Windows 11.

Same error in situations  (A), (B) and (C). How to reset the workspace source control properties such that the connect succeeds? Is there perhaps a related entry in the Windows registry or PowerBuilder ini files?

 

How can i have different instances of my PowerClie...
What version numbering scheme do people use for th...
Accepted Answer
Bas Oversteegen
Bas Oversteegen Accepted Answer Pending Moderation
  1. Thursday, 17 February 2022 09:07 AM UTC
  2. PowerBuilder
  3. # Permalink

Thanks for the suggestions. But fortunately I found the cause of the problem:

In TortoiseGit I had the following annoying warning when performing a pull/push:

git: 'credential-manager' is not a git command. See 'git --help'. The most similar command is credential-manager-core

To get rid of it I executed the following code in a CMD box:

git credential-manager-core configure

This killed the error in TortoiseGit where pull/push still works fine. However it also confuses PowerBuilder which no longer understands the credentials in the source control properties for system Git and generates a 'generic error' when performing a pull/push. As of that moment deinstallation of TortoiseGit, Git and PowerBuilder, and then reinstalling them doesn't work, deleting the 'git:...' credentials in the Windows Credential Manager doesn't work, reverting Windows to a system restore point previous to my git command doesn't work. The only thing that worked was a reinstall of Windows. Apparently there somewhere somehow is a persistent credentials setting in Windows. I couldn't figure out the correct CMD git command to get rid of the annoying warning in TortoiseGit while not destroying the source control functionality in PowerBuilder. So I decided to keep the warning.

Now source control in PowerBuilder works fine again. The app versions I use are: Windows 11, BitBucket Cloud, PowerBuilder 2021 build #1288 (#1506 also works fine), Git-2.35.1.2-64-bit, TortoiseGit-2.13.0.1-64bit. When I 'Connect to Workspace' in PowerBuilder, for the source control properties I can specify 'basic' or 'token' for the Authentication Type, my BitBucket Cloud account username for the User ID, and my BitBucket Cloud account password or an App password for the Password/Token. So everything is OK now, also from March on it probably will be fine because I can use an App password.

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Thursday, 17 February 2022 19:21 PM UTC
Thanks for sharing Bas!
  1. Helpful
There are no comments made yet.
Responses (3)
Tom Jiang @Appeon
Tom Jiang @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 15 February 2022 01:11 AM UTC
  2. PowerBuilder
  3. # 1

If you are using username and password authentication, please check if your password contains any character that is not on a standard US keyboard. We had a case where it failed to connect to the server when there is the character "§" in the password. I suggest that you test with an account that doesn't use any special characters in the password.

 

As suggested by Miguel, you may try using PAT as the user name and password if you haven't already tried that.

 

Regards,

 

Tom Jiang

Comment
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 14 February 2022 17:19 PM UTC
  2. PowerBuilder
  3. # 2

Have you tried specifying the PAT (token) that you fill in in the password field also for the user field?

Comment
Load more comments
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Tuesday, 15 February 2022 12:08 PM UTC
" BitBucket Cloud (uses account passwords until march 2022; and App Passwords, mandatory as of march 2022)" - I don't understand, we're still in February.

Does Bitbucket Cloud ALLOW accessing with PAT already? Try creating it and use it, who knows if PB no longer supports anything else than tokens ...

Good luck!
  1. Helpful
Bas Oversteegen
  1. Bas Oversteegen
  2. Tuesday, 15 February 2022 14:13 PM UTC
To clarify:

The combination BitBucket username (account name) and account password suddenly doesn't work anymore in PowerBuilder. This is the main problem. If I get this to work I'm happy, but only for now, because BitBucket Cloud will no longer support account verification (via account username and password) as of march 2022. Form march on we will have to use App Passwords. These are already supported by BitBucket Cloud, but currently do not work in PowerBuilder. BitBucket Cloud uses and will use App passwords only whereas BitBucket Server uses and will use HTTP Access tokens (i.e.PAT) only.
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Tuesday, 15 February 2022 14:21 PM UTC
Ok, I see. Maybe it's a good idea to create a support ticket for this one https://www.appeon.com/standardsupport/newbug, with a pasted link to this post so you don't have to repeat yourself.

regards.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.