How To Fix 5C399 - System error when sending a message (&1, &2)

SAP Error Message - Details

• Message type: E = Error

• Message class: 5C - HR: Messages for Switzerland

• Message number: 399

• Message text: System error when sending a message (&1, &2)

What causes this issue?

Messages have to be sent to the PI for signing, sending, or for checking
the signature. In doing so, a technical problem occurred.

System Response

The current process step was canceled. The process changes to an error
status.

How to fix this error?

If the problem is temporary (for example, PI was temporarily unavailable
or down), you can execute the process step again later. To do this, you
manually change the status to a suitable follow-up status (for example,
?Query Status Again? if the problem occurred when querying the message
status) and execute the process again.

Procedure for System Administrators

The PI message monitor may contain further details about the cause of
the error. The message was sent on &V1& at &V2&.
If there is no entry in the message monitor, the problem may lie with
the connection of the ERP system to the PI. In view V_T50BK (Country
Grouping Switzerland), the RFC destinations are maintained under the
constants 'DEST' and 'DSTXI' and the remote-capable function modules are
maintained under the constant 'FNAM*', which are used for the connection
of the ERP system to the PI.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 5C399 - System error when sending a message (&1, &2) ?

  The SAP error message 5C399, which indicates a "System error when sending a message (&1, &2)," typically arises in the context of SAP's messaging system, particularly when there are issues with the communication between systems or components. Here’s a breakdown of the potential causes, solutions, and related information for this error:
  Causes:
  
  Network Issues: There may be network connectivity problems between the SAP system and the target system or service.
  Configuration Errors: Incorrect configuration settings in the SAP system or the messaging framework can lead to this error.
  System Resource Limitations: Insufficient system resources (like memory or CPU) can cause failures in processing messages.
  Message Queue Problems: Issues with the message queue (like being full or corrupted) can prevent messages from being sent.
  Authorization Issues: The user or service account may not have the necessary permissions to send messages.
  Software Bugs: There may be bugs in the SAP software or the specific version you are using.
  
  Solutions:
  
  Check Network Connectivity: Ensure that there are no network issues between the systems involved. You can use tools like ping or traceroute to diagnose connectivity.
  Review Configuration Settings: Verify the configuration settings for the messaging system. This includes checking the RFC destinations, logical systems, and any relevant parameters.
  Monitor System Resources: Use transaction codes like ST02 (buffer management) and ST06 (OS monitor) to check for resource bottlenecks.
  Inspect Message Queues: Check the status of the message queues using transaction codes like SMQ1 (for outbound queues) and SMQ2 (for inbound queues). Clear any stuck messages if necessary.
  Check Authorizations: Ensure that the user or service account has the necessary authorizations to send messages. You can use transaction SU53 to analyze authorization issues.
  Update SAP Software: If the issue persists, check for any available patches or updates for your SAP system that might address known bugs.
  
  Related Information:
  
  SAP Notes: Search the SAP Support Portal for any relevant SAP Notes that might provide specific guidance or patches related to this error.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM21 (system log), ST22 (dump analysis), and SLG1 (application log) to gather more information about the error.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  
  If the problem persists after trying the above solutions, it may be beneficial to contact SAP support for further assistance, providing them with detailed logs and error messages to facilitate troubleshooting.