How To Fix STRALAN_MSAG379 - Export of request & already running

SAP Error Message - Details

• Message type: E = Error

• Message class: STRALAN_MSAG - Language Transport Messages

• Message number: 379

• Message text: Export of request & already running

What causes this issue?

You have rescheduled the export of transport requests even though an
export has not yet finished.

System Response

The system terminates the rescheduled export.

How to fix this error?

Wait until the scheduled release process has finished.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message STRALAN_MSAG379 - Export of request & already running ?

  The SAP error message "STRALAN_MSAG379: Export of request & already running" typically indicates that there is an ongoing export process for a transport request, and a new export attempt is being made for the same request. This can happen in various scenarios, such as when multiple users or processes try to export the same transport request simultaneously.
  Cause:
  
  Concurrent Export Attempts: Another user or process is already exporting the same transport request.
  Long-Running Export: The export process may be taking longer than expected, leading to a situation where a second export is attempted before the first one completes.
  System Lock: The transport management system may have a lock on the request due to a previous operation that has not yet completed.
  
  Solution:
  
  Wait for Completion: If you suspect that another export is in progress, wait for that process to complete before attempting to export the request again.
  Check Background Jobs: Use transaction code SM37 to check for any background jobs related to the transport request. If you find a job that is stuck or taking too long, you may need to investigate further.
  Cancel Stuck Jobs: If you identify a job that is stuck, you can cancel it (if you have the necessary permissions) and then try to export the request again.
  Review Transport Logs: Check the transport logs for any errors or warnings that might indicate why the export is taking longer than expected.
  System Restart: In some cases, if the issue persists and you have the necessary authorizations, a system restart may help clear any locks or stuck processes.
  Contact Basis Team: If you are unable to resolve the issue, it may be necessary to contact your SAP Basis team for assistance. They can provide deeper insights into the transport management system and help resolve any underlying issues.
  
  Related Information:
  
  Transaction Codes: 
  
  SE09 or SE10: To manage transport requests.
  SM37: To monitor background jobs.
  ST22: To check for dumps that might be related to the issue.
  
  
  Transport Management System (TMS): Understanding how TMS works can help in troubleshooting transport-related issues.
  SAP Notes: Check SAP Notes for any known issues or patches related to transport requests and the specific error message.
  
  By following these steps, you should be able to diagnose and resolve the issue related to the "STRALAN_MSAG379" error message.