SSO ticket expired !!

Hi ,
we are running EP 7.0 (NW04s) and we are getting following error in ESS
while opening it,
com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: System received an expired SSO ticket
 at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)
 at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1015)
 at com.sap.mw.jco.JCO$Client.connect(JCO.java:3238) ................
and strangely we are facing this problem for few user id's. its not generic problem
also if i delete cookies and temp files from internet option, it works for some time ,
then throws same error again.
finally clearing temp files and cookies also works on some system.
Any suggestion would be appreciated.
Thanks in advance
Abhay

Hey,
For those perticular users, there shoud be an active session in R/3. In SM04 delete the sessions opened by JCo user.
Look at following threads
Re: System received an expired SSO ticket
SSO ticket expires
SAP Note 825149--SSO ticket expired
Cheers!!
AShutosh

Similar Messages

RFC_ERROR_LOGON_FAILURE: System received an expired SSO ticket

Hi All,
We installed NW 7.0 SP 14 with EP 7.0; All the post-installation steps were completed and JCo's configured with SSO to backend ECC 6.0 system.
Since morning we are getting he below mention error when trying to test the JCo's for all the users.
com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: System received an expired SSO ticket.
Tried many variations and also changed the Ticket expiration time(to 24 from 8) restarted the server but the problem still remains. Can any one suggest any more ideas on how to sole this?
Is this problem any where related to CR Content? If so can you suggest how to check the current veriosn and how to find out the exact level which would be supported for our NW system.
Thanks in advace for you help.
Thanks,
Sravanthi

Hi,
Your portal certificate has expired.
To renew - you need to generate a new one in the ticket keystore using Visual Admin.
Next you export the new updated ticket to the trusting system (in yoru case ECC) using tcode STRUSTSSO2.
You then import the ticket and assign it to the ACL.
Issue should then be resolved.

UWL config-S ystem received an expired SSO ticket not found in system

Hi All,
We are getting following erro while configuring UWL.
Exception type:com.sap.netweaver.bc.uwl.connect.ConnectorException Message:uwlExceptionID: 1179143938021 :uwlExceptionID: 1179143938021 JCO Function template USER_NAME_GET:SAPR3CLNT900WF:com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: System received an expired SSO ticket not found in system
Please HELP.
Rgds
Ganga

hi ganga,
may be there is problem with uwl configuration. u try with this link....
hope ur error will clear........
How configure UWL in Portal 7.0,
Problem configuring UWL,
regards
bhargava

Usually this system rejects access using SSO tickets exception

Hi,
I'm facing a problem when trying to access to some tasks in the UWL.
It appears an error message saying "Usually this system rejects the access using SSO tickets" (it's not an accurate translation, the message in spanish says "Generalmente este sistema rechaza el acceso mediante ticket SSO").
The same happens when I try to access to the backend system (R/3 Release 4.6C) using an iView.
At first I thought it was a problem related with the certificate between the backend and the portal, but we have reimported the certificate in the backend and the problem still happens. And the certificate doesn't expire until 2012.
I have restarted the J2EE Engine too, but it continues the same.
What is extrange is that all the WebDynpro applications that call RFCs in the backend system work fine and get the information.
Anybody knows what can I do to solve this problem? Yesterday all worked fine and this morning I saw all this.
The release is Enterprise Portal 6.0 SP18.
Thank you very much! All help would be highly appreciated (and rewarded)!

You can check the following
- the following profile parameters are set
login/create_sso2_ticket = 2
login/accept_sso2_ticket = 1
- if the corresponding R3 user is not locked or expired
- if the portal certificate is added to the ACL list of the R/3 System (using STRUSTSSO2)
Regards,
Abhishek

Setting of SSO ticket life time in EP7

Hi guys,
We are having some problem with the lifetime of the SSO ticket, it will auto expire in less than 5 minutes time.
These are what we have done so far:
1) In RZ10, set the "login/accept_sso2_ticket = 1", "login/create_sso2_ticket = 1", "login/ticket_expiration_time = 48"
2) set the ITS timeout as 3600 seconds
3) set the UME property login.ticket_lifetime to 8 hours (Default)
FYI, we are using EP7.0 with the 4.6C.
I remember that in EP6, we can set it under the System Administration > System Configuration > UM Configurations > Security Settings > Lifetime of SAP Logon Ticket
However, in EP7 we can't find any setting for logon ticket under the System Administration > System Configuration > UME Configurations > Security Policy
Do you have any similar experience in your previous project before?
Appreciate for any suggestion or comment.
Thanks,
Justin Yee

