Table of Contents
| Table of Contents |
|---|
Error message: "Message processing in SAP PO failed" for a new configuration object or running existing SAP PI/PO unit test type
...
Error message: "SAP PO outbound message after mapping not found" while running a SAP PO Outbound test case.
...
The messages are visible in SAP PO monitoring; however, Int4 Suite can't fetch them.
By default Int4 Suite only searches messages which were pushed on SAP PO during the last 10 seconds. However, the time is taken from the system on which the Int4 Suite is installed (for example, Solution Manager). In case the timezones of Solution Manager and SAP PO are different, you need to increase the property - SRCH_TRS_O to make up for the time difference /wiki/spaces/IUM/pages/50195
Error message: "Output message has same interface as input"
...
Error message: "ABAP stack: function module SXMB_GET_MESSAGE_LIST returned execution error 5"
Error 5 stands for 'others' in function module signature. The most probable reason for the message is an unreachable RFC destination. In this case, you should ensure that destination is maintained correctly → SAP PI ABAP stack configuration
...
And fill the table this way with your external service desk guid:
...
Error message: "XML element, Envelope missing in SOAP message header (SAP XI Extension)"
...
Please make sure that the following two services are activated in SICF:
sap/public/bc/icons
sap/public/bc/webicons
Error message: " Internal Error 500 error " when opening transaction SOAMANAGER on the sandbox system
Suppose Int4 Suite is installed on a new sandbox system. In that case, there is a high possibility that WebDynpro applications and SOAMANAGER are not activated. After SOAMANAGER activation in transaction SICF in the following path /default_host/sap/bc/webdynpro/sap/APPL_SOAP_MANAGEMENT you still get error "Internal Error 500 " after successful login in SOA Manager.
To solve this problem:
Execute report rsicf_service_activation with the option WEB DYNPRO ABAP to make sure that Webdynpro applications will run properly. ( SAP Note 1088717).
In transaction SICF, activate the following path and all services below: /sap/bc/srt (SAP Note 1124553).
Error message: "SRT Framework exception: Service Ping ERROR: Error when calling SOAP Runtime functions: SRT Couldn't create Object: ("ICF error when creating HTTP client object by config for url" when creating ports via Int4 Suite configuration wizard or manually in SOAMANAGER
...
Suppose Int4 Suite is installed on a new sandbox system. In that case, there is a high possibility that you will get the above error message. The reason is that there is no valid certificate for SSL Client (Anonymous) in transaction STRUST.
To solve this problem, please make sure that:
In the RFC connection for your SAP PI/PO, you use a user with the necessary authorization
Download the relevant certificate from your SAP PI/PO and then import it in transaction STRUST under SSL client SSL Client (Anonymous). Add it to the certificate and save it.
Error message: "Missing message: Party: Receiver: Int.: Ns:
You're running a test case on a new environment, and you see the message above:
To solve this problem:
Check if the SAP PO ICO configuration has this receiver configured on the landscape on which you're running the test case.
Ensure the mapping did not fail for this test case on the landscape on which you're running the test case.
Check if the logging and staging settings are using the Int4 Suite recommended settings and are not changed in case of this ICO only.
Error message: "Parent message: X found for Y", "Hint: Check if the BI logging is set or disable looking for parent message by additional parameter PIIGPARENT"
You tried to create a test case from an SAP PI/PO message created by splitting the original message. The split was done as a scenario that contained multiple receivers.
The original message is stored as version BI. Due to the SAP recommendation, the BI processing is not staged, so the message before the split is not visible in monitoring.
In such a case, Int4 Suite requires logging on the BI. It might be activated globally (check SAP PI/PO JAVA Stack Persistence or locally in ICO settings).
If you would like to create a test case just on the final receiver, then set additional parameter PIIGPARENT = X
...
Error message: "Message processing failed in SAP PO. No Succesors" while saving a test case.
...
An error like on the screenshot above pops up. However, the message looks like it was processed correctly in Message Monitor on the PI Java stack.
Solution: Please check if this is a classical ABAP stack scenario. And if so, configure the Automation Object accordingly, i.a. define an Automation Object additional parameter "PI: Landscape where interface exists on the ABAP stack" as in the example below:
...
An error like this can happen if the PIT connection is not correctly registered (PI connection available is set to false). You can manually register it from the EJB Explorer using the registerPitConnection, as shown in the figure below.
...
Random HTTP 403 errors on CPI tenants with multiple nodes
You may receive an "HTTP/1.1 403" authentication error when sending requests from Int4 Suite to the SAP CPI (Cloud Platform Integration) when the CPI has two or more tenant management or worker nodes enabled.
This situation can happen during test case execution or trace activation.
The root cause is described in note 2950846 - the SAP kernel encodes the cookies' value by default, which breaks the load balancing feature in the CPI.
To solve the issue set profile parameter ict/disable_cookie_urlencoding to 1 or 2 depending on kernel level, as described in note 2681175.
...
Int4 Suite result report is displayed in SAP HTML Viewer control which uses the underlying Web browser on the current frontend. On Windows clients, it's Internet Explorer.
Internet Explorer is displaying Intranet pages in 'Compatibility view' mode by default. Depending on network settings Int4 Suite report address might be recognized as an intranet page and displayed in compatibility view, which causes rendering issues.
The solution is to disable the compatibility view in Internet Explorer. This can be done in Tools > Compatibility View settings by unchecking 'Display intranet sites in Compatibility View.'
...
Error message: "SoapFaultCode:5..."
...
Error message: "Get logged message bytes - returned an exception"
In case you're using payload level restrictions, make sure the Int4 Suite communication user used to connect to the respective SAP PO landscape has all the correct user roles "XiMdt.*."
Error message: "Error while sending message to middleware. HTTP error status: 500"
...
It can occur during the TC creation done by Robot or while manually creating a new node in the Cockpit.
...
If Int4 Suite can't create a new node id, this issue will occur. Technically speaking, Int4 Suite can't insert the new row into the table /INT4/IFTT_TGRP. To create the new Node ID, the Number Range /INT4/SCNR is used.
If you receive this error, please check if the current interval in the Number Range /INT4/IFTT_TGRP is correct and contains a bigger number than the last (highest) value of the SCNRID from the table /INT4/IFTT_TGRP. If not, adjust the Number Range manually.
Error message: "Failed to get channel * status"
It can occur during the test case execution in the scenario where Start/Stop channel configuration is used.
...
In that case the following automation object additional parameters must be double checked comparing the SAP PO channel details:
CHANNEL
CHANNEL_BC
CHANNEL_PT
Error message: "HTTP error status: 500 Intern - System is currently not started "
...