How To Fix RSM858 - Could not create job &1; error &2

SAP Error Message - Details

• Message type: E = Error

• Message class: RSM -

• Message number: 858

• Message text: Could not create job &1; error &2

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 RSM858 - Could not create job &1; error &2 ?

  The SAP error message RSM858, which states "Could not create job &1; error &2," typically occurs in the context of background job scheduling in SAP. This error indicates that there was a failure in creating a background job, and the placeholders &1 and &2 will be replaced with specific job names and error codes, respectively.
  Causes:
  
  Authorization Issues: The user attempting to create the job may not have the necessary authorizations.
  System Configuration: There may be issues with the job scheduling configuration in the SAP system.
  Resource Limitations: The system may be running out of resources (e.g., memory, processes) to create new jobs.
  Job Name Conflicts: There may be a conflict with existing job names or naming conventions.
  Database Issues: Problems with the database connection or database performance can also lead to job creation failures.
  Transport Issues: If the job is being created as part of a transport request, there may be issues with the transport configuration.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to create background jobs. This can be done by checking the user's roles and profiles.
  Review Job Scheduling Configuration: Check the configuration settings for job scheduling in transaction SM37 (Job Monitoring) and SM36 (Define Background Job).
  Monitor System Resources: Use transaction ST02 (Tune Summary) or ST06 (Operating System Monitor) to check for resource bottlenecks.
  Check Job Names: Ensure that the job name being used does not conflict with existing jobs. If necessary, modify the job name to avoid conflicts.
  Database Health Check: Verify the health of the database and ensure that it is performing optimally. Check for locks or long-running transactions that may be affecting job creation.
  Review Transport Configuration: If the job is part of a transport, ensure that the transport is correctly configured and that there are no issues with the transport directory.
  
  Related Information:
  
  
  Transaction Codes:
  
  SM36: To create and define background jobs.
  SM37: To monitor and manage background jobs.
  ST22: To check for dumps that may provide more context on the error.
  SM21: To view system logs for any related error messages.
  
  
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  
  Logs and Traces: Review the system logs and traces for any additional error messages that may provide more context about the failure.
  
  
  If the issue persists after trying the above solutions, it may be beneficial to contact SAP support for further assistance, providing them with the specific error details and any relevant logs.