Instructot iview is not working in portal

Hi Experts,
We downloaded instructor business package into portal and when we click on it its saying
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 12:17_09/09/08_0023_8592250
Refer to the log file for details about this exception
plz help me in this waiting for u r responses
Regards,
Shilpa

Hi Pradeep,
here is the exception id and logs
#00505693764F00760000006800001288000456231D6C3D7D#1220608725041#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#kishore#326##n/a##3b53e9907b2e11dda43d00505693764f#SAPEngine_Application_Thread[impl:3]_35##0#0#Error##Java###03:28_05/09/08_0011_8592250
[EXCEPTION]
#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&<ProducerInfo>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_false PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System: &#39;SAP_LocalSystem&#39;,
Attribute: &#39;client&#39;.
 at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
 at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
 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:645)
 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:524)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
 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: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:102)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
#1.5 #00505693764F007C0000003B00001288000456231DD9E807#1220608732229#com.sapportals.wcm.repository.manager.cm.CmRepositoryManager#sap.com/irj#com.sapportals.wcm.repository.manager.cm.CmRepositoryManager.startUpImpl(341)#Guest#0##n/a##004a07307b2911dda8dc00505693764f#Thread[Thread-81,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Error occured while retrieving canonical name for folder 'http://atlsapepd.ananthtech.com:50000/irj/go/km/docs/documents' (java.io.IOException: The filename, directory name, or volume label syntax is incorrect)#
#1.5 #00505693764F007C0000003C0000128800045623216D4924#1220608792233#com.sapportals.wcm.repository.manager.cm.CmRepositoryManager#sap.com/irj#com.sapportals.wcm.repository.manager.cm.CmRepositoryManager.startUpImpl(341)#Guest#0##n/a##004a07307b2911dda8dc00505693764f#Thread[Thread-81,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Error occured while retrieving canonical name for folder 'http://atlsapepd.ananthtech.com:50000/irj/go/km/docs/documents' (java.io.IOException: The filename, directory name, or volume label syntax is incorrect)#
#1.5 #00505693764F006E0000009F0000128800045623245B3F67#1220608840658#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#3##n/a##7f137b217b3111dda92900505693764f#SAPEngine_Application_Thread[impl:3]_21##0#0#Error#1#/System/Server#Java#deploy_5005##Application sap.com/lms - web is not deployed on cluster element Server 0 0_85922 and it is not possible to get its status.#3#sap.com/lms - web#Server 0 0_85922#get its status#
#1.5 #00505693764F006E000000A00000128800045623245B46E3#1220608840658#com.sap.engine.services.deploy##com.sap.engine.services.deploy#Administrator#3##n/a##7f137b217b3111dda92900505693764f#SAPEngine_Application_Thread[impl:3]_21##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/lms - web is not deployed on cluster element Server 0 0_85922 and it is not possible to get its status.
 at com.sap.engine.services.deploy.server.DeployServiceImpl.getStatus(DeployServiceImpl.java:3866)
 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.GeneratedMethodAccessor55.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 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:319)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
 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:102)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
#1.5 #00505693764F006E000000A20000128800045623245B4C40#1220608840658#com.sap.engine.services.jmx.MBeanServerInvoker##com.sap.engine.services.jmx.MBeanServerInvoker#Administrator#3##n/a##7f137b217b3111dda92900505693764f#SAPEngine_Application_Thread[impl:3]_21##0#0#Warning#1#/System/Server#Java###Exception occurred while processing external JMX request [ JMX request (java) v1.0 len: 337 | src: 2 target-node: 8592250 req: invoke params-number: 4 params-bytes: 0 | :name=deploy,j2eeType=SAP_J2EEServiceRuntimePerNode,SAP_J2EEClusterNode=8592250,SAP_J2EECluster="" getApplicationStatus [Ljava.lang.Object;@40a8f463 [Ljava.lang.String;@1444b0bf ]
[EXCEPTION]
#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:319)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
 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:102)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: java.rmi.RemoteException: Error in getting status of application lms - web : Application sap.com/lms - web is not deployed on cluster element Server 0 0_85922 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.GeneratedMethodAccessor55.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
 ... 24 more
caused by -
java.rmi.RemoteException: Error in getting status of application lms - web : Application sap.com/lms - web is not deployed on cluster element Server 0 0_85922 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.GeneratedMethodAccessor55.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 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:319)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
 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:102)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Regards,
Shilpa

Similar Messages

Learning Solution: Instructor / Tutor iView(s) not working in Portal

