topic Re: SSFP_SET_TEMPPSE return code 4 RFC destination. in Application Development and Automation Discussions

SSFP_SET_TEMPPSE return code 4 RFC destination.

Former Member — Sat, 11 Nov 2006 08:21:26 GMT

In SSO2 transaction i have selected the RFC destination (ABC_110) and executed. In next screen i am getting following error.

" Function SSFP_SET_TEMPPSE Return Code 4 RFC Destination BPD_110

Administration not Possible (Local System of Release < 4.6C and no Connection To a

Issuinging System for the Logon Ticket

System BPD Client 110

certificate of the Issuing System for the Logon Ticket

Owner CN=BPD, OU=CLP, OU=CLP Power, O=SAP Trust Community, C=DE

Issuer CN=BPD, OU=CLP, OU=CLP Power, O=SAP Trust Community, C=DE

Serialal Number 00

Vaidity 19971001 000000 20380101 000000

Check Sum 18:15:F1:8F:62:07:D7:55:0D:DD:70:8A:97:BF:52:A1

profile Parameters login/create_sso2_ticket = 2

System BPD Is Creating Logon Tickets That Do not Include Its Certificate ("it showing green light")

The Certificate for System BPD Is not Included In the Certificate List for System (it showing red light)

System ETD Accepts Verified Logon Tickets for System BPD (green light)"

Earlier it was fine. Now i am not able to see the "activation button" on application tool bar.

I have checked ACL (strustsso2) certificate is there in place for client 110.

Please help me to solve this problem.

Thanks and regards

Seshu

Re: SSFP_SET_TEMPPSE return code 4 RFC destination.

Wolfgang_Janzen — Mon, 13 Nov 2006 12:23:04 GMT

When calling transaction STRUST: are error messages / red lights also reported, there?

Re: SSFP_SET_TEMPPSE return code 4 RFC destination.

Former Member — Mon, 13 Nov 2006 12:28:22 GMT

Thanks!

There are no error messages/red lights are reported when i called transaction STRUST.

Regards

Seshu

Re: SSFP_SET_TEMPPSE return code 4 RFC destination.

Wolfgang_Janzen — Mon, 13 Nov 2006 12:37:12 GMT

Where did you run transaction STRUST - in the local system or in the remote system? You should run it in the remote system (BPD, client 110).

I assume that the user used in the RFC communication (destination BPD_110) is not equipped with sufficient authorizations. Therefore I'd recommend to run SSO2 and enter the physical connection data (hostname + instance number of the ticket issuer) instead of an RFC destination. You will then be prompted for logon data; enter logon data of a priveledged user (who is allowed to run transaction STRUST) and no problems should occur. Notice: the logon data that you enter in the "remote logon screen" will not be stored (in contrast to SM59 destinations).

Cheers, Wolfgang

Re: SSFP_SET_TEMPPSE return code 4 RFC destination.

Former Member — Tue, 14 Nov 2006 05:28:37 GMT

We have done the same. Its fine there were no red traffic lights and the error (SSFP_SET_TEMPPSE return code 4 RFC destination ) not displayed when i executed with the previlige user.

We are accessing SRM server with internal url (srmspd01.corp.plp.com) and from that screen when we click on collabratiion bid invitation we are able to logon to cFolder server with SSO method without any problem. At SRM server in RFC connections we have maintained cFolder server (etdspd01.corp.plp.com).

Problem is, for external users we are published one external URL (esp11.plpgroup.com) . External users can access SRM application by using this external URL. This URL will first hit the ISA 2004 server, there we have activated link translator and mapped external URL to internal URL. After they accessed the SRM application, when they click on collabration bid link, it prompting for the user id and password. The same user not able to logon to the cFodler server by SSO method. Earlier there is no problem, it is working fine. Suddenly external users facing SSO problem.

Please help me to solve this problem.

Thanks and regards

Seshu

Re: SSFP_SET_TEMPPSE return code 4 RFC destination.

Former Member — Tue, 14 Nov 2006 07:32:27 GMT

Hi Seshu,

did the problem appear after activating the link translator on the ISA Server ?

Re: SSFP_SET_TEMPPSE return code 4 RFC destination.

Former Member — Tue, 14 Nov 2006 08:43:12 GMT

No, actually there was no SSO problem to cFolder server after activating the link translator. This problem has come recently that external users not able to access cFolder by SSO method.

In the process i have checked SSO2 transaction, i have found this error SSFP_SET_TEMPPSE returncode 4 RFC destination. earlier i havent found this error. As you said i have executed SSO2 transaction with previliged user.. I havent seen this error. But the SSO problem from external URL to cFoder server is still there..

Please help me to trouble shoot this problem.

Thanks and regards

Seshu.

Re: SSFP_SET_TEMPPSE return code 4 RFC destination.

Former Member — Tue, 14 Nov 2006 09:18:25 GMT

Hi Seshu,

what do you mean, that you get an error, if the user does not have the rights in transaction SSO2. Usually, you should only be able to use this transaction as an admin.

Re: SSFP_SET_TEMPPSE return code 4 RFC destination.

Former Member — Tue, 14 Nov 2006 09:27:47 GMT

I am trying this with admin user id only.

In ETD server, i have executed SSO2. at logical RFC destination i have given (BPD_110) and executed, i have got (SSFP_SET_TEMPPSE return code 4 )error.

if i give (BPD_120) as a logical system, i am not getting this error.. and all traffic lights showing green lights. what could be the reason..?

Thanks and regards

Seshu

Re: SSFP_SET_TEMPPSE return code 4 RFC destination.

Former Member — Tue, 14 Nov 2006 10:07:17 GMT

based on this, I would guess, the system has trouble to reach the system behind BPD_110. So the RFC Destination could be wrong. What is the difference between BPD_110 and BPD_120 ?

Re: SSFP_SET_TEMPPSE return code 4 RFC destination.

Former Member — Tue, 14 Nov 2006 10:30:16 GMT

I have checked the RFC connections for both clients.. there is no difference in RFC connections.

Thanks and regards

seshu

Re: SSFP_SET_TEMPPSE return code 4 RFC destination.

Former Member — Tue, 14 Nov 2006 10:36:40 GMT

The user for this connection, is he admin in the remote system ?

Maybe you can just delete BPD_110 and have it recreated using SSO2.

Re: SSFP_SET_TEMPPSE return code 4 RFC destination.

Former Member — Tue, 14 Nov 2006 11:56:13 GMT

Hi,

Have you tried to call transaction code strustsso2, right click on the 'System PSE' and choose 'Replace'?

Best regards,

Agoes

Re: SSFP_SET_TEMPPSE return code 4 RFC destination.

Wolfgang_Janzen — Fri, 17 Nov 2006 12:33:32 GMT

Caution: do not simply replace an PSE.

That will cause data loss (=> loosing all imported certificates which are stored in the "certificate list" / "address book" of that PSE) - and you will invalidate all existing trust relationships / digital signatures (since you create a new key pair).

I'd recommend to submit a support report to SAP.

Using a remote connection it should be possible to analyse the cause of the problem.

Regards, Wolfgang