Hi Justin,
You can also use the Global settings in Visual Admin. UME Provider service has property SSO_Ticket_Lifetime.
Best regards,
Jan Laros

Unable to Interpret SSO Ticket Recieved.

Hai ,
While working in ESS , I tried to create travel request. While creating i recieved Error message.
Error: System is Unable to Interpret SSO ticket recieved.
Kindly Help me out.
Regards
ArunRajan,
Hosur

Hi,
Please check tha SSO is configured correclty & test is fine from both Portal & Back-end side.
Please refer to
[http://help.sap.com/saphelp_nw70/helpdata/EN/4d/dd9b9ce80311d5995500508b6b8b11/content.htm|http://help.sap.com/saphelp_nw70/helpdata/EN/4d/dd9b9ce80311d5995500508b6b8b11/content.htm]
In case you still face an issue, then please let me know.

A failure occured while importing Java SSO ticket certificate in ABAP stack Exception : FOREIGN_ENQUEUE_LOCK

Dear All,
We have completed the fresh installation of Soman7.1.
Now , We are doing the "Configuration of the Solman" and we are in the Step "Basic configuration ".
SID: SMI
Hostname: Solmantrg
Solman version: 7.1
The SSO Setup is failing with below error.
Message :
A failure occured while connecting to ABAP stack on solmantrg.thetimes.co.in sys=01 client=001 user=null. Details : 'user' missing
Details of the Log
Found SID for SSO ACL entry : SMI
Found login.ticket_client for SSO ACL entry : 000
The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc~webadministrator~solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
ABAP SSO ticket certificate of SMI was imported in ABAP PSE of solmantrg.thetimes.co.in (client 001)
The ABAP SSO ticket certificate was successfully imported in ABAP System PSE, and the ACL updated accordingly (SID=SMI LoginTicketClient=001)
A failure occured while importing Java SSO ticket certificate in ABAP stack
!! Exception : FOREIGN_ENQUEUE_LOCK(Abap cause=SOLMAN_ADMINE_TABLEE)
The ABAP instance profile contains the parameter : login/accept_sso2_ticket=1
The SSO ticket Certificate <CN=SMI> has been successfully imported into Java Keystore
The com.sap.security.core.server.jaas.EvaluateTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
The Authentication template for component sap.com/SQLTrace*OpenSQLMonitors was already set to ticket
The Authentication template for component sap.com/SQLTrace*SQLTrace was already set to ticket
The Authentication template for component sap.com/tc~monitoring~systeminfo*monitoring was already set to ticket
The Authentication template for component sap.com/tc~monitoring~systeminfo*sap_monitoring was already set to ticket
The Authentication template for component sap.com/com.sap.security.core.admin*useradmin was already set to ticket
The Authentication template for component sap.com/tc~webadministrator~solmandiag*smd was already set to ticket
The Authentication template for component sap.com/tc~smd~e2etraceupload*E2EClientTraceUploadW was already set to ticket
The com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
The Authentication template for component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1 has been set to evaluate_assertion_ticket
The Login Module BasicPasswordLoginModule was added to the security component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1
A failure occured while connecting to ABAP stack on solmantrg.thetimes.co.in sys=01 client=001 user=null
!! Exception : 'user' missing
The ABAP instance profile contains the parameter : login/create_sso2_ticket=2
Exception
com.sap.mw.jco.JCO$AbapException: (126) FOREIGN_ENQUEUE_LOCK: FOREIGN_ENQUEUE_LOCK
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1512)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3937)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3570)
at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:276)
at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:249)
at com.sap.sup.admin.setup.ManagingServices.setupDualStackSSO(ManagingServices.java:752)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:564)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:445)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:674)
at com.sap.sup.admin.setup.ws.SetupWrapper._diagSetup(SetupWrapper.java:279)
at com.sap.sup.admin.setup.ws.SetupWrapper.diagSetup(SetupWrapper.java:21)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:76)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)
at SoapServlet.doPost(SoapServlet.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
========================
com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'user' missing
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:518)
at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1087)
at com.sap.mw.jco.JCO$Client.connect(JCO.java:3310)
at com.sap.sup.admin.setup.CommonServices.getJcoClient(CommonServices.java:773)
at com.sap.sup.admin.setup.CommonServices.getJcoClient(CommonServices.java:722)
at com.sap.sup.admin.setup.SolManRfcAdapter.getJ2eeSsoSettings(SolManRfcAdapter.java:649)
at com.sap.sup.admin.setup.ManagingServices.updateSSOfromURLrepository(ManagingServices.java:790)
at com.sap.sup.admin.setup.ManagingServices.setupDualStackSSO(ManagingServices.java:773)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:564)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:445)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:674)
at com.sap.sup.admin.setup.ws.SetupWrapper._diagSetup(SetupWrapper.java:279)
at com.sap.sup.admin.setup.ws.SetupWrapper.diagSetup(SetupWrapper.java:21)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:76)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)
at SoapServlet.doPost(SoapServlet.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
In strustsso2, cerficate date is valid only.
kindly help us to fix this SSO_Setup issue
Thanks and Regards,
Gayathri.K

Hi ,
Thanks for the above reply.
I have executed the Step 2.3 AND 2.4 and i started the SSO Setup again. Still i am getting below error
Message
A failure occured while importing Java SSO ticket certificate in ABAP stack
Details Of the Log
Found SID for SSO ACL entry : SMI
Found login.ticket_client for SSO ACL entry : 000
The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc~webadministrator~solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
ABAP SSO ticket certificate of SMI was imported in ABAP PSE of solmantrg (client 001)
The ABAP SSO ticket certificate was successfully imported in ABAP System PSE, and the ACL updated accordingly (SID=SMI LoginTicketClient=001)
A failure occured while importing Java SSO ticket certificate in ABAP stack
!! Exception : FOREIGN_ENQUEUE_LOCK(Abap cause=SOLMAN_ADMINE_TABLEE)
The ABAP instance profile contains the parameter : login/accept_sso2_ticket=1
The SSO ticket Certificate <CN=SMI> has been successfully imported into Java Keystore
The com.sap.security.core.server.jaas.EvaluateTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
The Authentication template for component sap.com/SQLTrace*OpenSQLMonitors was already set to ticket
The Authentication template for component sap.com/SQLTrace*SQLTrace was already set to ticket
The Authentication template for component sap.com/tc~monitoring~systeminfo*monitoring was already set to ticket
The Authentication template for component sap.com/tc~monitoring~systeminfo*sap_monitoring was already set to ticket
The Authentication template for component sap.com/com.sap.security.core.admin*useradmin was already set to ticket
The Authentication template for component sap.com/tc~webadministrator~solmandiag*smd was already set to ticket
The Authentication template for component sap.com/tc~smd~e2etraceupload*E2EClientTraceUploadW was already set to ticket
The com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
The Authentication template for component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1 has been set to evaluate_assertion_ticket
The Login Module BasicPasswordLoginModule was added to the security component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1
The ABAP instance profile contains the parameter : login/create_sso2_ticket=2
Exception
com.sap.mw.jco.JCO$AbapException: (126) FOREIGN_ENQUEUE_LOCK: FOREIGN_ENQUEUE_LOCK
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1512)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3937)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3570)
at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:276)
at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:249)
at com.sap.sup.admin.setup.ManagingServices.setupDualStackSSO(ManagingServices.java:752)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:564)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:445)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:674)
at com.sap.sup.admin.setup.ws.SetupWrapper._diagSetup(SetupWrapper.java:279)
at com.sap.sup.admin.setup.ws.SetupWrapper.diagSetup(SetupWrapper.java:21)
at sun.reflect.GeneratedMethodAccessor2202.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:76)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)
at SoapServlet.doPost(SoapServlet.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Also , i have checked the note # 1008474 Diagnostics Setup Wizard uses wrong ABAP client.
As mentioned in above note, i have checked in visual admin all settings are maintained correctly.
RFC destination WEBADMIN & SOLMANDIAG is also working fine.
please tel why i am getting Foreign Enquelock
Regards,
Gayathri.K

Problem accessing R/3 with SSO ticket from the EP6.0

Hi all,
I have seen this thread: Problem accessing R/3 with SSO ticket from the EP6.0
I know that it is possible to read SSO ticket from the Cookie in WebDynpro application.
Now we are at the first step, we don't know how to read SSO ticket from the Cookie in WebDynpro application with java code.
So anyone can help us?

Hi,
This has been discussed in a previous forum.Check this link.A code snippet is also there to read a cookie in webdynpro with this question
How to implement SSO between Portal, Webdypro and ABAP system?
I am not able to send the link exactly.
Regards,
Sowjanya.
Message was edited by: Sowjanya Chintala

RFC_ERROR_LOGON_FAILURE: This system rejects all logons using SSO tickets

hello again,
i manage to restart my server and applications
but now when i try to start :
http://host:port/b2b/b2b/init.do
and i can't
the logs show these line which i don't understand :
1}#2#parameters: [client]='null' [user]='null' [language]='null' [ashost]='null' [systemnumber]='null' [mshost]='null' [gwhost]='null' [gwserv]='null' [group]='null' [systemid]='null'
Properties: {lang=en, passwd=?, sysnr=01, client=300, user=$MYSAPSSO2$, ashost=192.168.1.14, jco.client.type=A, maxcon=0, jco.client.trace=1, codepage=1100}
Client not connected#com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'mysapsso2' missing
 at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:456)
 at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:922)
 at com.sap.mw.jco.JCO$Client.connect(JCO.java:3171)
 at com.sap.isa.core.eai.sp.jco.JCoConnectionStateless.getInternalJCoClient(JCoConnectionStateless.java:118)
 at com.sap.isa.core.eai.sp.jco.JCoConnectionStateless.isValid(JCoConnectionStateless.java:479)
 at com.sap.isa.user.backend.crm.IsaUserBaseCRM.loginViaTicket(IsaUserBaseCRM.java:1677)
 at com.sap.isa.user.backend.crm.IsaUserBaseCRM.loginForBPRole(IsaUserBaseCRM.java:127)
 at com.sap.isa.user.backend.crm.UserBaseCRM.login(UserBaseCRM.java:248)
 at com.sap.isa.user.businessobject.UserBase.login(UserBase.java:308)
