Troubleshooting¶
In this section, you will find steps to troubleshoot issues while running the SAP extractor.
Common connectivity issues¶
Before starting the extraction routines, the SAP extractor performs a connection check to all configured endpoints.
ConnectTimeout¶
requests.exceptions.ConnectTimeout: HTTPConnectionPool(host=gateway_url, port=port): Max retries exceeded with url: /sap/opu/odata/sap/YOURSERVICE
This error occurs when the SAP extractor can't reach the configured SAP gateway, and the connection ends in a timeout. To solve this error, make sure the extractor can access the SAP OData gateway instance, for instance via the firewall, VPN, or SAP WebDispatcher.
401 Logon Failed¶
RuntimeError: Could not connect to SAP Gateway https://yourgatewayurl : Status Code 401 Logon failed
This error occurs when the extractor can't authenticate to SAP. Review the client, username, and password configuration parameters.
403 No service found¶
RuntimeError: Could not connect to SAP Gateway https://yourgatewayurl: Status Code 403 No service found for namespace '', name 'YOURSERVICE', version '0001'
This error occurs when the endpoint configured doesn't exist in SAP. Review the configuration in the endpoints section.
RuntimeError: 1 (rc=1): key=RFC_COMMUNICATION_FAILURE¶
RuntimeError: 1 (rc=1): key=RFC_COMMUNICATION_FAILURE, message=
LOCATION CPIC (TCP/IP) on local host with Unicode
DETAIL NiBufIConnect: connection pending after 60000m
rfc SAP source.
To solve this error, make sure the extractor can access the SAP server, for instance via the firewall, VPN, or SAP WebDispatcher.
Common data extraction issues¶
AttributeError: Entityset XXX not defined¶
This error occurs when the configuration parameter sap_entity for the related endpoint configuration is incorrect. You must use avalid entity name.
Maximum string length Error (OData endpoint)¶
This is a limitation in SAP OData endpoint related to the size of the OData object in the response. This error is likely to happen when running the extractor in full load mode (incremental_field is not configured)Extractor might enter in a "loop" state when using incremental_field (Custom OData endpoints)¶
The SAP extractor uses OData $skip and $top operations in order to handle pagination. Therefore, when setting up the SAP extractor towards a custom SAP OData endpoint, make sure that your SAP implementation supports pagination.