How To Fix C$458 - Could not start job. Error in procedure & (exception &)

SAP Error Message - Details

• Message type: E = Error

• Message class: C$ -

• Message number: 458

• Message text: Could not start job. Error in procedure & (exception &)

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 C$458 - Could not start job. Error in procedure & (exception &) ?

  The SAP error message C$458, which states "Could not start job. Error in procedure & (exception &)," typically indicates that there is an issue with a background job that is trying to execute a specific procedure or function module. This error can arise from various causes, and here are some common reasons along with potential solutions:
  Causes:
  
  Authorization Issues: The user or the background job may not have the necessary authorizations to execute the procedure.
  Missing or Incorrect Configuration: The procedure or function module being called may not be correctly configured or may be missing.
  Runtime Errors: There could be a runtime error in the procedure itself, such as unhandled exceptions or logic errors.
  System Resource Issues: Insufficient system resources (like memory or processing power) can prevent the job from starting.
  Database Issues: Problems with the database connection or database locks can also lead to this error.
  Transport Issues: If the procedure was recently transported from another system, it may not have been properly activated or may have dependencies that are not met.
  
  Solutions:
  
  Check Authorizations: Ensure that the user executing the job has the necessary authorizations to run the procedure. You can use transaction SU53 to analyze authorization issues.
  Review the Procedure: Check the procedure or function module for any errors. You can do this by debugging the procedure or reviewing the code for any potential issues.
  Check Job Logs: Look at the job logs for more detailed error messages. You can access this through transaction SM37 (Job Monitoring).
  System Resources: Monitor system resources to ensure that there are enough resources available for the job to run. You can use transaction ST02 (Tune Summary) or ST06 (Operating System Monitor) for this.
  Database Connection: Verify that the database is up and running and that there are no locks or issues preventing the job from executing.
  Transport Activation: If the procedure was recently transported, ensure that it has been activated in the target system. You can check this in transaction SE80 or SE37.
  Check for Updates: Ensure that your SAP system is up to date with the latest patches and updates, as this can resolve known issues.
  
  Related Information:
  
  Transaction Codes: 
  
  SM37: Job Monitoring
  SE80: Object Navigator
  SE37: Function Module
  SU53: Authorization Check
  ST22: Dump Analysis
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  Debugging: If you have access, consider debugging the job or the procedure to identify the exact point of failure.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.