#1.5#000423A6E1B400640000002E0000169C00041D66DC92778B#1158227531375#tracing.isa.runtime#sap.com/crm~b2b#tracing.isa.runtime#ABAHMANE#466##crm_CRM_15121750#ABAHMANE#a4727b3043d611dbc03b000423a6e1b4#SAPEngine_Application_Thread[impl:3]_17##0#0#Debug##Plain###[actionxecution]='end' [actionclass]='com.sap.isa.user.action.LoginBaseAction' [path]='/login' [forward]='/base/error_ume.jsp' [exectime]='32'#
#1.5#000423A6E1B400480000000F0000169C00041D66DCE4AE38#1158227536750#tracing.advisor.method#sap.com/crm~b2b#tracing.advisor.method#ABAHMANE#466##crm_CRM_15121750#ABAHMANE#a4727b3043d611dbc03b000423a6e1b4#SAPEngine_Application_Thread[impl:3]_8##0#0#Debug##Plain###AdvisorBusinessObjectManager:<constructor>#
#1.5#000423A6E1B40048000000120000169C00041D66DCE4B676#1158227536765#tracing.isa.runtime#sap.com/crm~b2b#tracing.isa.runtime#ABAHMANE#466##crm_CRM_15121750#ABAHMANE#a4727b3043d611dbc03b000423a6e1b4#SAPEngine_Application_Thread[impl:3]_8##0#0#Debug##Plain###[actionxecution]='begin' [actionclass]='com.sap.isa.isacore.action.IsaCoreInitAction' [path]='/b2b/coreinit'#
#1.5#000423A6E1B40048000000130000169C00041D66DCE4C261#1158227536765#tracing.isa.runtime#sap.com/crm~b2b#tracing.isa.runtime#ABAHMANE#466##crm_CRM_15121750#ABAHMANE#a4727b3043d611dbc03b000423a6e1b4#SAPEngine_Application_Thread[impl:3]_8##0#0#Debug##Plain###[actionxecution]='end' [actionclass]='com.sap.isa.isacore.action.IsaCoreInitAction' [path]='/b2b/coreinit' [forward]='/user/performLogin.do' [exectime]='0'#
#1.5#000423A6E1B40048000000140000169C00041D66DCE4C607#1158227536765#tracing.isa.runtime#sap.com/crm~b2b#tracing.isa.runtime#ABAHMANE#466##crm_CRM_15121750#ABAHMANE#a4727b3043d611dbc03b000423a6e1b4#SAPEngine_Application_Thread[impl:3]_8##0#0#Debug##Plain###[actionxecution]='begin' [actionclass]='com.sap.isa.core.action.SetReloginCookieAction' [path]='/relogin/setcookie'#
#1.5#000423A6E1B4004800000
many thnx if you can help me

