RT312 - Erreur lors de communication avec serveur application &1

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 312

• Message text: Erreur lors de communication avec serveur application &1

Quelle est la cause de ce problème?

The system is unable to communicate with the application server that is
specified. This is caused by RFC communication problems.

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?

Normally, you should see few or no calls with communication problems.
However, communication problems do not necessarily represent a problem.
For example, CPI-C errors may occur if a server or system is down for
maintenance. If the destination is returned to service before the retry
interval runs out, then the tRFC calls and LUWs are automatically
processed.
If the CPI-C errors are not caused by a routine problem such as
servicing, then you should check the network connection to the
destination server. In addition to actual network problems, CPI-C errors
may be caused by:
An inactive gateway process in the calling or destination System
An incorrect CPI-C implementation in an external server
Incorrect data in the definition of the destination in the calling
system (transaction SM59).
You can test connections to RFC destinations in Transaction SM59.
After you have corrected the problem, the tRFC calls and LUWs that were
affected are automatically processed, if the retry interval has not
elapsed.
Otherwise, you can trigger processing an affected LUW by hand in
Transaction SM58 (the analysis method for tRFC).
Once successfully processed, calls with communication errors are
automatically deleted from the tRFC work queue, and will no longer
appear in this monitor.

Procédure pour les administrateurs système

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