How To Fix RSCRT342 - Could not start RDA daemon; requests are deleted in DataStore object

SAP Error Message - Details

• Message type: E = Error

• Message class: RSCRT - Near-To-Real-Time Messages

• Message number: 342

• Message text: Could not start RDA daemon; requests are deleted in DataStore object

What causes this issue?

You tried to start a daemon for real-time data acquisition (RDA) to
which the data transfer process &V1& is assigned. Requests are
currently being rolled back or deleted in the target of this DTP
(InfoProvider &V2&). One of these requests is &V3&.

System Response

The RDA daemon cannot be started while requests are being deleted in
InfoProvider &V2&.

How to fix this error?

Wait until the requests in the InfoProvider have been deleted.
Then start the RDA daemon again.

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 RSCRT342 - Could not start RDA daemon; requests are deleted in DataStore object ?

  The SAP error message RSCRT342 indicates that the RDA (Real-Time Data Acquisition) daemon could not be started, which leads to the deletion of requests in the DataStore object (DSO). This error typically occurs in the context of SAP BW (Business Warehouse) when there are issues with the data acquisition process.
  Causes:
  
  Configuration Issues: The RDA daemon may not be properly configured in the SAP BW system.
  System Resource Limitations: Insufficient system resources (CPU, memory) can prevent the RDA daemon from starting.
  Network Issues: Problems with network connectivity can hinder the daemon's ability to communicate with the source system.
  Authorization Problems: The user or service account running the RDA daemon may lack the necessary authorizations.
  Background Job Issues: If the background job responsible for starting the RDA daemon is not running or has failed, this can lead to the error.
  Software Bugs: There may be bugs in the SAP BW version being used that affect the RDA functionality.
  
  Solutions:
  
  Check Configuration: Verify the configuration settings for the RDA in the SAP BW system. Ensure that all parameters are correctly set.
  Monitor System Resources: Check the system's CPU and memory usage. If resources are low, consider optimizing the system or upgrading hardware.
  Network Connectivity: Ensure that there are no network issues between the SAP BW system and the source system. Test connectivity and resolve any issues.
  Review Authorizations: Check the authorizations for the user or service account that is supposed to run the RDA daemon. Ensure it has the necessary permissions.
  Check Background Jobs: Look into the background jobs related to the RDA daemon. Ensure they are scheduled and running correctly. If they have failed, investigate the logs for errors.
  SAP Notes and Patches: Check for any relevant SAP Notes or patches that address known issues with the RDA daemon. Apply any necessary updates.
  Restart the Daemon: If the daemon is not running, try restarting it manually. This can sometimes resolve transient issues.
  
  Related Information:
  
  Transaction Codes: Use transaction codes like RSCUSTV10 to check RDA settings and SM37 to monitor background jobs.
  Logs: Review the system logs (transaction SM21) and the RDA logs for any additional error messages that can provide more context.
  SAP Support: If the issue persists after trying the above solutions, consider reaching out to SAP Support for further assistance.
  
  By following these steps, you should be able to diagnose and resolve the RSCRT342 error in your SAP BW environment.