cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Backbone connectivity still not enabled after completed all configurations steps

valfre
Participant
0 Kudos

Hello Guys

I already completed the configuration, applyed all sap notes, SAP hub configuration in STC01 is all in Green, Web services working fine.

I followed up this checklist and everything is ok

https://support.sap.com/en/alm/solution-manager/sap-support-backbone-update/backbone-update-checklis...

This is the Early Watch Alert report about SAP Backbone Connectivity

I really check everything but i dont have any more ideas about what to check, i found a lot of sap notes and everything looks fine.

I have Solution Manager 7.2 SP9

Regards

bharathyp
Active Participant
0 Kudos

Just thinking aloud here. But, isn't the user type supposed to be technical user?

I myself in the midst of setting up a brand new Solman 7.2 sp9 as well.

Accepted Solutions (1)

Accepted Solutions (1)

ben_schneider
Product and Topic Expert
Product and Topic Expert

Hello Marco,

thanks for the feedback. This is a technical issue in the EarlyWatch Alert, a fix for this will be shipped soon. Please ignore the yellow indicator for now.

Best regards,

Ben Schneider
Digital Business Services, SAP SE

valfre
Participant
0 Kudos

Hello Benjamin

Trying to find a solution to this i applyed these two sap notes : 2793641, 2827658 and now the following Jobs are getting canceled:

An exception of type CX_SISE_EXCEPTION has occurred.

An exception was raised

SoapFaultCode:5Server Error

Already applyed the following sap notes : 2525987,2639809,2508990 but doesn't solve my problem, there is not any other sap note to fix this, now im in a worse status.

Im thinking to reverse the sap notes. Can you recommend me something else?

Regards.

valfre
Participant
0 Kudos

Hello Benjamin

Accoding with the early watch report issue could you tell me if i must open an incident? when do you estimate to have a solution?

Regards.

Answers (4)

Answers (4)

christoph_ostrop
Active Contributor
0 Kudos

Despite of that many sapnotes on the topic,

the customizing of the ANST has been forgotten in all of them => table ANST_SETTINGS

(to change the RFC to new support portal)

patelyogesh
Active Contributor
0 Kudos

Hello Marco Valero

I think this is the issue on SAP side and it is On-and-Off

Please check SAP note below for more information...

2525987 - Internal Server Error, SoapFaultCode:5 Server Error or Timeout error (ICM_HTTP_TIMEOUT) in jobs using the asynchronous channel

Regards

Yogesh

former_member209604
Active Contributor
0 Kudos

Hi Marco,

the check "SAP Backbone Connectivity" was updated in meanwhile.

You can access the latest report conveniently via the "SAP EarlyWatch Alert Workspace" in "SAP ONE Support Launchpad":
https://launchpad.support.sap.com/#/ewaworkspace -> Card 'Overall Rating'

Column "User" in table "Latest Data for System <SID> sent to SAP" is currently not filled in all cases. Further adjustments will follow.

The corrected service check content will be made available through "Service Content Update" (transaction AGS_UPDATE in SAP Solution Manager).

Best regards,
Ruediger Stoecker

valfre
Participant

Hello Ruediger

Thanks for wrote, I want to know if this fix will be ready before 2020, do you have any release date for this?

Best regards.

former_member209604
Active Contributor
0 Kudos

The Column "User" is still empty. I will do a follow-up with the development team, when the change will be finally available.

former_member209604
Active Contributor

Marco, I already got a response from the development team. The correction is not yet completed and finally tested, therefore the correction could not be published. I will update this thread as soon I have further news.

MikeDumas
Participant
0 Kudos

Hi Marco,

We had a similar issue with the SM:UPLOAD SYSTEM DATA job and SAP Support directed us to note 2525987. That may apply to your situation as well.

Good luck!

Mike Dumas

valfre
Participant
0 Kudos

Thanks Michael

The sap note 2525987 is already applyed in the system but the issue is still there.