How To Fix RSM1349 - Daemon & assigned; cannot start delta/init InfoPackage &

RSM1349 - Overview

• Message type: E = Error

• Message class: RSM1 - Messages for AWB, Scheduler and Monitor (new)

• Message number: 349

• Message text: Daemon & assigned; cannot start delta/init InfoPackage &

What causes this issue?

InfoPackage &V2& should be executed, while daemon no. &V1& has assigned
an InfoPackage for real-time data acquisition (RDA) which belongs to the
same DataSource.

System Response

The system cannot execute InfoPackage &V2&.

How to fix this error?

If you want to load the data with RDA<(>,<)> start daemon no. &V1& in
the RDA monitor (Transaction RSRDA). If you want to load the data with
InfoPackage &V2&, delete the assignment to daemon no. &V1& in the RDA
monitor.

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 RSM1349 - Daemon & assigned; cannot start delta/init InfoPackage & ?

  The SAP error message RSM1349 typically indicates that there is an issue with the Data Transfer Process (DTP) or InfoPackage in the context of data extraction and loading in SAP BW (Business Warehouse). The message suggests that the daemon (a background process) cannot start the delta or initialization InfoPackage.
  Causes:
  
  
  Configuration Issues: The InfoPackage or DTP may not be properly configured. This could include incorrect settings for the source system, target InfoObject, or data transfer settings.
  Process Chain Issues: If the InfoPackage is part of a process chain, there may be issues with the process chain itself, such as missing or incorrectly configured steps.
  Locking Issues: There may be locks on the data or objects that prevent the daemon from starting the process.
  Background Job Issues: The background job that is supposed to execute the InfoPackage may not be running or may have failed.
  Authorization Issues: The user executing the InfoPackage may not have the necessary