Question Re: Error : "java.lang.NullPointerException" While Creating JCO connection in Technology Q&A

Error : "java.lang.NullPointerException" While Creating JCO connection

Former Member — Fri, 12 Mar 2010 05:51:10 GMT

Hello All,

Here I am facing a very strange issue in Portal Content Administration. I have Successfully deployed ESS/MSS on Portal. SLD and JCOs were working fine and my ESS application was also running successfully. Suddenly i start getting Error in ESS u201C com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: u2018passwordu2019 missing u201D.

Now when i tried to Test or Ping Jco connection from Portal Content Administration, It is green and successful. SLD is also successful but if I try to preview or create JCO connection, its throwing error "java.lang.NullPointerException".

I cross checked all the settings related to SLD ang JCOs.Everything is configured here still error is occurring.

Thanks & Regards

Nivedita

Re: Error : "java.lang.NullPointerException" While Creating JCO connection

Former Member — Fri, 12 Mar 2010 06:59:15 GMT

Hi Nivedita,

I think u have configured all jco connections with Ticket.

but u have to configure Jco connections , model data applications with ticket and meta data applications with user id and password .

For example

take 2 JCOs

1: SAP_R3_Financials -->for this use sso

2:SAP_R3_Financials_MetaData -->for this use userid/password .

Check this in ur system .

Regards,

Surekha .

Re: Error : "java.lang.NullPointerException" While Creating JCO connection

Former Member — Fri, 12 Mar 2010 07:19:42 GMT

Hi Nivedita,

Login into portal with administrator, go to Content Administration --> webdynpro. Choose the button Maintain JCo Destinations.

To ESS you use:

- Application Data:

SAP_R3_Travel

SAP_R3_Financials

SAP_R3_HumanResources

SAP_R3_SelfServiceGenerics

In this JCO Connections you choose Ticket (SSO)

- MetaData

SAP_R3_Travel_Metadata

SAP_R3_Financials_MetaData

SAP_R3_HumanResources_MetaData

SAP_R3_SelfServiceGenerics_MetaData

In this JCO Connections, Metadata JCO connections must use User / Password as Used Method.

Please check if you have followed the following steps in creating the metadata connection

1. Then create a metadata destination

2. Define J2EE cluster where you want your JCO to be assigned

3. Select Dictionary Meta data and click Next

4. Select your message server and logon group

5. In this screen the Used method would be disabled as Metadata would

always ask for a user and password.

After restart the portal.

Hope this helps.

Deep Nain Kundra

Re: Error : "java.lang.NullPointerException" While Creating JCO connection

Former Member — Fri, 12 Mar 2010 08:44:21 GMT

Hello Deep Sir,

All settings were done in the same manner as u said. In Metadata we mapped user/ password and in application data we mapped Ticket. But now suddenly errors are coming and I am not able to create or maintain the connection as when I click on the tabs, on screen it is throwing NullPointerException.So I am not able to see the screen even to set or preview the JCOs.

Thanks & Regards

Nivedita

Re: Error : "java.lang.NullPointerException" While Creating JCO connection

Former Member — Fri, 12 Mar 2010 08:55:43 GMT

Hi ,

first check detailed logmessage in default.trc . try to findout which jco test failed.

if jco with sso failed , check usermapping and backend user id credentials and authorizations.

if jco with rfc usid/pw failed - check rfc uid ,pwd information.

post detailed logfile to analyse the issue

Regards,

Koti Reddy

Re: Error : "java.lang.NullPointerException" While Creating JCO connection

Former Member — Fri, 12 Mar 2010 09:22:34 GMT

Has basis applied any patch recently? As you said thing were fine in the past.

Cheers,

Re: Error : "java.lang.NullPointerException" While Creating JCO connection

Former Member — Fri, 12 Mar 2010 09:41:44 GMT

No Anup. No Patch up gradations.

Regards

Nivedita

Re: Error : "java.lang.NullPointerException" While Creating JCO connection

Former Member — Fri, 12 Mar 2010 10:43:18 GMT

Dear Koti,

here is the log file.

#1.5 #001F29E34E4E006C00000138000015C80004819544C9725C#1268378010993#com.sap.tc.webdynpro.sessionmanagement#sap.com/tc_wddispwda#com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleThrowable#234500p#18262##n/a##c075c9502da611df9579001f29e34e4e#SAPEngine_Application_Thread[impl:3]_37##0#0#Error#1#/System/UserInterface#Java###Exception occured during processing of Web Dynpro application . The causing exception is nested.

[EXCEPTION]

#2#sap.com/tc_wdtools/Explorer#java.lang.NullPointerException

at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)

at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)

at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:285)

at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:251)

at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:158)

at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:236)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)

at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)

at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)

at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:881)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)

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

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(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)

#1.5 #001F29E34E4E006C00000139000015C80004819544C9860F#1268378011009#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tc_wddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#234500p#18262##n/a##c075c9502da611df9579001f29e34e4e#SAPEngine_Application_Thread[impl:3]_37##0#0#Error##Plain###application [webdynpro/dispatcher] Processing HTTP request to servlet [dispatcher] finished with error. The error is: java.lang.NullPointerException