sap.com/tc~sec~ume~wd~umeadmin - WEBDYNPRO is not deployed on cluster eleme

[Former Member]

Any one has any idea how to fix this issue? I see the Weyb Dynpro Application is running fine, but it is complaning about not deployed correctly into cluster of the instance? How do I fix this issue?

Please advice. thanks in advance.

Kumar

#1.5 #0050569500A6006F0000001300000CAC0004A369F86E0EFC#1305575441513#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tc~wd~dispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#ksubrama#472##n/a##c53f70237ff511e0bb410000011dd66a#SAPEngine_Application_Thread[impl:3]_26##0#0#Error#1#/System/Server/WebRequests#Plain###application [webdynpro/dispatcher] Processing HTTP request to servlet [dispatcher] finished with error.
The error is: java.lang.NoSuchMethodError: com.sap.portal.activitydatacollector.ICollectorHook.isActive()Z
Exception id: [0050569500A6006F0000001100000CAC0004A369F86E0C0B]#
#IExternalStandardCheckInterface is class com.sap.tc.webdynpro.check.jcodest.wdp.InternalJCODestAvailabilityCheckInterface$External#
#1.5 #0050569500A600670000001000000CAC0004A36A6AD2C8D2#1305577360697#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#170##n/a##3f9dc6e07ffa11e0c5c80000011dd66a#SAPEngine_Application_Thread[impl:3]_28##0#0#Error#1#/System/Server#Java#deploy_5005##Application sap.com/webdynpro is not deployed on cluster element Server 0 0_87326 and it is not possible to get its status.#3#sap.com/webdynpro#Server 0 0_87326#get its status#
#1.5 #0050569500A600670000001100000CAC0004A36A6AD2FC80#1305577360711#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#170##n/a##3f9dc6e07ffa11e0c5c80000011dd66a#SAPEngine_Application_Thread[impl:3]_28##0#0#Error#1#/System/Audit#Java###Exception {0}#1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/webdynpro is not deployed on cluster element Server 0 0_87326 and it is not possible to get its status.
	at com.sap.engine.services.deploy.server.DeployServiceImpl.getStatus(DeployServiceImpl.java:3870)
	at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1353)
	at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1388)
	at com.sap.engine.services.deploy.server.DeployRuntimeControlImpl.getApplicationStatus(DeployRuntimeControlImpl.java:409)
	at sun.reflect.GeneratedMethodAccessor543.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:331)
	at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
	at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
	at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
	at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
	at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
	at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
	at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
	at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
	at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
	at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
	at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
	at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
	at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
	at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
	at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
	at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
	at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
	at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
	at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
	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 #0050569500A600670000001300000CAC0004A36A6AD35725#1305577360719#com.sap.engine.services.jmx.MBeanServerInvoker##com.sap.engine.services.jmx.MBeanServerInvoker#Administrator#170##n/a##3f9dc6e07ffa11e0c5c80000011dd66a#SAPEngine_Application_Thread[impl:3]_28##0#0#Warning#1#/System/Server#Java###Exception occurred while processing external JMX request [ JMX request (java) v1.0 len: 338 |  src: 2 target-node: 18732650 req: invoke params-number: 4 params-bytes: 0 | :name=deploy,j2eeType=SAP_J2EEServiceRuntimePerNode,SAP_J2EEClusterNode=18732650,SAP_J2EECluster="" getApplicationStatus [Ljava.lang.Object;@1414ae02 [Ljava.lang.String;@59ac0f9a ] 
[EXCEPTION]
 {0}#1#javax.management.MBeanException: Exception invoking method getApplicationStatus
	at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:80)
	at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
	at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
	at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
	at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
	at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
	at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
	at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
	at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
	at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
	at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
	at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
	at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
	at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
	at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
	at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
	at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
	at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
	at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
	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)
Caused by: java.rmi.RemoteException: Error in getting status of application webdynpro : Application sap.com/webdynpro is not deployed on cluster element Server 0 0_87326 and it is not possible to get its status.
	at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1371)
	at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1388)
	at com.sap.engine.services.deploy.server.DeployRuntimeControlImpl.getApplicationStatus(DeployRuntimeControlImpl.java:409)
	at sun.reflect.GeneratedMethodAccessor543.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:331)
	at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
	... 24 more
-------- caused by --------
java.rmi.RemoteException: Error in getting status of application webdynpro : Application sap.com/webdynpro is not deployed on cluster element Server 0 0_87326 and it is not possible to get its status.
	at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1371)
	at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1388)
	at com.sap.engine.services.deploy.server.DeployRuntimeControlImpl.getApplicationStatus(DeployRuntimeControlImpl.java:409)
	at sun.reflect.GeneratedMethodAccessor543.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:331)
	at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
	at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
	at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
	at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
	at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
	at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
	at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
	at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
	at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
	at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
	at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
	at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
	at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
	at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
	at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
	at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
	at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
	at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
	at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
	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 #0050569500A600690000000F00000CAC0004A36A6B0DFD6D#1305577364577#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#170##n/a##41edb2ee7ffa11e0c2cd0000011dd66a#SAPEngine_Application_Thread[impl:3]_36##0#0#Error#1#/System/Server#Java#deploy_5005##Application sap.com/tc~sec~ume~wd~umeadmin - WEBDYNPRO is not deployed on cluster element Server 0 0_87326 and it is not possible to get its status.#3#sap.com/tc~sec~ume~wd~umeadmin - WEBDYNPRO#Server 0 0_87326#get its status#