it doesn't work ..
i need to understand the meaning of SSO ticket in sap logon..
i still have the error :
parameters: [client]='null' [user]='null' [language]='null' [ashost]='null' [systemnumber]='null' [mshost]='null' [gwhost]='null' [gwserv]='null' [group]='null' [systemid]='null'
Properties: {lang=en, passwd=?, sysnr=01, client=300, user=$MYSAPSSO2$, ashost=192.168.1.14, jco.client.type=A, maxcon=0, jco.client.trace=1, codepage=1100}Client not connected#com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'mysapsso2' missing
 at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:456)
why does it replace the user i mapped in XCM JCO setting with the user 'mysapsso2' ?
plz help me

Impact of Hardware Change on SSO tickets

Hi Experts,
We are carrying out a hardware refresh of our production EP database server. Hardware refresh involves changing the server on which the EP database & application servers are residing with no change in the Hostname and IP addresses for the EP servers.
We use SSO tickets to connect our EP system to our ECC6 system for accessing ESS/MSS functionality & are doing an impact analysis before the hardware refresh & would like to check if there can be any impact to the single sign on setup between our EP & ECC6 system.
Appreciate any comments. Thanks.
Regards,
Murali

Hi,
There should be no effect at all unless and until Hostname and IP address does not change.
With Regrads,
Saurabh

