SAML SSO BI Launchpad URL throws FWM 20030 post deleting old SIA stopped CMS entry from CMS DB.

[former_member211289]

Dear SAP Community,

I sincerely request you please do the needful on below.

Issue: SAML SSO based BI Launchpad URL throws FWM 20030 error post deleting old SIA CMS entry from CMC / CCM and CMS database.

Details:
1. Recently, we created new SIA with CMS port 6401 (CMS Server:6401) as part of troubleshooting one issue i.e., SIA_New (for example.).
2. Since SAP suggested that we shouldn't keep two SIAs in one node, we have deleted old SIA stopped CMS entries in CMC / CCM and CMS database.
3. We have rebooted both SIA node and Tomcat node and understand that we're unable to access SAML SSO BI Launchpad. PFA screenshot. Please note that system name and port is still taking server:6400 only in BI Launchpad, though we had new SIA CMS 6401 entry.

Error: Account information not recognized: Could not reach CMS 'Server:6400'. Specify the correct host and port and check for network issues. (FWM 20030)

4. BO version is 4.2 SP5 Patch 11 and Tomcat 8. This environment is having one SIA node and one Tomcat node. We're able to access CMC with port 6401 without any issues.

Queries:

1. How can we fix this issue with new SIA CMS port 6401?

2. If it is not possible to fix, can we restore CMS_INFOOBJECTS7 table from CMS DB as issue triggered post deleting old SIA CMS entry from CMC / CCM and CMS database?

3. If we want to restore CMS_INFOOBJECTS7 table, do I need to restore FRS (CIFS share) as well? Do I need to restore both CMS_INFOOBJECTS7 table and FRS (CIFS share) at once?

saml-sso-bi-launchpad-url-gives-could-not-reach-cm.png

Thanks

Rama.

[former_member210113]

Hi Rama,

In the screenshot, I see that you are attempting to login to 6400 port when specifying CMS name. Now that you have changed the CMS listening port to 6401 (if I understood you correctly), I would suggest to try to login to CMS name:6401 in the dialog box from your screenshot. What happens?

Tomasz

[former_member211289]

Dear tomasz.zima

We updated Server: 6401 (as per new SIA CMS entries) in BI Launchpad properties file followed by Tomcat reboot but issue still persists.

We understood that SAML SSO is still taking deleted Old SIA stopped CMS entries reference and throwing error.

To fix this, we would like to restore only CMS_INFOOBJECTS7 table and check the issue.

Thanks.

[hariprasad_chennamadhavun]

Hello Rama,

I'm guessing the issue might be becuase of you are using an old trusted authentication secret. Could you please test trusted authentication login?

If it is not working, please regenerate it. For more information, follow below SAP Note:

https://launchpad.support.sap.com/#/notes/0002791348

Thanks,

Hari