on 04-21-2006 4:24 PM
Hi All,
I am trying to create a KM Scheduler Task. However while starting the task it gives me this error.
[code]Configuration Error: Failed to load task com.wyeth.clinicaltrials.jobs.PubstratFeed[/code]
This is the error that is shown on the component Monitor under System Administration->Monitring->Knowledege Management->Component Monitor.
If I click on the properties under this task it throws the following nullpointerexception
[code]java.lang.NullPointerException
at com.sapportals.wcm.service.scheduler.SchedulerEntry.getDescription(SchedulerEntry.java:357)
at com.sapportals.wcm.service.scheduler.crt.SchedulerEntryProxy.getDescription(SchedulerEntryProxy.java:102)
at com.sapportals.wcm.repository.manager.crt.CrtPropertyManager.getProperties(CrtPropertyManager.java:340)
at com.sapportals.wcm.repository.ResourceImpl.internalGetProperties(ResourceImpl.java:3620)
at com.sapportals.wcm.repository.ResourceImpl.getProperties(ResourceImpl.java:1209)
at com.sapportals.wcm.control.edit.PropertiesControl.initialize(PropertiesControl.java:1058)
at com.sapportals.wdf.stack.Control.initializeImpl(Control.java:449)
at com.sapportals.wdf.stack.Pane.initialize(Pane.java:510)
at com.sapportals.wdf.stack.PaneStack.initialize(PaneStack.java:509)
at com.sapportals.wdf.stack.Pane.initialize(Pane.java:504)
at com.sapportals.wdf.stack.PaneStack.initialize(PaneStack.java:509)
at com.sapportals.wdf.stack.Pane.initialize(Pane.java:504)
at com.sapportals.wdf.stack.PaneStack.initialize(PaneStack.java:509)
at com.sapportals.wdf.WdfCompositeController.doInitialization(WdfCompositeController.java:279)
at com.sapportals.wdf.WdfCompositeController.buildComposition(WdfCompositeController.java:659)
at com.sapportals.htmlb.AbstractCompositeComponent.preRender(AbstractCompositeComponent.java:33)
at com.sapportals.htmlb.Container.preRender(Container.java:120)
at com.sapportals.htmlb.Container.preRender(Container.java:120)
at com.sapportals.htmlb.Container.preRender(Container.java:120)
at com.sapportals.portal.htmlb.PrtContext.render(PrtContext.java:414)
at com.sapportals.htmlb.page.DynPage.doOutput(DynPage.java:237)
at com.sapportals.wcm.portal.component.base.KMControllerDynPage.doOutput(KMControllerDynPage.java:130)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:129)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
at com.sapportals.wcm.portal.component.base.ControllerComponent.doContent(ControllerComponent.java:73)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
at java.security.AccessController.doPrivileged(AccessController.java:204)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
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:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:180)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)[/code]
I am using the SP16 Developer studio to create the scheduler task. There is nothing in the scheduler task just a log message. Still this fails. Is this a bug or I am missing something here.
I would really appreciate any help in this regards.
Thanks
Ankur
The problem was solved when we used a SP14 specific version of the NWDS and re-build the complete scheduler. There were some extra files getting generated with an older NWDS and hence was causing this error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
just a guess - do you have your Description field filled in your CM configuration for task? From the trace it seems it could not read the property DESCRIPTION from the Cm configuration.
Just check it...
Romano
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, we have the same issue with SP14. Do you find a solution for that?
Thanks
Matthias
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
94 | |
11 | |
11 | |
10 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.