Multiple SSO Tickets Cause Problem

Dear SAP Fellas,
Our customer implemented NWBC based travel management into ECC6 based HR system.
It uses its own SSO tickets, when users log on via webbrowser, it is working fine.
In this landscape there is an Enterprise Portal used for other purposes, but also issues its own SSO tickets.
When this portal is also used at the same time or was used before (so an 'alien' SSO ticket is in the browser's cache), ECC6 changes logon style, username and password fields are greyed out and asks user to press a button for an additional popup window, where username and password can be typed in. This behavior breaks NWBC's operation internally, every clicks on menuitems invokes this password window.
Do you know any way to teach this ECC6 system to process only its own SSO ticket and ignore others?
Thank you for answers in advance.

Dear SAP Fellas,
Our customer implemented NWBC based travel management into ECC6 based HR system.
It uses its own SSO tickets, when users log on via webbrowser, it is working fine.
In this landscape there is an Enterprise Portal used for other purposes, but also issues its own SSO tickets.
When this portal is also used at the same time or was used before (so an 'alien' SSO ticket is in the browser's cache), ECC6 changes logon style, username and password fields are greyed out and asks user to press a button for an additional popup window, where username and password can be typed in. This behavior breaks NWBC's operation internally, every clicks on menuitems invokes this password window.
Do you know any way to teach this ECC6 system to process only its own SSO ticket and ignore others?
Thank you for answers in advance.

Portal behaviour after Login Ticket expire

Hi.
We setup Logon Ticket life time to "00:10" in Portal UME.
After 10M, Logon Ticket expired and I have to logon again.
When User try to access portal contents after Logon Ticket expired, Portal just create error message.
I want to move Portal login page after Logon Ticket expired.
Is there any method ?
Regards, Arnold.

closing the thread..

We got error "System is unable to interpret the SSO ticket received"

We got error "System is unable to interpret the SSO ticket received" on Backend system(R/3 4.7).
We use SAP Enterprise Portal 6.0 SP15.
Please let us know what is problems ?
We done following steps in SAP EP.
1. Created LOGON-METHOD (Logon Method : SAPLOGONTICKET).
2. Export Public-key (verify.der) from SAP EP.
   (System Admin -> System config -> Keystore Administration -> Download)
We done following steps in SAP R/3.
3. Start STRUSTSSO2 Transaction.
   In the PSE status frame on the left, choose the system PSE.
   In the certificate section, choose Import Certificate.
     The Import Certificate screen appears.
   Choose the File tab.
   In the File path field, enter the path of the portal's verify.der file.
   Set the file format to DER coded and confirm.
   In the Trust Manager, choose Add to PSE.
   Choose Add to ACL, to add the Portal Server to the ACL list.
   In the dialog box that appears, enter follows:
     system ID    :J2E
     client       :000
     Subject name :CN=J2E
     Issuer name :CN=J2E
     Serial number:00
   Save your entry.
4. Set profile parameters
   login/accept_sso2_ticket = 1
   login/create_sso2_ticket = 0
5. Restart SAP R/3 system.

Hi,
I faced the same problem when i am configuring the SSO,
check the portal client number in System Administration>System Configaration->UM Configuration--->Direct Editing
and give the same client number
In the dialog box that appears,
system ID :J2E
client :000
else check weather u r importing the certificate correctly.
First export the verify.der and and import that using the STRUSTSSO2
Thanks
Ajay

RFC_ERROR_LOGON_FAILURE: The system is unable to interpret the SSO ticket

Hi folks,
i've here an issue that i could not solve, i've implemented SSO between SAP EP and SAP ERP 2005 several times but this time i've the error message
" The system is unable to interpret the SSO ticket received"
I've already imported portal certificate, put parameters in instance profile and restart ERP but it still gave the error, i found the same issue from others sdn users but none of then have the solution for me.
Could anyone help me here?
This is a urgent matter.
thanks in advance,
Pedro Rodrigues

Hi Pedro,
what result do you get in a connection test in the portal ?
To do that :
open the System definition (under System Administrator/System Configuration);
Open the ERP 2005 system entry> "Connection Test"
Select "Connection test for Connector".
Also make sure that the domain of both systems (portal and ERP) are the same e.g. portal.company.com and erp.company.com . IP addresses are not working in SSO....
Also helpful is the OSS 701205 which has a attached PAR file for testing the SSO.
Regards,
Kai

The system is unable to interpret the SSO ticket received

Hi,
We are facing the following error. Could anyone please help us understand/resolve the same
com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: The system is unable to interpret the SSO ticket received
     at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java(Compiled Code))
     at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java(Compiled Code))
     at com.sap.mw.jco.JCO$Client.connect(JCO.java(Compiled Code))
     at com.sap.mw.jco.JCO$Pool.initPool(JCO.java(Compiled Code))
     at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java(Compiled Code))
     at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java(Inlined Compiled Code))
     at com.sap.mw.jco.JCO.getClient(JCO.java(Inlined Compiled Code))
     at com.sap.mw.jco.webas.WebDynproExtension.addClientPool(WebDynproExtension.java(Compiled Code))
     at com.sap.mw.jco.webas.WebDynproExtension.addClientPool(WebDynproExtension.java(Compiled Code))
     at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.createPool(AbstractJCOClientConnection.java(Compiled Code))
     at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.checkPoolEntry(AbstractJCOClientConnection.java(Inlined Compiled Code))
     at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.getClient(AbstractJCOClientConnection.java(Compiled Code))
     at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModelInternal(BackendConnections.java:261)
     at com.sap.pcuigp.xssfpm.wd.BackendConnections.initBackend(BackendConnections.java:226)
     at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModel(BackendConnections.java:159)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.connectModel(InternalBackendConnections.java:183)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.connectModel(FPMComponent.java:699)
     at com.sap.pcuigp.xssfpm.wd.BackendConnections.init(BackendConnections.java:138)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.init(InternalBackendConnections.java:179)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:170)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java(Compiled Code))
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java(Inlined Compiled Code))
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java(Inlined Compiled Code))
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java(Compiled Code))
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:382)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:618)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code))
     at java.security.AccessController.doPrivileged1(Native Method)
     at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
- Harshal

Hello Erin,
1. Can you please confirm whether what type of SSO concept has been configured....whether Logon Tickets or user mapping?
If logon tickets, just check once if the same user-id exists on both systems.....
2. Can you also try pinging & testing the JCo in hte SLD....just confirmation.
Awaiting Reply.
Warm Regards,
Ritu

SSO ticket expired !!

Similar Messages

Maybe you are looking for