Versions Compared

Old Version 42

changes.mady.by.user Konstantinos Tsakalos

Saved on

compared with

New Version Current

changes.mady.by.user Mateusz Nowak

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

Error message: " Internal Error 500 error " when opening transaction SOAMANAGER on the sandbox system

Suppose Int4 IFTT 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:

  1. Execute report rsicf_service_activation with the option WEB DYNPRO ABAP to make sure that Webdynpro applications will run properly. ( SAP Note 1088717).
  2. 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 IFTT configuration wizard or manually in SOAMANAGER


Suppose Int4 IFTT 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:

  1. In the RFC connection for your SAP PI/PO, you use a user with the necessary authorization
  2. 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:

  1. Check if the SAP PO ICO configuration has this receiver configured on the landscape on which you're running the test case. 
  2. Ensure the mapping did not fail for this test case on the landscape on which you're running the test case. 
  3. Check if the logging and staging settings are using the Int4 IFTT 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"

...

Error message: "Message processing failed in SAP PO. No Succesors" while saving a test case. 

image.png

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:

...

Error message: "Get logged message bytes - returned an exception"

In case you're using payload level restrictions, make sure the Int4 IFTT 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 IFTT can't create a new node id, this issue will occur. Technically speaking, IFTT 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 "


Image Added

It can occur if your SAP PO system is totally down or one of the application servers is not available.