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.

Similar Messages

  • 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

  • File to Idoc -- Unable to interpret IDoc interface mi_Orders05_In_Asyn..??

    Hi All,
    Im trying the File to Idoc scenario.. and im getting the following error in SXMB_MONI,
    Anyidea what might have gone wrong??
    <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
      <SAP:P1>mi_Orders05_In_Asyn</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      +<SAP:Stack>Unable to interpret IDoc interface mi_Orders05_In_Asyn</SAP:Stack>+
      <SAP:Retry>M</SAP:Retry>
    Waiting for your answers.
    Thank You.
    Seema.

    Hi Seema,
    I think you are using mi_Orders05_In_Asyn as the IDOC interface.
    Use the imported idoc as the interface. i.e you dont need to create Inbound Message interface for IDOC. You can use the imported idoc structure as interface.
    Let us know if that doesnt solve your problem.
    Regards,
    Sumit

  • Unable to interpret u3030u0081@ as a number - problem

    Hi,
    We've got problem with BPMs which use graphical (java) mapping. In SXI_MONITOR such processes have "Message being sent" status. In process engine workflow log it stops at mapping step with "In process" status. Technical details show that there is a tRFC call which fails with "Unable to interpret &#12336;@ as a number.". This is also visible in ST22. BPM without mapping works without any problems. Test mapping in integration repository works fine.
    Has anyone got any ideas?
    Kind regards,
    Michal Krawczyk

    Hi,
    Have you tested your mapping using the actual source message that caused the error in BPM?
    From the BPE monitor copy-n-paste the actual message into the Interface Mapping test tool.
    Regards,
    Bill

  • 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

  • Error: Unable to interpret / as a number

    We have an R/3 Infoset that is used as a source for some Crystal Report queries -- basically it is pulling some revenue recognition data from GLPCA and pairing it with supporting tables such as billing documents, orders, customer, material, etc.  This has been available in Production for a few months, but recently a user has started encountering the following messages at runtime:
    Crystal Reports
    Failed to retrieve data from the database.
    Database Connector Error: 'Unable to interpret / as a number.'
    Database Connector Error: 'RFC_INVALID_HANDLE'
    So we were able to even track down the error to one specific billing document and can recreate the error when selecting only the one document number.  The report errors whenever it pulls that data and if a certain amount field is brought in to the listing.  Looking at the underlying data through an SQL query, we don't see a problem with the data and have been unable to figure out why only certain records are causing this short dump.  The abend info in ST22 shows it is related to a CONVT_NO_NUMBER runtime error in ABAP program /CRYSTAL/SAPLFLAT - procedure /CRYSTAL/BUILD_STRING.  Looking through the details did not uncover much information that would point to the problem.
    Has anyone encountered this type of problem with Crystal integration to SAP data? Any suggestions on troubleshooting or identifying the problem would be appreciated.

    Hi,
    would suggest you open a case with support and provide the details on the steps so that the support folks can directly look at your system.
    thanks
    Ingo

  • 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

  • Unable to interpret IDoc interface ReplenishmentOrderNotification_In

    Hi All,
    I am trsfering orders03 idoc from r/3 4.5 B system to XI and from XI to SNC system using idoc adapter.
    In sxmb_moni, When I double click on particular XML message with errors
    I am getting error in call adapter
    details:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
      <SAP:P1>ReplenishmentOrderNotification_In</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to interpret IDoc interface ReplenishmentOrderNotification_In</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

    Hi
    I am creating JDBC to IDOC scenario but experiencing the same issue.
    Can you advise how you solved this?
    Thanks.

  • 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: <u>{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}</u>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

  • RFC_ERROR_SYSTEM_FAILURE: Unable to interpret * as a number

    Hi,
    I facing a strange problem while executing a query in bex analyzer and WAD. When I open a query it is throwing error as 'Unable to interpret * as a number'. I am getting this error before the pop-up menu itself. But all other reports are working fine. Please guide me to solve this issue.
    Regards
    Githen

    hi Githen Ronney  ,
    Is that query Standard OR customized one.
    If it is standard once check the SAP-EXIT variables.
    Thanks,
    KIran Manyam

  • 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

  • Error:Unable to interpret "TABLE".

    When I use BTE, There is an error in FM Z_WRITE_TO_QUEUE in R/3.
    FUNCTION Z_WRITE_TO_QUEUE.
    ""Local interface:
    *"  IMPORTING
    *"     REFERENCE(I_DATASOURCE) TYPE  ROOSOURCE-OLTPSOURCE
    *"  TABLES
    *"      I_T_DATA OPTIONAL
    TYPE-POOLS:
        sbiwa.
      DATA:
        l_exstruct TYPE roosource-exstruct,
        l_initflag TYPE roosprmsc-initstate,
        l_subrc    TYPE sy-subrc,
        lr_is_data TYPE REF TO data,
        lr_es_data TYPE REF TO data,
        lr_et_data TYPE REF TO data,
        l_t_fields TYPE sbiwa_t_fields,
        l_t_select TYPE sbiwa_t_select.
      FIELD-SYMBOLS:
        <i_s_data> TYPE ANY,
        <e_s_data> TYPE ANY,
        <e_t_data> TYPE STANDARD TABLE.
    Check to see if Delta initialization has been performed.
      SELECT SINGLE initstate FROM roosprmsc INTO l_initflag
             WHERE  oltpsource  = i_datasource
             AND    rlogsys     NE space
             AND    slogsys     NE space
             AND    initrnr     NE space.
    If initialization has taken place continue
      IF sy-subrc EQ 0 AND l_initflag EQ 'X'.
      grab the extraction structure from roosource based on the
      datasource parameter input.
        SELECT SINGLE exstruct FROM roosource INTO l_exstruct
               WHERE  oltpsource  = i_datasource
               AND    objvers     = 'A'.
        CHECK sy-subrc = 0.
        CREATE DATA lr_is_data LIKE LINE OF i_t_data.
        ASSIGN lr_is_data->* TO <i_s_data>.
        CREATE DATA lr_es_data TYPE (l_exstruct).
        ASSIGN lr_es_data->* TO <e_s_data>.
        CREATE DATA lret_data TYPE STANDARD TABLE OF (l_exstruct)._
          ASSIGN lr_et_data->* TO <e_t_data>.
        LOOP AT i_t_data ASSIGNING <i_s_data>.
          CLEAR <e_s_data>.
          MOVE <i_s_data> TO <e_s_data>.
         MOVE-CORRESPONDING <i_s_data> TO <e_s_data>.
          INSERT <e_s_data> INTO TABLE <e_t_data>.
        ENDLOOP.
        CALL FUNCTION 'EXIT_SAPLRSAP_001'
          EXPORTING
            i_datasource             = i_datasource
            i_isource                = ''
            i_updmode                = ''
          TABLES
            i_t_select               = l_t_select
            i_t_fields               = l_t_fields
            c_t_data                 = <e_t_data>
          EXCEPTIONS
            rsap_customer_exit_error = 1
            OTHERS                   = 2.
        IF sy-subrc <> 0.
          MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                  WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        ENDIF.
        CALL FUNCTION 'RSC1_TRFC_QUEUE_WRITE'
          EXPORTING
            i_isource     = i_datasource
            i_no_flush    = 'X'
          IMPORTING
            e_subrc       = l_subrc
          TABLES
            i_t_data      = <e_t_data>
          EXCEPTIONS
            name_too_long = 1
            OTHERS        = 2.
        IF sy-subrc <> 0.
          MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                  WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        ENDIF.
      ENDIF.
    ENDFUNCTION.
          FORM abs_type_to_rel_type                                     *
          The purpose of this subroutine is to convert an absolute type *
          name into a relative type name.                               *
    -->  TYPE_NAME                                                     *
    form abs_type_to_rel_type changing type_name.
      data junk(100) type c.
      split type_name at '\TYPE=' into junk type_name.
    endform.
    "CREATE DATA lr_et_data TYPE STANDARD TABLE OF (l_exstruct)" makes an Error "Unable to interpret "TABLE"."
    I don't why!
    So anbody can help me?
    Thank you!

    Hi,
    Use this statement.
    data:begin of lr_et_data occurs 0,
    include l_exstruct.
    end of lr_et_data.
    Ravi

  • Unable to interpret IDoc interface  Error

    Hi All,
    We are getting the following error while trying to translate a X12 to IDOC , we are using Seeburger Adapters for the translation.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
      <SAP:P1>I_867_ORDERS01_ZORDRS1X_PTD_SS</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Unable to interpret IDoc interface I_867_ORDERS01_ZORDRS1X_PTD_SS</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    The Reason we are using a Interface rather than using a IDOC directly is because our the IDOC Structure is 867.ORDERS01.ZORDRS1x and this is a custom IDOC in ECC and when we try to directly use the structure in the Interface Determination we get the error
    Check Result for Object ARROWUS | ARROWUS_IN_AS2 | A_867_V4010_ABS | | BS_ECC_D03_DEV
    First character invalid: 8 Only a(A)-z(Z), 0-9, and "/" and "_" are permitted
    Has anyone faced a similar problem ? If so please let me know how you fixed it.
    Appreciate your help
    Regards,
    Madhu

    have you seend below threads:
    [link1|Unable to interpret IDoc interface ZSHIPDEL_packageRD;
    [link2|IDOC Error;

Maybe you are looking for

  • Open all PDFs in same window option in Acrobat 9?

    All my PDFs open in separate windows/acrobat instances. There used to be a feature in option to allow all to open in same window. Cant seem to find it in verison 9.

  • Adobe webdynpro taking time too long

    Hi, Initially, I have Read Timed Out issue. I;ve incresed the Web Container timeout to 360 seconds. but now, when I run the program with Interavtive form, it tooks very long time. It's been 30 minutes and still going. I do see the log mentioned not f

  • Error in Soap Communication Channel

    Hi All, I am using Soap as sender from UPXI and again Soap as receiver in EUPI but while doing end to end test SOAP sender channel was failing. Below was the error which I cam seeing the channel mointoring. Message processing failed. Cause: com.sap.e

  • Installing J2SE

    Hey all, it's me perlgoodies but I forgot my password and can't change it because I didn't setup a password reminder thing. I formatted a few days ago and had to reinstall everything. Now I can't get javac to work, it keeps saying it's not a command

  • IMovieHD Aspect Ratio woes..... !

    OK, so I have two clips imported into iMovieHD from my Canon 5DMKII, they are 1080p and 16x9 clips. I'm all for OAR (original aspect ratios) and enjoy "black bars" on the top and bottom, but its 16x9 and the monitor is not... so its adding them when