Message type: E = Error
Message class: SWF_XI_ADAPTER - XI BPM: Messages
Message number: 405
Message text: Inbound queue &1 (SMQ2) for process type &2 is not stopped
You want to change the settings for inbound processing for a process
type. This change is not permitted because the process-type-specific
queue is not stopped.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
The short text of the error message specifies which queue must have a
stop entry. Copy the queue name and call transaction SMQ2. Start the
selection using the copied queue name. The possibilities are as follows:
The queue does not exist
Try to make the settings again.
The queue exists
Create a stop entry in the queue. Wait until no more queue entries are
being processed. Note that stopping the queue does not affect the queue
entry currently being processed; only the subsequent entries are
stopped.
When the queue is stopped, you should be able to change the setting for
the process type.
<ZH>Note the following:</> A non-existent queue may be seen as stopped
in the system, since inbound processing is locked while the settings are
being changed. Once a queue entry exists, the administrator must create
a stop entry for the corresponding queue. If, in the first case, the
system still refuses the change, this is probably because the queue
became existent or still existed in the meantime. Since new queue
entries are constantly being added, you must only change the settings
for inbound processing when the system load is low. You may have to make
several attempts to stop the queue in SMQ2 and change the setting.
Error message extract from SAP system. Copyright SAP SE.
SWF_XI_ADAPTER405
- Inbound queue &1 (SMQ2) for process type &2 is not stopped ?The SAP error message SWF_XI_ADAPTER405 indicates that there is an issue with the inbound queue in the SAP system, specifically related to the process type that is not stopped. This error typically occurs in the context of SAP Process Integration (PI) or SAP Process Orchestration (PO) when there are problems with message processing in the queues.
Cause: Message Processing Issues: The inbound queue (SMQ2) for the specified process type is not stopped, which may indicate that messages are stuck or not being processed correctly. Configuration Errors: There may be configuration issues with the process type or the integration scenario that is causing the queue to remain active. System Performance: High load on the system or performance issues may prevent the queue from processing messages in a timely manner. Deadlocks or Locks: There may be locks on the queue or deadlocks that are preventing the processing of messages.
Solution: Check Queue Status: Go to transaction SMQ2 and check
Get instant SAP help. Sign up for our Free Essentials Plan.
SWF_XI_ADAPTER404
Mode for process type &1 has unexpected values (DB &2; buffer &3)
What causes this issue? You want to change the processing logic in the settings for inbound processing for a process type. The system does not recogn...
SWF_XI_ADAPTER403
Action &1 is not currently supported
What causes this issue? You want to adapt the settings for inbound processing for a process type. The change you want to make is not supported due to...
SWF_XI_ADAPTER406
An LUW is being processed in inbound queue &1 (SMQ2) for process type &2
What causes this issue? You want to change the settings for inbound processing for a process type. This change is not permitted because the process-t...
SWF_XI_ADAPTER407
Inbound queue &1 (SMQ2) for process type &2 has LUW with errors
What causes this issue? You want to change the settings for inbound processing for a process type. The change is not permitted in this case because t...
Click on this link to search all SAP messages.