#1.5 #0050569500A600690000001000000CAC0004A36A6B0E22F8#1305577364587#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#170##n/a##41edb2ee7ffa11e0c2cd0000011dd66a#SAPEngine_Application_Thread[impl:3]_36##0#0#Error#1#/System/Audit#Java###Exception {0}#1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/tc~sec~ume~wd~umeadmin - WEBDYNPRO is not deployed on cluster element Server 0 0_87326 and it is not possible to get its status.
	at com.sap.engine.services.deploy.server.DeployServiceImpl.getStatus(DeployServiceImpl.java:3870)
	at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1353)
	at com.sap.engine.services.deploy.server.DeployServiceImpl.getApplicationStatus(DeployServiceImpl.java:1388)
	at com.sap.engine.services.deploy.server.DeployRuntimeControlImpl.getApplicationStatus(DeployRuntimeControlImpl.java:409)
	at sun.reflect.GeneratedMethodAccessor543.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:331)
	at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
	at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
	at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
	at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
	at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
	at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
	at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)

Edited by: Kumar Subramaniam on May 16, 2011 10:56 PM

[Former Member]

Answered

[Former Member]

Hi Kumar,

I assume that you are getting this error:

impl:3]_26##0#0#Error#1#/System/Server/WebRequests#Plain###application [webdynpro/dispatcher] Processing HTTP request to servlet [dispatcher] finished with error.

The error is: java.lang.NoSuchMethodError: com.sap.portal.activitydatacollector.ICollectorHook.isActive()Z Exception id: [0050569500A6006F0000001100000CAC0004A369F86E0C0B]#

#IExternalStandardCheckInterface is class com.sap.tc.webdynpro.check.jcodest.wdp.InternalJCODestAvailabilityCheckInterface$External

when you are trying to access some iView in the portal?

The most common issues with this is either when one of the JCO destinations is not configured correctly or that some file from the portal component EP-SERV package was not deployed

properly.

Could you please go to the NWA WebDynpro Content Administrator > Maintain JCO Destinations > and execute here "Test" for all your destinations, more importantly for the

ones that your application is using.

In addition, you may want to re-deply the EP-SERV package as well.

Best regards,

Shimon Zafrir

SAP AGS

[Former Member]

Well, non of Web Dynpro iViews are working. We ahve ESS/MSS Applications non of them are working. Even the user managemet tab is not working within the Potral. i.e. Non of the Web Dynpro iViews are working.

I get this error.

java.lang.NoSuchMethodError:

com.sap.portal.activitydatacollector.ICollectorHook.isActive()Z

Error Summary

While processing the current request, an exception occured which could

not be handled by the application or the framework.

If the information contained on this page doesn't help you to find and

correct the cause of the problem, please contact your system

administrator. To facilitate analysis of the problem, keep a copy of

this error page. Hint: Most browsers allow to select all content, copy

it and then paste it into an empty document (e.g. email or simple text

file).

Root Cause

The initial exception that caused the request to fail, was:

java.lang.NoSuchMethodError:

com.sap.portal.activitydatacollector.ICollectorHook.isActive()Z

at

com.sap.portal.activityreport.ActivityReportHookInterface.updateADCAfterInteraction(ActivityReportHookInterface.java:176)

at

com.sap.portal.activityreport.ActivityReportHookInterface.onAfterInteraction(ActivityReportHookInterface.java:145)

at

com.sap.portal.activityreport.wdp.InternalActivityReportHookInterface.onAfterInteraction(InternalActivityReportHookInterface.java:128)

at

com.sap.portal.activityreport.wdp.InternalActivityReportHookInterface$External.onAfterInteraction(InternalActivityReportHookInterface.java:167)

at com.sap.portal.pb.hook.PortalHooksManager.updateHooks

(PortalHooksManager.java:58)

... 34 more

[Former Member]

Hi,

If the User Management tab is also not working, there is some issue with the portal installation itself. Please get in touch with your basis. Make sure all the portal components have been applied to the server, and the deployment runs error-free. If necessary, ask them to re-apply the patches one by one- installing all the required dependant components.

Thanks

[p330068]

Hi Kumar,

Please check the webdynpro services and other services properly active / deployed in the Visual Administrator or not. if not then you need to deploy / activate in the VC.

For accessing the ESS/MSS webdynpro iview you need to check the SLD and JCO destination connections under content admin > webdynpro.

Best Regards

Arun Jaiswal

[Former Member]

issue resovled after deploying the patch version of the following compoents:

EPPSERV07P_19-10005915.SCA Patch 19 for PORTAL 7.01 SP 07

[Former Member]

Hi Kumar,

Correct, like I said in my first reply, you may want to re-deploy the EP-SERV package as well. Sorry I didn`t have

time to give more details as to which sp or patch level.

Regards,

Shimon