on 04-23-2014 1:02 PM
Hi
We are on Portal 7.3 ehp1 sp9.
Steps followed are :
RFC Destination called “SAP_RFC” has been created as below :
Configuration -> Destinations -> RFC Destinations
Connection and Transport:
-------------------------------------
Load balancing :Yes
Provided : SystemID / MS Server / MS Server Service / Logon Group / Gateway Host / Gateway Service
SNC : Inactive
Logon Data:
------------------
Authentication : Current User (Assertion Ticket)
Language : EN
Client : XXX
Repository Connection:
-----------------------------------
Destination Name : This Destination
Specific Data:
----------------------
pooled Connection Mode : Yes
Max : 5
Size : 10
Max. wait time : 10,000
Ping Destination results : Successfully connected to System XXX as per user XXXXXXX.
JAVA Code as Follows:
JCoDestination destination = JCoDestinationManager.getDestination("SAP_RFC");
//destination.ping();
JCoRepository repository = destination.getRepository();
JCoFunction function = repository.getFunction("FM_NAME");
function.execute(destination);
Lines highlighted in RED color throwing an error as below :
{"ERROR":"Initialization of destination JCO_RFC failed: Incomplete logon data. on <SID> mshost <MS_HOST>/ com.sap.conn.jco.JCoException: (103) JCO_ERROR_LOGON_FAILURE: Incomplete logon data. on SID mshost MS_HOST"}
And found that no COOKIE with the name “SAP_SESSIONID_<system>_<client>” was not found, I am afraid that “Assertion Ticket” was not created in above scenario.
To confirm SSO configuration working, i have followed below steps:
1) Created System Object pointing to R/3 and tests were successful for authentication type "SSOLOGONTICKET / ASSERTIONTICKET"
It's J2EE application, no references or any other additional configuration been made part from above.
Any help ?
Thanks
Here is log ..Assertion ticket could not be retrieved. Error was null
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mohan,
Hope you are doing good.
The error shows that the parameters are missing. can you check the parameters with the backend details. If teh issue persists, enable the JCo trace (to level 5) as per note 628962. Check:
<https://wiki.sdn.sap.com/wiki/display/SI/Java+Connectivity>
(check JCo trace activation via Java system properties)
Thank you and have a nice day :).
_____________
Kind Regards,
Hemanth
SAP AGS
Thanks for your reply.
Ping Destination results : Successfully connected to System XXX as per user XXXXXXX.
If anything missing / wrong, test would fail right ?
Before i proceed further, i would like to know whether the approach is correct or not ?
You can see above, an error message from trace file.
Error message from jco_rfc file : RfcGetException rc (7) message: Incomplete logon data.
Message from log viewer under NWA : Assertion ticket could not be retrieved. Error was null
Thanks
Hi Mohan,
I remember such an issue with a previous customer. There is a known issue with the assertion tickets. Please see note 1754939 No logged in user exception. Also, due to the intertwined dependencies, it is highly recommended to deploy the latest patches for the other SCAs as well mentioned in note 1794179 when you do a SCA upgrade. Deploy using any tool mentioned in sap note 1715441.
___________
Kind Regards,
Hemanth
SAP AGS
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.