|
| 1 | +--- |
| 2 | +title: Troubleshooting |
| 3 | +category: getting-started |
| 4 | +order: 60 |
| 5 | +--- |
| 6 | + |
| 7 | +The most common issues with abapGit are listed here |
| 8 | + |
| 9 | +## Connection Types |
| 10 | + |
| 11 | +There are several ways to connect from your SAP system to a git server. For example: |
| 12 | + |
| 13 | +- SAP System > HTTP/S > Git Server |
| 14 | +- SAP System > HTTP/S > Proxy > Git Server |
| 15 | +- SAP System > Exit( RFC Destination ) > HTTP/S > Git Server |
| 16 | +- SAP System > Exit( RFC Destination + Proxy ) > HTTP/S > Git Server |
| 17 | + |
| 18 | +Be sure to check all areas. |
| 19 | + |
| 20 | +## HTTP Errors |
| 21 | + |
| 22 | +### 401 - Unauthorized and 403 - Forbidden |
| 23 | + |
| 24 | +Reading public repositories typically does not require authentication to the git server. However, accessing private repositories or trying to update repositories in general will require authentication. |
| 25 | + |
| 26 | +- Check your user and password |
| 27 | +- Check if the server requires a token as the password (for example, GitHub) |
| 28 | +- Test your credentials using a command line tool (git, curl, etc) |
| 29 | + |
| 30 | +### 404 - Not Found |
| 31 | + |
| 32 | +- Check if the git servers requires `.git` at the end of the repository URL (for example, GitLab) |
| 33 | +- Check if it's a private repository that requires authentication |
| 34 | + |
| 35 | +### 407 - Proxy Authentication Required |
| 36 | + |
| 37 | +Also: `ICM_HTTP_SSL_ERROR`, `SSSLERROR_SSL_READ`, `SSSLRC_CONN_CLOSED` |
| 38 | + |
| 39 | +- Check the proxy configuration in abapGit [Global Settings](/user-guide/setup/settings-global.html) |
| 40 | +- Check the [SSL Setup](/user-guide/setup/ssl-setup.html) |
| 41 | +- Use the [SSL Test Tool](/user-guide/setup/ssl-test.html) to verify the connection |
| 42 | + |
| 43 | +### 411 - Connection Failed |
| 44 | + |
| 45 | +Also: `NIECONN_REFUSED` |
| 46 | + |
| 47 | +- Check SAP system parameters in [SAP Note 510007](https://me.sap.com/notes/510007) |
| 48 | + |
| 49 | +### 421 - Misdirected Request |
| 50 | + |
| 51 | +Also: `ICM_HTTP_SSL_PEER_CERT_UNTRUSTED`, `SSSLERR_PEER_CERT_UNTRUSTED` |
| 52 | + |
| 53 | +- Check the [SSL Setup](/user-guide/setup/ssl-setup.html) |
| 54 | +- Use the [SSL Test Tool](/user-guide/setup/ssl-test.html) to verify the connection |
| 55 | + |
| 56 | +## SAP GUI |
| 57 | + |
| 58 | +Try to run the latest version of SAP GUI. Older version are known to have issues. SAP GUI for Windows is the most used and tested client. |
| 59 | + |
| 60 | +- Check the [SAP GUI Setup](/user-guide/setup/sapgui.html) |
| 61 | + |
| 62 | +## Supported Object Types |
| 63 | + |
| 64 | +Which object types are supported in your system depends on the combination of abapGit and SAP releases. |
| 65 | + |
| 66 | +- Check "Debug Info" from the tools menu on the repository overview (shows the object types supported in your system) |
| 67 | +- Check the [List of Supported Object Types](/user-guide/reference/supported.html) (most recent release) |
| 68 | +- Check [Requests for Supporting New Object Types](https://github.com/abapGit/abapGit/issues/5912) (unchecked means "not supported") |
| 69 | + |
| 70 | +## User Exits |
| 71 | + |
| 72 | +Behaviour of abapGit can be changed using [User Exits](/user-guide/reference/exits.html). |
| 73 | + |
| 74 | +- Check "Debug Info" from the tools menu on the repository overview (shows which exits are active in your system) |
| 75 | +- In case of issues, deactivate all exits to narrow down the root cause. |
| 76 | + |
| 77 | +## SAP ABAP Development Tools (ADT) |
| 78 | + |
| 79 | +If you are using the ADT abapGit plugin provided by SAP, check [SAP BTP, Working with abapGit](https://help.sap.com/docs/btp/sap-business-technology-platform/working-with-abapgit). |
| 80 | + |
| 81 | +## SAP Cloud Solutions |
| 82 | + |
| 83 | +You can find tips for connections from SAP Cloud solutions [here](https://github.com/abapGit/abapGit/issues/6206#issuecomment-2047638552). |
0 commit comments