cancel
Showing results for 
Search instead for 
Did you mean: 

Exception while getting JCo connection Error while obtaining JCO connection

0 Kudos

Hi All,

We have installed EP7.0, which was working fine till yesterday.

I've loggedinto the portal as administrator content management > Webdynpro> Maintain JCo connections.

When I'm trying to test Jco connection it is giving below error message.

"Exception while getting JCo connection Error while obtaining JCO connection"

Because of the above issue we are not able to access ESS and MSS in portal.

Please help..

Regards

Naren!

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Dear Colleague

That error message "Issuer of SSO ticket is not authorized" usually appears, when the ticket is issued by a system with unknown certificate I would like you to first carry out the checks outlined in note 701205 that you may have not performed yet.

Also could you please check, whether the portal certificate is created with the RSA algorithm, if yes, please, recreate it, but using the DSA algorithm, re-import it into the R/3 store and the ACL and try the SSO configuration with the new certificate. even if the certificate is created with the DSA algorithm, re-import it in the R/3 system, and complete all the necessary steps, for the configuration.

Also take care that the system ID and client combination must be unique when tickets are to be accepted by an SAP Web AS ABAP system. Verify the client # that is imported into ACL.

Cheers

Answers (5)

Answers (5)

Former Member
0 Kudos

Hello,

Here's a couple of things I've had before that you might want to check.

When you test an SSO jco connection I think you need to ensure that the user you logon to the portal with has a corresponding user in the backend otherwise the test will fail.

It is also worth checking that you have not entered a validity date for the certificate beyond 2038 since it won't work if that is the case.

Regards

Garry

Former Member
0 Kudos

First include following parameters in the default profile sing RZ10,

login/create_sso2_ticket=2

login/accept_sso2_ticket=1

Export the portal certificate,

http://help.sap.com/saphelp_nw04/helpdata/en/e2/f71940d4558f5ce10000000a155106/content.htm

Then Import the portal certificate into the backend

http://help.sap.com/saphelp_nw04/helpdata/en/eb/1f1640033ae569e10000000a155106/content.htm

or

fix it by generating a new keystore from the portal, replace the original ticket keystore. then delete the old ticket from strustsso2 and reimport a freshly-downloaded verify.der from the portal.

Hope this helps you.

0 Kudos

Hi Mahi,

Thanks!

I've tried both the ways you have specified..

But still the same issue..

Regards

Naren

p330068
Active Contributor
0 Kudos

Hi Naren,

It looks like there is some problem with certificate issue either from portal or backend.

Please have a look the blog - [SSO Blog |http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/2370] [original link is broken] [original link is broken] [original link is broken]; and verify it accordingly.

Hope it will helps

Regards

Arun Jaiswal

former_member227283
Active Contributor
0 Kudos

Hi,

Can we know the process which you are following for SSO confirguaration.

Also, hope you are not using ip address for calling portal.

SSO only work when you call the hostname and not the ip address from URL.

Thanks

Anil

Former Member
0 Kudos

Hi Naren,

I need the log of defaultTrace not developer trace.

0 Kudos

Hi Mahi,

Sorry!!

Please find the defaulttrace

#1.#001125A6DBAF0074000000320015304A00048BF6C5E44714#1279791905129#com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails#sap.com/tcwddispwda#com.sap.t

c.webdynpro.tools.explorer.JCOConnectionsDetails#Administrator#15128##n/a##c5ebc740957511dfb334001125a6dbaf#SAPEngine_Application_Thread[impl:3]_21##0#0#Erro

r##Java###Issuer of SSO ticket is not authorized

[EXCEPTION]

#1#com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Issuer of SSO ticket is not authorized

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:516)

at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1086)

at com.sap.mw.jco.JCO$Client.connect(JCO.java:3256)

at com.sap.mw.jco.JCO$Pool.initPool(JCO.java:4726)

at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:6181)

at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:6136)

at com.sap.mw.jco.JCO.getClient(JCO.java:8804)

at com.sap.mw.jco.webas.WebDynproExtension.addClientPool(WebDynproExtension.java:133)

at com.sap.mw.jco.webas.WebDynproExtension.addClientPool(WebDynproExtension.java:74)

at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.createPool(AbstractJCOClientConnection.java:322)

at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.checkPoolEntry(AbstractJCOClientConnection.java:304)

at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.getClient(AbstractJCOClientConnection.java:443)

at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.onActionTestConnection(JCOConnectionsDetails.java:230)

at com.sap.tc.webdynpro.tools.explorer.wdp.InternalJCOConnectionsDetails.wdInvokeEventHandler(InternalJCOConnectionsDetails.java:303)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)

at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)

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:1039)

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(AccessController.java:215)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Former Member
0 Kudos

Hi Krishna,

reproduce the error and post the defaulttrace.log file.

Thanks,

Mahendra

0 Kudos

Hi Mahi,

I've re produced the error and below is the log from developer trace..

  • TIME Thu Jul 22 10:07:19 2010

[Thr 11825] * RELEASE 700

[Thr 11825] * COMPONENT CPIC (TCP/IP) with Unicode

[Thr 11825] * VERSION 3

[Thr 11825] * RC 473

[Thr 11825] * MODULE r3cpic_mt.c

[Thr 11825] * LINE 6117

[Thr 11825] * COUNTER 13

[Thr 11825] *

[Thr 11825] *****************************************************************************

[Thr 11825]

*****************************************************************************

*

[Thr 11825] * LOCATION CPIC (TCP/IP) on local host with Unicode

[Thr 11825] * ERROR illegal parameter value ( function=SAP_CMTIMEOUT2 /

  • parameter=conversation_ID / value=44884461 )

[Thr 11825] *

  • TIME Thu Jul 22 10:07:19 2010

[Thr 11825] * RELEASE 700

[Thr 11825] * COMPONENT CPIC (TCP/IP) with Unicode

[Thr 11825] * VERSION 3

[Thr 11825] * RC 769

[Thr 11825] * MODULE r3cpic_mt.c

[Thr 11825] * LINE 7333

[Thr 11825] * COUNTER 14

[Thr 11825] *

[Thr 11825] *****************************************************************************

[Thr 11825] ***LOG S98=> STISearchConv, no conv (44885539) [r3cpic_mt.c 6116]

[Thr 11825]

*****************************************************************************

*

[Thr 11825] * LOCATION CPIC (TCP/IP) on local host with Unicode

[Thr 11825] * ERROR no conversation found with id 44885539

[Thr 11825] *

  • TIME Thu Jul 22 10:07:19 2010

[Thr 11825] * RELEASE 700

[Thr 11825] * COMPONENT CPIC (TCP/IP) with Unicode

[Thr 11825] * VERSION 3

[Thr 11825] * RC 473

[Thr 11825] * MODULE r3cpic_mt.c

[Thr 11825] * LINE 6117

[Thr 11825] * COUNTER 15

[Thr 11825] *

[Thr 11825] *****************************************************************************

[Thr 11825]

*****************************************************************************

*

[Thr 11825] * LOCATION CPIC (TCP/IP) on local host with Unicode

[Thr 11825] * ERROR illegal parameter value ( function=SAP_CMTIMEOUT2 /

  • parameter=conversation_ID / value=44885539 )

[Thr 11825] *

Former Member
0 Kudos

Hi Naren,

Please check the SLD conection.

Regards,

Mahendra

0 Kudos

Hi Mahendra,

I've tested connectivity with SLD. connectivity is working fine..

Regards

Naren