How To Fix RT387 - Starting ...

SAP Error Message - Details

• Message type: E = Error

• Message class: RT - Monitoring infrastructure MSG and alert texts

• Message number: 387

• Message text: Starting ...

Self-Explanatory Message

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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message RT387 - Starting ... ?

  The SAP error message RT387 typically indicates an issue related to the starting of a process or job in the SAP system. While the exact cause can vary depending on the specific context in which the error occurs, here are some common causes, potential solutions, and related information:
  Causes:
  
  Job Scheduling Issues: The job may not be scheduled correctly or may have been canceled.
  Authorization Problems: The user or process may lack the necessary authorizations to start the job.
  System Configuration: There may be configuration issues in the SAP system that prevent the job from starting.
  Resource Availability: Insufficient system resources (like memory or CPU) can prevent jobs from starting.
  Dependencies: The job may depend on other jobs or processes that have not completed successfully.
  
  Solutions:
  
  Check Job Status: Use transaction code SM37 to check the status of the job. Look for any errors or messages that might indicate why the job is not starting.
  Review Authorizations: Ensure that the user or process has the necessary authorizations to execute the job. You can check this in transaction SU53 or by reviewing the user roles.
  Re-schedule the Job: If the job was canceled or failed, try to re-schedule it. You can do this in transaction SM36.
  Check System Resources: Monitor system resources using transaction SM50 or SM66 to ensure that there are enough resources available for the job to start.
  Review Job Dependencies: If the job has dependencies, ensure that all prerequisite jobs have completed successfully.
  Consult Logs: Check the application logs or system logs for any additional error messages that might provide more context about the failure.
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that might address specific issues related to the RT387 error.
  Documentation: Review SAP documentation for job scheduling and background processing for more detailed guidance.
  Community Forums: Consider checking SAP Community forums or other user groups for similar issues and solutions shared by other users.
  
  If the problem persists after trying the above solutions, it may be beneficial to contact SAP support for further assistance, providing them with detailed information about the error and the context in which it occurred.