Problems on Working with Version Control System (VCS)

Problem

Selecting a local folder with repository clone or getting the latest object version returns the Access Denied, Push Failed, and Fetch Failed errors.

Cause

The errors are caused by absence of access permissions to connect to GIT repository or by the two-factor authentication if connection to a GitHub account is being executed.

Solution

To solve the problem:

• Make sure that the application is started under the operating system user who has administrator permissions. If credentials that are used to connect to GIT repository differ from the current operating system user, change the line in the configuration file S\.git\config, where S - path to the local cloned repository:

[remote "origin"]

url = https://<repository URL>

to:

[remote "origin"]

url = https://<login>:<password>@<repository URL>

• If a connection to version control system is being executed, in which personal access tokens (PAT) are set up, replace the string with:

[remote "origin"]

url = https://<login>:<user token>@<repository URL>

Personal tokens are created in different ways and depend on the version control system in use. For details see corresponding documentation: Azure DevOps, GitHub, GitLab.

• If the user works in Windows OS, and storing of login and password in open form in files is forbidden, credentials can be saved in the operating system credential manager. To do this:

1. Open the control panel in Windows OS and open the User Accounts section.

2. In the left part of the window click the Manage Your Credentials link to open the credential manager.

3. Click the Windows Credentials button.

4. In the Generic Credentials group click the Add a Generic Credential link, then specify full path to the repository, user login and password:
   

5. Click the OK button to save the credentials.