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.

Similar Messages

  • Will multiple Lan cards cause problems using rmi?

    Will multiple Lan cards cause problems using rmi? If a host has two or more network cards (only one of which is Internet-enabled), how does RMI know which IP address to use? There seems to be a problem when such a client registers with an RMI service, and has a client-side callback method invoked by the server.

    You can tell RMI the address you want by defining java.rmi.server.hostname at the JVM which exports the remote object.

  • Multiple Address Books causing problem syncing

    I use Desktop Manager to syncronize my address book.  On my BB, I have two address books for some reason.  One only has 39 entries and that is also what is showing in my Outlook.  The other address book has 234 entries that are not showing in my Outlook.  I need all 273 in my device and Outlook.
    Please help.

    Hi
    I had the same (two adessbooks [DESKTOP]after switching from BIS/Outlook to BES /Lotus Notes
    after a while I also discovered that camera pictures where stored to device memory, wheras movies to the mem-card
    another thing: first phonecall on a day was silent - no ringtone.
    I thought internal databases must be screwed up..
    I wiped device and re-did the firmware update 
    all good now and all flaws fixed..
    I blamed the BIS -BES switch  , don't know if I'm right..
    interestingly, I expected that Contacts,Calendar and email to be be updated on the air via BES
    but I also found my Browser favorites reloaded ! Big Brother RIM or is it my employer?
    good luck

  • 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

  • Issuing Multiple MYSAPSSO2 tickets for Multiple Domains

    Hi,
    I am having a problem understanding the SAP documentation on how to go about issuing SAP login tickets in multiple domains. In the documentation it states that in order to do so, you require either a IRJ or the SAP ISAPI Web Filter installed in on a server in the target Domain. I have now setup the IIS_SSO.dll ISAPI filter in the domain I require the SSO ticket to be issued in however when I make a request to that webserver I do not see the MYSAPSSO2 cookie being created in my browser, I do see in the ISAPI logs that the request has been filtered and the portal username extracted and set to the configured HTTP Header, but no new Cookie created in the DOMAIN.
    Can anyone help? Has anyone done something like this before?
    Basically I have a portal in the domain <b>myportal.subdomain.domain.com</b> and an ITS in the domain <b>myits.domain.com</b>. With this configuration the MYSAPSSO2 cookie is not sent to the ITS server as it is in a Super Domain. So what I want is to configure the portal to issue a Cookie in the super domain (domain.com) rather then subdomain.domain.com. I thought I could do this with the parameter login.ticket_recieving_hosts in the usermanagment.properties file (EP5) and the IIS ISAPI filter to SSO (IIS_SSO.dll) configured on a website in the super domain (domain.com).
    Any help would be greatly appriciated.
    Simon.

    I believe we had to set the domain relax level (ume.logon.security.relax_domain.level) but needed to make sure this was secure since it changes the domain scope of cookies that are valid for the system.
    See the following:
    http://scn.sap.com/thread/1534863
    http://help.sap.com/saphelp_nw70ehp3/helpdata/en/5e/473d4124b08739e10000000a1550b0/frameset.htm
    Hope this helps.

  • 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

  • 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

  • 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.

  • Do I use same oracle account on 2 cluster nodes cause problem?

    Do I use same oracle account on 2 cluster nodes cause problem?
    If I use same oracle account on 2 cluster nodes running 2 database, when failover happens, 2 database will be running on one node, does 2 oracle account make SHM ... memory conflict?
    or do I have to use oracle01 account on node1, oracle02 account on node2? Can not use same name account?
    Thanks.

    I'm not 100% certain I understood the question, so I'll rephrase them and answer them.
    Q. If I have the same Oracle account on each cluster node, e.g. uid=100 (oracle) gid=100 (oinstall), groups dba=200, can I run two databases, one on each cluster node without problems?
    A. Yes. Having multiple DBs on one node is not a problem and doesn't cause shared memory problems. Obviously each database needs a different database name and thus different SID.
    Q. Can I have two different Oracle accounts on each cluster node e.g. uid=100 (oraclea) gid=100 (oinstall), groups dba=200 and e.g. uid=300 (oracleb) gid=100 (oinstall), groups dba=200, and run two databases, one for each Oracle user?
    A. Yes. The different Oracle user names would need to be associated with different Oracle installations, i.e. Oracle HOMEs. So you might have /oracle/oracle/product/10.2.0/db_1 (oraclea) and /oracle/oracle/product/11.0.1.0/db_1 (oracleb). The ORACLE_HOME is then used to determine the Oracle user name by checking the user of the Oracle binary in the ${ORACLE_HOME}/bin directory.
    Tim
    ---

  • 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........
    <b>How configure UWL in Portal 7.0,
    Problem configuring UWL,</b>
    regards
    bhargava

  • SSO ticket expired !!

    Hi ,
      we are running EP 7.0 (NW04s) and we are getting following error in ESS
    while opening it,
    <b>com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: System received an expired SSO ticket</b>
         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

  • 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

  • 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

  • Null values from DB2 cause problems

    Hi,
    I have another problem with database link to DB2 using IBM iSeries Access for Linux on 64 bit OEL5 with Oracle Database gateway and unixODBC 2.2.14.
    DB link works. However, null values from DB2 cause problems. Date columns that are null on db2 return a date '30.11.0002', and character columns that are null return an error ORA-28528: Heterogeneous Services datatype conversion error.
    isql returns correct results.
    How can i fix this? Perhaps set some parameters for data conversion on the gateway?
    Thank you.

    If the driver is not fully ODBC level 3 compliant and misses functions, we're lost. But sometimes the drivers are ODBC level 3 compliant but miss the correct 64bit implementation. In those cases we can tell the gateway to use the 32bit ODBC level 3 standard by setting in the gateway init file:
    HS_FDS_SQLLEN_INTERPRETATION=32

  • I want to uninstall ReloadEvery as I think it is causing problems however it is not in my list of Extensions or Plugins yet it is clearly installed, I tried reinstalling FF but it was still there! How can I get rid of it?

    I installed ReloadEvery a while ago and it seemed to be working fine however I am now having problems with FF crashing and weird things like pages not reloading and not being able to use the back button etc
    I have already tried uninstalling and reinstalling FF and upgrading to FF 4.
    When I upgraded to FF 4 I was still having problems even though I didn't have any Extensions installed at all, or so I thought. I noticed that ReloadEvery was still installed. I was rather puzzled as I had done a clean install of FF 4. I want to remove ReloadEvery to see if it will solve my problems.
    I have also tried following the help on the FF Troubleshooting about manually uninstalling Extensions but again ReloadEvery not listed there yet I am still able to use it in FF!
    I want to get rid of it!! I really need some help please.

    Clear the cache and the cookies from sites that cause problems.
    "Clear the Cache":
    *Tools > Options > Advanced > Network > Cached Web Content: "Clear Now"
    "Remove Cookies" from sites causing problems:
    *Tools > Options > Privacy > Cookies: "Show Cookies"
    If clearing cookies doesn't work then it is possible that the <i>cookies.sqlite</i> file that stores the cookies is corrupted.
    Rename (or delete) <b>cookies.sqlite</b> (cookies.sqlite.old) and delete other present cookie files like <b>cookies.sqlite-journal</b> in the Firefox Profile Folder in case the file cookies.sqlite got corrupted.
    *http://kb.mozillazine.org/Cookies

Maybe you are looking for