Hi all . . .
We just installed the Instructor/Tutor package in our sandbox portal. I gave the role to myself so that I could see the Instruction and Tutoring tab. Yet, when I click on Work Overview to see the Instructor's Work Center iView, it throws a Portal Runtime Error. I have already reviewed the following:
Link: Instructot iview is not working in portal
This gave me some ideas, but no real help.
I have also reviewed
Link: http://help.sap.com/erp2005_ehp_03/helpdata/EN/44/5f713e28cf4688e10000000a11466f/content.htm
and ensured that I created the entry for the system required (connection tests ran successfully - with the exception of the ITS connection test - citing that port number not found in host name - but it's like this in Production so apparently it's not needed ) . . . and I assigned the SAP_ERP_TrainingManagement alias name to the system.
Here is the respective result in the defaultTrace file. Any ideas?
#1.5 #00145EC81CCC0046000001250016503800045BAA531ED439#1226687003939#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#44785#915##n/a##2f73d450b27911dd8ba700145ec81ccc#SAPEngine_Application_Thread[impl:3]_12##0#0#Error#1#/System/Server#Java###Exception ID:01:23_14/11/08_0002_8013050
[EXCEPTION]
{0}#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/com.sap.pct/specialist/com.sap.pct.erp.instructor.bp_folder/com.sap.pct.erp.instructor.roles/com.sap.pct.erp.instructor.instructor/com.sap.pct.erp.instructor.instructor/overview/com.sap.pct.erp.instructor.work_overview/com.sap.pct.erp.instructor.work_overview/com.sap.pct.erp.instructor.instructor_worklist
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : 44785
 at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
 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:645)
 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:524)
 at java.security.AccessController.doPrivileged(AccessController.java:246)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
 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: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:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 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:219)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&<ProducerInfo>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_false PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System: &#39;SAP_LocalSystem&#39;,
Attribute: &#39;client&#39;.
 at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
 at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
 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)
 ... 29 more
#1.5 #00145EC81CCC0046000001270016503800045BAA531F1371#1226687003955#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#44785#915##n/a##2f73d450b27911dd8ba700145ec81ccc#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Java###01:23_14/11/08_0002_8013050
[EXCEPTION]
{0}#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&<ProducerInfo>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_false PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System: &#39;SAP_LocalSystem&#39;,
Attribute: &#39;client&#39;.
 at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
 at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
 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:645)
 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:524)
 at java.security.AccessController.doPrivileged(AccessController.java:246)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
 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: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:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 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:219)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Hi Anagha,
I am integrating the ABAP Webdynpro into GP Process callable object. When I click on the task I am getting the following error.
Please help
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:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<ProducerInfo>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>&\#39;; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System: &\#39;SAP_LocalSystem&\#39;,
Attribute: &\#39;client&\#39;.
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
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)

WEBGUI is not working in portal

Hi
I had conected to production server and created Transactional Iview with SAPGUI for WINDOWS and running it successfully.
My aim is to make use of SAPGUI for HTML in the place of SAPGUI for WINDOWS.
So i had activated ITS services successfully and the URL is working fine.As i am using integrated ITS i checked with the fallowing URL.
http://server:port/sap/bc/gui/sap/its/webgui
It had shown the screen of SAP WEB Application Server with portal SID and asking for credentials. after proving the credentials its showing SAP screen successfully.
Now i had changed SAPGUI for HTML in transactional IVew and getting the same screen succesfully. as it ask for SAP user Id pwd. i had entered the same credentials wat i had entred earlier during the test. Now its showing an error like
Client, name, or password is not correct; log on again .
what could be the problem ?why its not working in portal while working fine with URL ?
Please guide me .

Hi
U Need to enable SAPGUi for html
goto se80 give internet services (in the drop down box)
Below drop down give SYSTEM publish these service by right clicking system publish--complete service.
and also publish same way WEBGUI
Check SAP Note 698329
Hope this helps you.
Regards
Krishna.

IF_FPM_WORK_PROTECTION is not working in portal

Dear Experts.
IF_FPM_WORK_PROTECTION is not working in portal . Which i have re-implemented in my Z-Wdp Component and in IS_DIRTY( ) method, following is the code which i have written.
ev_dirty = abap_true.
DATA lo_api_component TYPE REF TO if_wd_component.
DATA lo_portal_manager TYPE REF TO if_wd_portal_integration.
lo_api_component = wd_this->wd_get_api( ).
lo_portal_manager = lo_api_component->get_portal_manager( ).
CALL METHOD lo_portal_manager->set_work_protect_mode
EXPORTING
mode = if_wd_portal_integration=>co_wp_mode_application_only.
lo_portal_manager->set_application_dirty_flag( dirty_flag = ev_dirty ).
The scenario is : I have CANCEL button on my screen. And on click of that button,It is triggering go data loss popup.But on click of OK in that popup, It is giving the below message.
When i click on OK button, Instead of closing the appl'n is it giving the above error.
Thanks
KH

