How To Fix MCEX147 - Reading of RFC queue &1 with destination &2 already started

SAP Error Message - Details

• Message type: E = Error

• Message class: MCEX - Extraction Interface LIS/BW

• Message number: 147

• Message text: Reading of RFC queue &1 with destination &2 already started

What causes this issue?

You have started processing of extraction queue &V1&. However, it seems
that processing of the queue is still running.

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

How to fix this error?

If you have received this message but are sure that processing of queue
&V1& is not currently active, check whether lock entries still exist
for the lock object EMCEXUPD, and delete them as required.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MCEX147 - Reading of RFC queue &1 with destination &2 already started ?

  The SAP error message MCEX147 indicates that there is an issue with the Remote Function Call (RFC) queue. Specifically, it means that a reading process for the RFC queue with a specific destination has already been initiated, and a second attempt to read from the same queue is being made, which is not allowed.
  Cause:
  
  Concurrent Access: The error typically occurs when multiple processes or jobs attempt to read from the same RFC queue simultaneously. This can happen if there are multiple instances of a program or transaction trying to access the same destination.
  Long-Running Processes: If a previous reading process is taking longer than expected, it may block subsequent attempts to read from the queue.
  Configuration Issues: There may be configuration issues in the RFC destination settings or in the way the RFC queues are managed.
  
  Solution:
  
  Check Running Processes: Use transaction SM58 (Transactional RFC) to check for any long-running or stuck RFC calls. If you find any, you may need to resolve or terminate them.
  Avoid Concurrent Reads: Ensure that your application logic does not attempt to read from the same RFC queue concurrently. This may involve implementing locks or checks to prevent multiple reads.
  Increase Timeout Settings: If the reading process is taking too long, consider increasing the timeout settings for the RFC destination.
  Monitor and Optimize Performance: Analyze the performance of the processes that are reading from the RFC queue. Optimize them if necessary to reduce the time they take to complete.
  Check Configuration: Review the configuration of the RFC destination in transaction SM59 to ensure it is set up correctly and that there are no issues with the connection.
  
  Related Information:
  
  Transaction SM58: This transaction allows you to monitor and manage the transactional RFC calls. You can see if there are any stuck or failed calls that need attention.
  Transaction SM59: This transaction is used to configure RFC destinations. You can check the settings and test the connection to ensure it is functioning correctly.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps. You can search for notes related to RFC issues or the specific error message.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.