How To Fix J4058 - Transfer restarted after system termination

SAP Error Message - Details

• Message type: E = Error

• Message class: J4 - External Data Transfer

• Message number: 058

• Message text: Transfer restarted after system termination

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message J4058 - Transfer restarted after system termination ?

  The SAP error message J4058, which states "Transfer restarted after system termination," typically occurs in the context of data transfer processes, such as those involving IDocs, batch input sessions, or other data transfer mechanisms. This error indicates that a data transfer process was interrupted due to a system termination (e.g., a crash, a forced shutdown, or a timeout) and is now being restarted.
  Causes:
  
  System Crash or Termination: The most common cause is an unexpected termination of the SAP system or the specific process handling the data transfer.
  Timeouts: Long-running processes may hit timeout limits, causing the system to terminate the transfer.
  Resource Issues: Insufficient system resources (memory, CPU, etc.) can lead to process failures.
  Network Issues: Problems with network connectivity can interrupt data transfers, especially in distributed environments.
  Configuration Issues: Incorrect settings in the data transfer configuration can lead to failures.
  
  Solutions:
  
  Check System Logs: Review the system logs (transaction SM21) to identify the cause of the termination. Look for any critical errors or warnings that occurred around the same time.
  Monitor Background Jobs: Use transaction SM37 to check the status of background jobs related to the data transfer. Look for any jobs that may have failed or been terminated.
  Increase Timeout Settings: If timeouts are a frequent issue, consider increasing the timeout settings for the relevant processes.
  Resource Allocation: Ensure that the SAP system has adequate resources (CPU, memory, etc.) to handle the data transfer processes.
  Network Stability: Check the network connection and stability, especially if the transfer involves remote systems.
  Re-run the Transfer: If the issue is resolved, you may need to manually restart the data transfer process.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM21 (System Log), SM37 (Job Monitoring), and SLG1 (Application Log) for troubleshooting.
  SAP Support: If the issue persists, consider reaching out to SAP Support for assistance, providing them with detailed logs and error messages.
  Documentation: Review SAP documentation related to the specific data transfer method you are using (e.g., IDocs, BAPIs, etc.) for best practices and configuration guidelines.
  
  By following these steps, you should be able to diagnose and resolve the J4058 error effectively.