Hi KH,
IF_FPM_WORK_PROTECTION is not working in portal .
As per my knowledge, the method Is_Dirty( ) method just sets the EV_DIRTY flag and informs the portal about unsaved data on application.
Please refer the below help link
Work-Protect Mode - Floorplan Manager for Web Dynpro ABAP - SAP Library
I don't think we need to do any thing else at WD side.
Please consult portal team member to assist you in this case.
Settings for WorkProtect Mode (SAP Library - iViews)
Hope this helps you.
Regards,
Rama

Exit Plug not working in Portal

Hi experts,
I have a web dynpro application (WDP A) which fire an exit plug to another web dynpro application (WDP B). It works fine in normal web dynpro runtime. The architecture of the application is shown [here|http://img232.imageshack.us/img232/7172/exitplug.png].
Now i have created an iView in the EP for WDP A. When the button which fires the exit plug is clicked, i get this error.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
Seems exit plug is not working in portal run time. Any one has an idea on how to solve this?? Use portal navigation?? What is that?? any guideline and documentation on that??
Thanks in advance.
Best Regards,
kityein
Edited by: kityein lai on Aug 5, 2009 10:04 AM

Hi,
Now that your WD apps are running in a Portal they should be more "Portal aware".
What I mean is that now they are part of a larger framework and you cannot just call the other WD app.
To do this properly (as the error message says) you should use the portal navigation.
Portal navigation consists of many variants: Normal, Dynamic, Quicklinks etc etc.
I personally advice to use Quicklinks if you want to navigate between 2 applciations running in the portal but are not native-portal apps. Altough this might not fit your requrements in this scenario, I cannot say....
In addtions here are some help resources:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/38/5dc53e5ae84d3be10000000a11405a/frameset.htm
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/97/b0ef8b24a64ae884f0ab246e54cae5/frameset.htm
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/43/00c110606a5277e10000000a1553f7/frameset.htm
Hope this helps you a bit...
Benjamin Houttuin

SP 19 upgrade issue : Log off Button not working in Portal Masthead

Hi All,
We have recently performed an upgrade from EP 7.0 SP12 to EP 7.0 SP19 stack level.
After the upgrade we are facing these 2 issues:
1) Log off button is not working in Portal Masthead
2) SSO to BW reports also not working.
Any immediate pointers and help is highly appreciable.
Regards,
Shailesh

Hi Tobias,
Thanks for the reply.
I have tried rebuilding and redloying the par file after removing the function "'releaseProducerSessions()' " which is not available in SP 19..but still the issue persists.
Any other process to be followed?
2) SSO is working for other stuff, and the issue is specifically for Bex iViews/Reports
Regards,
Shailesh

BugsEye iView does not work in EP6.0 sp10

Hello,
We are using SRM and we also want to use BugsEey but the iView does not work. When i ask a preview i get the following error message.
Could not find portal application PDKSystem
Is there anybody who can help me to solve this
Thanks
Kurt

