Internal Server Error: no message found from ECC

[Former Member]

Hi All,

We had configured ESS, but i am facing an error in one of the screen like when i am going to

Personal information> Family members/dependents> EDIT--> click on review button. i am seeing the following error.

java.lang.NoClassDefFoundError: com/sap/tc/webdynpro/progmodel/repository/enums/WDMessageFormatEnumInfo

Can anyone please help me in this regard.

The complete error is as given below.

java.lang.NoClassDefFoundError: com/sap/tc/webdynpro/progmodel/repository/enums/WDMessageFormatEnumInfo

at com.sap.pcuigp.xssfpm.java.MessageManager.flushMessages(MessageManager.java:83)

at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoPostProcessing(FPMComponent.java:219)

at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoPostProcessing(InternalFPMComponent.java:128)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doPostProcessing(DelegatingComponent.java:119)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doPostProcessing(ClientComponent.java:627)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPostProcessing(WindowPhaseModel.java:621)

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

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

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:731)

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

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

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

at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)

at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:879)

at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)

at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1291)

at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:325)

at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:831)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)

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

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

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

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

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

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

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: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(Native Method)

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

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

All the best,

André Sousa

[Former Member]

Hi

Thank you so much for this reply...

I should have asked to before anyways better late than never...

One last question is our portal is in EP 7 SP09 can we put ESS,MSS and PCUI_GP as SP13??.

And out ECC 6 patch for EA_HR is SP15.

Please reply if you have any idea regarding this..

Sorry I could give u points for this ,as this is ur own theard..

Thanks once again

Sai Sharan

[Former Member]

There's no problem at all. SP in ECC it's completely different from the SP in EP.

Regards,

André Correia Sousa

[Former Member]

Hi

Thanks to both for the response.

Babu: How to check whether the package is deployed or not? i checked in system info tc/wd/webdynpro was there apart from this there was nothing available.

Andre: Can you please tell me like wht you have done apart from the patch level thing for the removal of this error. Our patch for ESS,MSS is 600 SP 10 and pcui_gp is 1.0 SP13.But when we checked in one server it was fine, though the error came only under certain cases but if all the details are filled the data used to get saved properly.

Please help me in this regards as it is very critical for me.

Regards,

Sai Sharan Kalla

[Former Member]

Hi,

"the error came only under certain cases but if all the details are filled the data used to get saved properly"

Exactly! This happens because you have different levels of SP for ESS,MSS and PCUI_GP. When the filled data is incorrectly the PCUI_GP is getting the error from ECC and then communicating it to ESS or MSS. If the SP level isn't coherent then you got that specific error.

That was the solution for my problem. I hope you get yours solved as well with this solution.

Regards,

André Correia Sousa

[Former Member]

Hi,

Did u resolve this. I am facing the same problem but dint get resolved, Can you please suggest wht i need to do for this error. is this something related to Patch level problem?

Regards,

Sai Sharan Kalla

[sanyev]

Hi Sai,

looks like one of the package is not deployed or have errors that is why you are getting class not found error. try deploying the package tc/webdynpro/progmodel.

Regards,

Sanyev

[Former Member]

Yes it was! You need to check if your SP levels for ESS, MSS and PCUI_GP are all in the same level.

Regards,

André Correia Sousa