--- article_id: KB0402310 article_type: Support Note component_ids: - BNS-ARI-CI-PLT-CON - BNS-ARI-CI-PRT component_descriptions: - SAP Integration Suite, managed gateway > Managed Gateway - Platform > Managed Gateway - Buy side Connectivity - SAP Integration Suite, managed gateway > Managed Gateway - Portal products: - SAP Ariba Procurement, cloud edition - SAP Ariba Sourcing, cloud edition - SAP Business Network for Procurement and SAP Business Network for Supply Chain personas: - Admin - Buyer language: en created: 2026-07-15 updated: 2026-07-15 source: Knowledge Base url: https://support.ariba.com/item/view/KB0402310 connect_url: https://support.ariba.com/item/view/KB0402310?min=1 sap_for_me_url: https://me.sap.com/notes/KB0402310 --- # Error: "Fault response received from ANXXXXXXXXXXX with ErrorCode: CIG-PLT-00676" in Managed Gateway for Spend&Network ## Symptom When sending a transaction from SAP Ariba to SAP ERP or S/4 HANA via SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network, the following error is triggered in Transaction Tracker: Fault response received from: ANXXXXXXXXXXX-T for:ANXXXXXXXXXXX-T with Status: FAILED and ErrorResponse:XXXX Suggested Action : Please contact support with ErrorCode:CIG-PLT-00676. ## Cause The cause and resolution depend on the actual error response that is seen next to ErrorResponse: message. Follow resolutions below according to the ErrorResponse details. ## Resolution Error 1: Fault response received from: ANXXXXXXXXXXX for:XXXXX with Status:FAILED and ErrorResponse:Service Unavailable. There is no SAP Cloud Connector (SCC) connected to your subaccount matching the requested tunnel for subaccount "a8f3ed22c" and SCC location ID "XXXXX". Check the configuration on SCC and cloud side... Suggested Action : Please contact support with ErrorCode:CIG-PLT-00676. - Solution to follow: [3294218 - Managed Gateway for Spend&Network transactions are failing with "Error: There is no SAP Cloud Connector (SCC) connected to your subaccount](https://me.sap.com/notes/3294218/E) Error 2: There is no SAP Cloud Connector (SCC) connected to your subaccount matching the requested tunnel for subaccount 6ba78e41-6aed-4051-82c8-dda98a594023" and SCC location ID CIGCF123. Check the configuration on SCC and cloud side. while posting to customer AN12340001234-T target system with HTTP ResponseCode:503.. Suggested Action : Connectivity to target system failed due to missing SAP Cloud Connector (SCC) connection. ErrorCode:CIG-PLT-04640. Please review following Support KBA for solutions ( [https://me.sap.com/notes/3763212](https://me.sap.com/notes/3763212) ). For further assistance, please opening a support ticket with the component BNS-ARI-CI-PLT-CON. - Solution to follow: [3763212 - Transactions are failing after SAP Integration Suite Managed Gateway migration to SAP BTP Cloud Foundry](https://me.sap.com/notes/3763212/E) Error 3: Fault response received from: ANXXXXXXXXXXX for:XXXXX with Status:FAILED and ErrorResponse:Bad Gateway. Invalid server certificate.. Suggested Action : Please contact support with ErrorCode:CIG-PLT-00676. - Solution to follow: [3156901 - 502: Bad Gateway. Invalid Server certificate when connecting with Cloud Connector to an on-premise SAP system](https://me.sap.com/notes/3156901/E). Error 4: Fault response received from: ANXXXXXXXXXXX for:XXXXX with Status:FAILED and ErrorResponse:Bad Gateway. Unable to open connection to backend system.. Suggested Action : Please contact support with ErrorCode:CIG-PLT-00676. - Solution to follow: [3218619 - Unable to open connection to backend system: Connection refused: no further information](https://me.sap.com/notes/3218619/E) Error 5: Fault response received from: ANXXXXXXXXXXX for:XXXXX with Status:FAILED and ErrorResponse:Error reading XMLStreamReader: Unexpected character 'j' (code 106) in prolog; expected '\<' at \[row,col {unknown-source}\]: \[1,1\].. Suggested Action : Please contact support with ErrorCode:CIG-PLT-00676. - Solution to follow: In above case there is an error response but not in XML format. Most common issue could be related to SAP Cloud Connector. We recommend checking cloud connector trace logs for more details. Related common issue KBAs below: - [Transaction fails with error: "Error reading XMLStreamReader: Unexpected character 'j'"](https://me.sap.com/notes/3189765/en) - [Error: “Error reading XMLStreamReader: Unexpected character 'j'”](https://me.sap.com/notes/3181302/en) - In case no errors in cloud connector logs, enabling **Payload Trace** option temporarily under SAP Cloud Connector > **Logs and Traces** and reproducing issue could provide complete details of this error response. Trace file format: traffic\_trace\_XXXXX\_hana.ondemand.com.trc. Note: Switch off Payload trace after collecting the required details as it could slow down cloud connector performance. Error 6: Fault response received from: ANXXXXXXXXXXX for:XXXXX with Status:FAILED and ErrorResponse: .. Suggested Action : Please contact support with ErrorCode:CIG-PLT-00676. - Solution to follow: In above case the error response content is Could not send Message. Click on the **Download** button in the log message pop up. If log contains the text org.apache.cxf.transport.http.HTTPException: HTTP response '503: Service Unavailable Timed out waiting for tunnel to open for tunnelId account:///\*\*\*' when communicating with [https://ADDRESS](https://address/)\_IS\_SET\_VIA.HEADER, follow [3524076 - 503: Service Unavailable Timed out waiting for tunnel account](https://me.sap.com/notes/0003524076/en) - If there is no **Download** button available in the log message, then the error response content is empty i.e. null. Reason could be destination or ERP application encountered application error or dump. In such cases check in ERP SRT\_MONI, SRT\_LOG, SLG1, ST22, SMICM logs and for Purchase Requisition transactions capturing SRT\_UTIL trace during timestamp when transaction flow towards ERP failed in Managed Gateway for Spend&Network portal **Transaction Tracker**. If any middlebox like web dispatcher etc. check relevant logs. Error 7: Fault response received from: ANXXXXXXXXXXX for:XXXXX with Status:FAILED and ErrorResponse: Request Too Long. Request Too Long. \\\\\soap:Server\\An internal error occurred. For error details check MPL ID XXXXXXXXXXXXXXXXXXXXXXXXXXXX in message monitoring or use the URL XXXXXXXXXXXXXXX to directly access the error information.\\\\.. - Solution to follow: make sure that the target system is properly configured to receive payloads with the size which is being sent. Ideally, the whole end-to-end integration should be configured with equal parameters regarding the size of allowed requests. Error 8: Fault response received from: ANXXXXXXXXX for:ANXXXXXXXXXX with Status:FAILED and ErrorResponse:Could not send Message... - Solution to follow: In above case the error response content is Could not send Message. Click on the **Download** button in the log message pop up. If log contains the text org.apache.cxf.transport.http.HTTPException: HTTP response '401: Unauthorized' when communicating with [https://ADDRESS](https://ADDRESS)\_IS\_SET\_VIA.HEADER, follow [Documents failing in transaction tracker with Error: " HTTP response 401: Unauthorized" from Business Network](https://me.sap.com/notes/3450801/en) ## Keywords Cig, cpi, mb, kb, btp