Do you have any question about this error?
Message type: E = Error
Message class: /PRA/PN -
Message number: 135
Message text: Queue exists but Queue Manager not running; attempting to restart
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
/PRA/PN135
- Queue exists but Queue Manager not running; attempting to restart ?The SAP error message
/PRA/PN135 Queue exists but Queue Manager not running; attempting to restart
typically indicates that there is an issue with the Queue Manager in the SAP Process Integration (PI) or Process Orchestration (PO) environment. This error suggests that a queue exists, but the Queue Manager responsible for processing messages in that queue is not currently running. Here’s a breakdown of the cause, potential solutions, and related information:Cause:
- Queue Manager Not Running: The most straightforward cause is that the Queue Manager service has stopped or is not running due to various reasons such as system crashes, manual shutdowns, or configuration issues.
- Resource Issues: Insufficient system resources (CPU, memory) can prevent the Queue Manager from starting or functioning properly.
- Configuration Issues: Incorrect configuration settings in the SAP PI/PO system can lead to the Queue Manager not being able to start.
- Database Issues: Problems with the underlying database that the Queue Manager relies on can also cause it to fail.
- Network Issues: If the Queue Manager is trying to connect to other services or databases over the network, any network issues can prevent it from starting.
Solution:
- Check Queue Manager Status: Verify if the Queue Manager is indeed not running. You can do this through the SAP NetWeaver Administrator or by checking the relevant logs.
- Restart the Queue Manager: If the Queue Manager is not running, attempt to restart it. This can often resolve temporary issues.
- Use transaction
SXMB_MONI
to monitor the queues and check their status.- Use transaction
SICF
to check the services related to the Queue Manager.- Check Logs: Review the logs for any error messages that might indicate why the Queue Manager is not running. Look in the
dev_xxx
logs or the application logs in transactionSLG1
.- System Resources: Ensure that the server has enough resources (CPU, memory) available. If resources are low, consider optimizing or upgrading the server.
- Configuration Review: Check the configuration settings for the Queue Manager in the SAP PI/PO system. Ensure that all settings are correct and that there are no misconfigurations.
- Database Health: Check the health of the database. Ensure that it is running and accessible. Look for any database-related errors in the logs.
- Network Connectivity: Ensure that there are no network issues preventing the Queue Manager from connecting to other necessary services or databases.
Related Information:
By following these steps, you should be able to diagnose and resolve the issue related to the Queue Manager not running in your SAP environment.
Get instant SAP help. Start your 7-day free trial now.
/PRA/PN134
Can not set a manual PPN to a PPN delete reason code for an existing vcr
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/PRA/PN133
Resource wait; contention in group &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/PRA/PN136
No DN Launcher Queue Manager job found; yet is locked, preventing restart
What causes this issue? The monitoring logic has detected a potential issue, which consists of items waiting to be processed in the DN Launcher queu...
/PRA/PN137
Lock held by &1 since &2 &3
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.