How To Fix /SSB/CORE690 - Fetching job status for Story &1 failed due to HTTP communication error

SAP Error Message - Details

• Message type: E = Error

• Message class: /SSB/CORE -

• Message number: 690

• Message text: Fetching job status for Story &1 failed due to HTTP communication error

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 /SSB/CORE690 - Fetching job status for Story &1 failed due to HTTP communication error ?

  The SAP error message /SSB/CORE690 Fetching job status for Story &1 failed due to HTTP communication error typically indicates that there is an issue with the communication between the SAP system and the server that is responsible for processing the job related to the story (report or dashboard) in SAP Analytics Cloud (SAC) or SAP BusinessObjects.
  Causes:
  
  Network Issues: There may be network connectivity problems between the SAP system and the server.
  Server Unavailability: The server that processes the job may be down or experiencing issues.
  Timeouts: The request may be timing out due to long processing times or server overload.
  Configuration Issues: Incorrect configuration settings in the SAP system or the server can lead to communication errors.
  Firewall or Security Settings: Firewalls or security settings may be blocking the HTTP requests.
  
  Solutions:
  
  Check Network Connectivity: Ensure that there is proper network connectivity between the SAP system and the server. You can use tools like ping or traceroute to diagnose network issues.
  Server Status: Verify that the server responsible for processing the job is up and running. Check server logs for any errors or issues.
  Increase Timeout Settings: If the job is taking too long to process, consider increasing the timeout settings in the SAP system or the server.
  Review Configuration: Check the configuration settings in both the SAP system and the server to ensure they are correct. This includes checking URLs, ports, and authentication settings.
  Firewall Rules: Review firewall settings to ensure that HTTP requests are allowed between the SAP system and the server.
  Retry the Job: Sometimes, simply retrying the job can resolve transient issues.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Logs: Review application logs in both the SAP system and the server for more detailed error messages that can provide insight into the issue.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  Documentation: Refer to the official SAP documentation for guidance on configuring and troubleshooting communication between SAP systems and external servers.
  
  If the issue persists after trying the above solutions, it may be necessary to involve your IT support team or SAP support for further assistance.