Hi Kurt,
did you change the URL in the BugsEye iView?
To do that, open the mySAP SRM: Content Management folder, right click the BugsEye ECM iView and choose Edit -> Object. In the Property Category drop down menue select Show all. Search for the Content Link property.
The default is something like http://<server>:<port>/DemoCat/servlet/BugsEyeSAP?cmd=login&...
Change this link to your URL (in my case it was something like http://reg/servlet/BugsExeSAP?cmd=login&...) If you don't know which link to use, call your SRM admin to give you the exact URL; after that you should control your link by calling it directly in the browser. If it works, change the URL in your iView.
Hope that helps,
Frank

Application not working on Portal

Hi,
I have a query regarding one of the application. The application is a transactional app like creating a new supplier/material.
When i execute the application from backend ECC, it is running fine but the same application is not working on Portal.
The application is working fine from NWBC as well. The problem is that the application navigation is not happening when i click on Create and throwing below errors. Please suggest at the earliest.
com.sap.portal.appintegrator.sap.Generic::Generic/ConnectionLayer
MandatoryParameters
OptionalParameters
                     SAP_LocalSystem                     DE1CLNT110                     DE1CLNT130                     DF1CLNT100                     DG1CLNT100                     SAP-GRC                     SAP-GRC-AC                     SAP_BI                     SAP_ECC                     SAP_ERP_Common                     SAP_FMDM                     SAP_GATEWAY                     SAP_GRC                     WebEx
Authentication
DebugMode
                     No                     Yes
                     GET                     POST
Regards,
Yuvraj

Hi Yuvraj,
Well, as it turns out.. we're at SP12 and this note does not apply for us. It's not really a solution for our system and we're still looking for the reason for this behavior of the portal.
On the other hand, you've opened this thread and you are the only one who can award points and mark certain solution as correct
Regards,
Boris

BW query not working in portal

Hello Experts,
We have this issue when we have a BW query which is running well in RSRT but the query is not working in Portal.
The error message we have is
User when running the report is getting the error message “Error in File SMT-0454 - Contribution Analysis (Cx) : Error in formula Running Total Condition Formula: 'HierarchyLevel (GroupingLevel ({YPAXXM01_YPAXXM01_QC001.[YGLSUBBRD GSK1CXBRNDCATH]-NodeId})) = 1' This field name is not known..”
Explored the possibilties , Could this be issue with BW query.
We have this query getting fed to BO's. Please advise.
Thanks,
Santhosh

Hi Santhosh,
Error... This field name is not known, check your formulas in query, there might be some changes happenened with the characteristics used in formula.
Check the formula by going up to base level, you might removed some field ex: YGLSUBBRD from your query. Repair it appropriately.
Hope helps - Kumar

Business Planning is not working in Portal BI iviews

it give me error of JCO . SLD is fine, and JCO is configured but it still does not work. help me please

Hi,
Please refer to this link : http://help.sap.com/saphelp_nw04s/helpdata/en/fa/c1194276e0de2ce10000000a1550b0/frameset.htm. This documentation provides all the information you need to configure and run business planning on Portal.
Just refer to the section Tasks -> Business Planning Scenario Variant. It refers to the JCo Connections and other configurations you would need to maintain.
Hope this helps.
Cheers,
Sunil
PS: Reward points for helpful answers.

SWF file is not working in Portal PROD System

Hi All,
We have written custom mxml script in Adobe Flex 3 which displays the list of applications stored in the DB. Then we have posted that .swf file into our Portal KM and then we have created one URL iView with the location from KM.
These days we are facing issue like the output of the script is not working means the applications are not listed on the portal prod system.
Whenever the issue arieses we are requested to upload the file once again into KM and it works after the upload been done.
We are not sure what could be the reason for this issue and I request any one to assist us to resolve this issue.
Please let me know if you need more info on this issue.
Thanks in advance.
Best Regards,
Vijaykumar K.

Hi Vijay,
I belive this should be a portal issue, anyways let me give it a try.
I never worked on flex in SAP but did similar stuff in portal content development.
Do you have any traces in that development..?
Did you check any messages being loged in portal...?
Check if there is any issue with the file like couldn't recognise a resource from KM which is required etc.
Cheers,
Sai

Bex Query is not working in portal

Dear Experts,
i have uploaded BI master role into portal, By default Bex Queries are assgined to Master Role. when I clcik on preview for particular Bex Query, it's working fine. but after assigning the master role to end user, that same Bex Query is not working. it's showing Below error..
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 05:22_18/08/10_0002_7116150
Refer to the log file for details about this exception.
please give me suggetions...
Regards,
VENU

Hi Venu ,
Can you please check the logs for details - http(s):<host>:<port>/nwa . This may be a permissions issue . Check if the iview has read permission for everyone group and then test . Also post the error details here .
Regards
Mayank

Check Button Not Working on Portal for BI report

We have Vendor account group variable when I enter any random value and click on check its not working its not giving message as ' Invalid Input' on Portal ( Variable is single input optional variable) same Check Button Working in RSRT .
And For all other Infoobjects ( Plant , Profit center) check Buitton is working on Port as well in RSRT.
Please suggest.

done

Validation-code of a view is not working in portal

my validation code is working fine when testing in local view's application. the same view is attached to portal through fpm. while testing the same view in srm portal it is not working.can anybody suggest me why it is happening so. i will be thankful.

have you checked in debugging.....

Search is not working in Portal??

Hi all
This is the error i got i tried to search in portal:
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
iView not found: pcd:portal_content/every_user/general/eu_role/com.sap.km.home_ws/com.sap.km.hidden/com.sap.km.urlaccess/com.sap.km.basicsearch.
Exception id: 06:10_05/12/05_0017_8166050
See the details for the exception ID in the log file
But I can see this under
Portal Content->Portal Users->Standard Portal Users->Default Framework Page there is Tool Area iView. Here I can see "KM Search Component" which contains default entry "pcd:portal_content/every_user/general/eu_role/com.sap.km.home_ws/
com.sap.km.hidden/com.sap.km.urlaccess/com.sap.km.basicsearch".In Portal Content->Portal Users->Standard Portal Users -> Standard User Role. The iView KM Basic Search iView is not visible and also under Home the entries Hidden->URL Access is missing.
What else to be done?
Help me
Regards,
Ganesh

Hi Ganesh,
Is the problem solved?
If yes, please do let me know as to how did you resolve this?
If no, did you try re-installing the TREX Engine engine?
Awaiting Reply.
Warm Regards,
Ritu

Instructot iview is not working in portal

Similar Messages

Maybe you are looking for