How To Fix RT228 - Erreur CPI-C ALE : cible\Prog\Mndt &1, util. &2, fct. &3, ID MTE &4

SAP Error Message - Details

• Message type: E = Error

• Message class: RT - Monitoring infrastructure MSG and alert texts

• Message number: 228

• Message text: Erreur CPI-C ALE : cible\Prog\Mndt &1, util. &2, fct. &3, ID MTE &4

Quelle est la cause de ce problème?

This message describes the monitoring functions in the Alert Monitor.
Transactional RFC (tRFC, Remote Function Calls) is a function that
transfers data between SAP systems or between an SAP system and an
external component.
Here, you see the log messages for calls with CPI-C errors - calls that
could not be completed due to a connection or communication problem with
the SAP destination system or external destination component. You can
reschedule and repeat these jobs as background processing jobs. Enter
the number of retry attempts in transaction SM59.
Calls with CPI-C errors can be tRFC calls from ALE or tRFC calls from
other applications. You can also use the ALE monitoring tree to
investigate ALE calls with communication errors. The ALE monitoring tree
includes views of calls with communication errors in the ALE queue or
other entities.

Réponse du système

Le système émet un message d'erreur et ne vous permettra pas de poursuivre cette transaction tant que l'erreur n'est pas résolue.

Comment corriger cette erreur?

Each CPI-C error generates a log message. The log message contains the
information you need to identify the call. You can use the analysis
method or transaction SM58 to display CPICERR calls. The display gives
you more information about the problem. Note: You might not find log
messages for all calls with CPI-C errors. The Alert Monitor only has a
limited amount of space for these messages, which means that some might
be deleted. For a complete view of all calls with CPI-C errors, use the
analysis method for the monitoring tree element 'Number of CPI-C
Errors'.
CPI-C errors have level yellow. No red alert is generated, since the
communication problem is often not that severe. For example, the target
system might not be running due to maintenance work. Since calls with
CPI-C errors are repeated automatically, the problem might well be
solved as soon as the destination is available again.
If the CPI-C errors are not caused by a routine problem, such as
maintenance, then you must check the network connection to the
destination server. As well as definite network problems, CPI-C errors
can also be caused by the following:
An inactive gateway process in the calling or destination SAP system
A CPI-C implementation with errors on an external server
Errors in the definition of the destination of the calling system
(transaction SM59).
You can test the connection in transaction SM59.
Once you have solved the problem, the affected tRFC calls and LUWs are
processed automatically, as long as the interval for the retries has not
passed.
Otherwise, you can trigger the processing of an affected LUW manually in
transaction SM58, or in the analysis method for tRFC.

Procédure pour les administrateurs système

Extrait du message d'erreur du système SAP. Copyright SAP SE.