SSO BW to NW -->RfcGetException

[Former Member]

Hello everybody,

we wave a problem with the connection of SAP BW 3.5 to one of our NW Portals. The BW is connected to two portals and each portal is connected to three BW's. Five of Six connections are working perfectly. But one connection does not work. From BW site everything is fine... The Report RSPOR_SETUP is totally green. Only if try to connect to the BW via SSO the following error occured:

The dev_Jrfc.trc:

Error> occured >Thu Apr 13 15:27:11,379< >RfcGetException rc (7) message: Es wurde ein nicht interpretierbares SSO-Ticket empfangen

<RfcGetException

In the default trace there the corresponding error from the connection test:

[EXCEPTION]

#1#com.sap.security.api.umap.NoLogonDataAvailableException: Can't provide the user's SAP logon ticket because there is no existing logon ticket. Is it possible that the user has not been authenticated?

at com.sap.security.core.umap.imp.UserMappingDataImp.getAuthenticationTicket(UserMappingDataImp.java:1660)

Thanks in advance,

Axel

[Former Member · Accepted solution]

HI Axel,

Have you checked the steps required for Integrating BW and EP?

Do check the blog <a href="https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1505">Integration of SAP Business Warehouse and Enterprise Portal – Single Sign-on</a>

The error seems that it is unable to interpret the SSO2 ticket.

Please check if you have exported the Portal's SAP logon ticket to BW and that the logon method used by the system in your SLD is SAPLOOGON ticket.

Regards,

Siddhartha

[Former Member]

Hi Everybody,

for some reason the certificate was corrupted. I exported the Portal certificate again and did the Import to the BW again and now it works.

Thanks a lot for helping,

Regards,

Axel

[Former Member]

Happy Easter,

Thanks for your answers. I visited the links, but unfortunately they did not help me to find a solution. The SLD config should be fine because of the same system works in the development system and even the aliases are identical. One thought that goes to my mind is, that the problem might be caused by that we added new server notes to the J2EE Engine since we configured the SSO. The second BW which is connected to the portal is still working fine with SSO, but may be you can imagine that the new servers could cause this problem?

Thanks in advance,

Axel

[Former Member]

These link will give you an idea of your error

http://help.sap.com/saphelp_nw04s/helpdata/en/29/acd8403e37762ae10000000a155106/content.htm

https://media.sdn.sap.com/javadocs/NW04/SPS15/um/com/sap/security/api/umap/class-use/NoLogonDataAvai...

https://media.sdn.sap.com/javadocs/NW04/SPS15/um/index-files/index-14.html