Do you have any question about this error?
Message type: E = Error
Message class: SRT_CORE - Nachrichtenklasse für SOAP Runtime
Message number: 201
Message text: File d'attente bgRFC vide ou non trouvée
The bgRFC queue using in Web Service Reliable Messaging (WS RM) is empty
or already deleted even if there are still messages belonging to this
queue stored in the XI persistency.
This might happen if the bgRFC queue is deleted manually from within the
bgRFC Monitor. Therefore, never delete a bgRFC queue using by WS RM from
within bgRFC Monitor.
As the message belonging to this bgRFC queue is now in a inconsistent
state and it is not clear whether it is already delivered, following
steps are necessary:
Look at the message payload by clicking the "Message State" or
"Persistency ID" to run the XI Message Monitor.
Based on the payload contact the responsible Web Service application and
ask for checking whether you can cancel this message.
To cancel one or more messages just mark the according entries and click
"Cancel Messages".
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.
Extrait du message d'erreur du système SAP. Copyright SAP SE.
SRT_CORE201
- File d'attente bgRFC vide ou non trouvée ?Get instant SAP help. Start your 7-day free trial now.
SRT_CORE176
Utilisez la méthode ping_xi() pour la configuration XI.
Message auto-explicatif Étant donné que SAP estime que ce message d'erreur spécifique est 'auto-explicatif', aucune autre information n'a été fou...
SRT_CORE175
Ping du service : paramètres insuffisants entrés pour ping XI-P2P-
Quelle est la cause de ce problème? An internal error occurred. The service ping for XI P2P was called without all necessary parameters supplied.RÃ...
SRT_CORE202
ID de séquence non valide dans couche de séquence
Quelle est la cause de ce problème? The message stored in the XI persistency contains a logical sequence ID which is managed by the Sequence Manage...
SRT_CORE203
Echec du message d'annulation
Quelle est la cause de ce problème? The Task Watcher (TW) used for Tentative Update and Compensate or Confirm (TU<(>&<)>C/C) couldn...
Cliquez sur ce lien pour rechercher tous les messages SAP.