Portal Runtime Error connecting MDM (Employee repository)

Hi
I'm having difficulty getting our MDM repository (Employee). I keep getting a portal exception when trying to view the repository using iView.
I am able to connect to MDM Customers. I call Result Set of customers using an iView. I tried doing same for Employees, but it is not working and throwing an exception.
The following exception is logged:
Exception ID:12:07_06/06/07_0086_17794650
[EXCEPTION]
com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/com.sap.pct/specialist/com.sap.pct.mdm.appl.mdm_550/com.sap.pct.mdm.appl.templates/com.sap.pct.mdm.appl.templates.iviews/com.sap.pct.mdm.appl.result_set_editor
Component class : com.sap.pct.mdm.tech.editors.ResultSetEditor
User : Administrator
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
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: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:522)
at java.security.AccessController.doPrivileged(Native Method)
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(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)
Caused by: java.lang.NullPointerException
at com.sapportals.htmlb.Container.addComponent(Container.java:49)
at com.sapportals.admin.wizardframework.components.Group.getGroup(Group.java:39)
at com.sapportals.admin.wizardframework.components.Group.getDisplay(Group.java:45)
at com.sap.portal.admin.editor.ui.EditorGroup.getDisplay(EditorGroup.java:46)
at com.sapportals.admin.wizardframework.components.GridContainer.getGrid(GridContainer.java:182)
at com.sapportals.admin.wizardframework.components.GridContainer.getDisplay(GridContainer.java:210)
at com.sap.portal.admin.editor.ui.PELayout.doLayout(PELayout.java:145)
at com.sap.portal.admin.editor.pane.OutPane.doBeforeDisplay(OutPane.java:96)
at com.sap.portal.admin.editor.pane.EditorPaneWrapper.myDoBeforeDisplay(EditorPaneWrapper.java:95)
at com.sapportals.admin.wizardframework.components.FlowContainer.doBeforeDisplay(FlowContainer.java:124)
at com.sapportals.admin.wizardframework.core.WizardInstance.doPre(WizardInstance.java:305)
at com.sapportals.admin.wizardframework.core.WizardInstance.doWizard(WizardInstance.java:242)
at com.sap.portal.admin.editor.Editor.doWizard(Editor.java:605)
at com.sap.portal.admin.editor.Editor.run(Editor.java:150)
at com.sap.portal.admin.editor.AbstractEditorComponent.doContent(AbstractEditorComponent.java:59)
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

Hi
I am getting the same error. Please let know if you were able to resolve this error?
Regards
Aruna

Similar Messages

Portal runtime error in MSS / employee review --- all the links

Hi
I got an portal runtime error
Here is the error that I am getting.
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/WEB_GROUP.cra.ca.WEB_GROUP/roles/cra.mss.MSS/cra.mss.MSS/cra.mss.EmployeeReview/cra.mss.GeneralData/com.sap.pct.hcm.teamviewer_1
Component Name : com.sap.pct.hcm.teamviewer.default
The exception was logged. Inform your system administrator..
Exception id: 07:47_02/02/07_0031
See the details for the exception ID in the log file

Hi,
You need to locate the defaulttrace. Check out this help file:
http://help.sap.com/saphelp_nw04/helpdata/en/a0/58db515b95b64181ef0552dc1f5c50/frameset.htm
If you open the trace file, you can search for the exception id as mentioned in your 1st post.
cheers,
Noë

Pop ups on Standard MDM Portal iViews throw Portal Runtime Error

Hi all,
We are facing some issues with MDM Standard Search iViews in Portal. We have configured MDM standard iViews using MDM Search Texts iView, MDM Result Set iView, MDM Search Picklists iView, MDM Item Details etc. We are facing a problem with the MDM Search Picklists iViews wherein we have to click the ellipses button to open the pop up. Whenever we open the pop up, the pop up shows Portal Runtime Error. Please find the screenshot below:
http://img209.imageshack.us/img209/1138/portalruntimeerror.jpg
The MDM System is working fine. The other Standard iViews are also working fine. The surprising thing is that, when the Super Admin role is assigned to the user, the iViews start working perfectly as shown below:
http://img696.imageshack.us/img696/6808/worksfinethisway.jpg
I have checked the permissions also on all these iViews as well as the System object and did not find any problem. Moreoever, this was working fine till some days back. All of a sudden these iViews have stopped working. Please guide me as to what can be the reason for this and any possible solutions.
Thanks in advance.
Regards,
Ankur

I would check the logs but it sounds like a permission error to me. Can you or your basis resources modify the Security Zones?
System Administration -> Permissions -> expand Security Zones folder -> right click on com.sap.pct.mdm.appl.masteriviews and select Open Permissions -> in the assign permissions section add read permissions for a particular user, role, or group which the user getting the error is part of, check the End User checkbox -> Save. Login to the portal and try again.
-Greg

Portal runtime error in Purchasing in ESS

Hello,
After logging in to the portal, when I go to Employee Self-Services -> Purchasing, which ever option (Shop, Confirm Goods / Services, Check Status) I click, I get a portal runtime error as shown below:
#1.5 #005056803084006B00000039000000FC0004638903CCAF24#1235340032299#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#smagan#23907##KSCEPD.esr.cri.nz_EPD_3051250#smagan#f667c1b0012b11deb880005056803084#SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#/System/Server#Java###Exception ID:11:00_23/02/09_0004_3051250
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess.roles/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.area_purchasing/com.sap.pct.erp.ess.purchasing_services/com.sap.pct.erp.ess.purchasing_service
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : smagan
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(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: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(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)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;<System.Access.ITS.protocol>://<System.Access.ITS.hostname>/sap<ESID>/bc/gui/sap/its/<IAC[SAP_ITS_NAMESPACE]>?sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&DisconnectOnClose=0&DesignBaseUrl=<LAF.BaseUrl[url_ENCODE]>&~design=<LAF.Theme[url_ENCODE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>&\#39;; the problem occured at position 121. 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
Working Time, Timesheet, Personal Information, Pay Statement works perfectly. The error happens only in the case of Purchasing. I am new to ESS, so any help in this regard would be highly appreciated.
Thanks,
Ajay

Hi Bala,
It is happening for all users. I checked the authorizations in the backend. The roles assigned to the user has the following authorizations: S_RFC, S_SERVICE, S_TCODE, S_DATASET, S_TABU_DIS, S_WF_WI, P_TRAVL, PLOG, P_ABAP, P_ORGIN, P_ORGINCON, P_ORGXXCON, P_PCLX, P_PERNR, P_TCODE, M_BANF_BSA, M_BANF_EKG, M_BANF_EKO, M_BANF_WRK, M_BEST_BSA, M_BEST_EKG, M_BEST_EKO, M_BEST_WRK.
In portal the user is assigned the ESS and Standard portal user role.
The transaction ST22 shows the following:
 The user "TESTUSER9" has no RFC authorization for the function group
 "SDIFRUNTIME". Please contact your system administrator to give you
 the RFC authorization for the required function groups (such as "SDIFRUNTIME").
 The RFC authorization object is S_RFC.
Thanks,
Ajay

KM iviews, KM Content, Index Administration showed Portal Runtime error

Hi Experts,
We recently tried migrating our BI production portal to new hardware. The Portal version was not changed just it was migrated from one server to another. After migration the portal restarted properly but the KM iviews, KM Content and Index Administration showed "Portal Runtime Error".
We restarted the portal several times but still the same. Also the KM services were running.
We had migrated the BI development portal in similar manner couple of months back but it did not showed any such error. It was successful in first attempt.
Can anyone please suggest what must have gone wrong and how can this be corrected? Is there any monitoring or tracing tool we can use to check this. Please suggest.
Thanks & Regards,
Seema Rane.

Hi Ricardo , Lorcan,
Thank you for the prompt reply. Following is the default trace I found on the server:
Caused by: com.sap.engine.services.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception while starting: sap.com/com.sap.netweaver.coll.appl.room', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception while starting: sap.com/com.sap.netweaver.coll.appl.room
 at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.prepareStart(PortalRuntimeContainer.java:527)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4367)
 at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:589)
 ... 46 more
Caused by: com.sap.engine.services.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception while starting: SAPJ2EE::sap.com/xappscprxrpmui~collroomint', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception while starting: SAPJ2EE::sap.com/xappscprxrpmui~collroomint
 at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getAndStartSAPJ2EEApplicationItem(SAPJ2EEPortalRuntime.java:888)
 at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.prepareStart(PortalRuntimeContainer.java:511)
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [ExternalApplicationItem.prepare]: SAPJ2EE::sap.com/xappscprxrpmui~collroomint
 at com.sapportals.portal.prt.core.broker.ExternalApplicationItem.prepare(ExternalApplicationItem.java:188)
 at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:232)
 at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.start(SAPJ2EEApplicationItem.java:192)
 at com.sapportals.portal.prt.service.sapj2ee.Mediator.getAndStartExternalApplication(Mediator.java:132)
 at com.sap.portal.prt.sapj2ee.StartPortalApplication.coreRun(StartPortalApplication.java:59)
 at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getAndStartSAPJ2EEApplicationItem(SAPJ2EEPortalRuntime.java:884)
 ... 49 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.netweaver.coll.appl.room
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
 at com.sapportals.portal.prt.core.broker.ExternalApplicationItem.prepare(ExternalApplicationItem.java:180)
 ... 54 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.netweaver.coll.appl.base
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
 ... 55 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.netweaver.kmc.people
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
 ... 56 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.km.application
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
 ... 57 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.km.cm.main
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
 ... 58 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.km.cm.repository.filter
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
 ... 59 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.km.cm.service.base
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
 ... 60 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.km.cm.protocols.ice
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
 ... 61 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.km.cm.protocols.webdav
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
 ... 62 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.netweaver.bc.rf.service
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
 ... 63 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during start of application: SAPJ2EE::library:signature_lib
 at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:323)
 at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
 ... 64 more
Caused by: com.sapportals.portal.prt.core.broker.SAPJ2EELibraryNotFoundException: Could not find Library SAPJ2EE::library:signature_lib
 at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:277)
I guess the KM applications are not being found. How do I correct this? Our KM repository is connected to BI and has got lot of BI content in it.
Will redeploying the com.sap.km.applications.par file help?
Please provide some solution so that this error will be resolved without effecting the KM Content.
Thanks & Regards,
Seema Rane

Two iView(out of three) give Portal runtime error when refresh MSS-UWL Page

Hi All,
i am getting the Portal runtime exception in the MSS->Work Overview ->2nd and 3rd iView on this page.
First iView is the UWL-Task 2)Attendance Overview and 3) Work Orders
When i refresh this page "refresh" from pae level refresh. i am getting the below error on 2nd and 3rd iView. Last 2 iView is not displaying.
Portal Runtime Error
An exception occurred while processing your request
Exception id: 02:02_12/01/09_0039_38688450
See the details for the exception ID in the log file.
i have tryed to search the log also in the default trace but can not find any log with this exception ID.
Please suggest me on this ?
thanks in advance!
Narpal S Sihag

Hello,
I have also a problem like this (error 09_0006_808022650)
Can you describe your scenario ?
My scenario is
- Portal MDM connection OK and working tasks in MDM
- new UWL System (connector type : MdmUwlConnector)
- new config file (XML)
- dedicated Role and dedicated iView (copy of standard UWL iView)
- clearing cache
Test : No working Tasks in UWL
- restarting portail application com.sap.netweaver.bc.uwl
Test : No working Tasks in UWL
- running wizard (System Admin, system config, UWL customize IView)
- new field "TEST" to iView
- portail create the com.sap.pct.erp.mss.001
Test : No working Tasks in UWL
Test : standard UWL crashes with error 09_0006_808022650
After what, we try roolback, removing XML config, connection, dedicated iView, ...
Still crashing with error 09_0006_808022650
Now our developpemnt system don't work for UWL ... (using UWL with ECC connection and was OK for ECC)
Questions : is your scenario similar to this one ? Is anyone can help us ?
My best thanks
Vincent

Portal runtime error under travel/ESS/MSS

Dear all,
When we see privew under Employee self service --> ERP 2005 EhP2 --> iviews -->travel and expenses --> create travel request
Here I'm getting
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 02:19_26/02/11_0006_39627050
Refer to the log file for details about this exception.
But it is working fine under Employee self service --> iviews -->travel and expenses --> create travel request.
What could be reason, any body reply me.
I appreciate if any one can share the resolution
Regards,
Mahee.

Hi,
I have checked the following thread,
Travel Management--Webdynpro ABAP Services
I Have added system alias. now I'm getting different error,
Internet Explorer cannot display the webpage
What you can try:
Diagnose Connection Problems
More information
This problem can be caused by a variety of issues, including:
Internet connectivity has been lost.
The website is temporarily unavailable.
The Domain Name Server (DNS) is not reachable.
The Domain Name Server (DNS) does not have a listing for the website's domain.
There might be a typing error in the address.
If this is an HTTPS (secure) address, click Tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section.
For offline users
You can still view subscribed feeds and some recently viewed webpages.
To view subscribed feeds
Click the Favorites Center button , click Feeds, and then click the feed you want to view.
To view recently visited webpages (might not work on all pages)
Click Tools , and then click Work Offline.
Click the Favorites Center button , click History, and then click the page you want to view.
Awaiting for your valuable response.
thanks in advance.
Regards,
Mahee.

Portal Runtime Error while accessing BW reports through portal

Hi,
We are facing portal runtime error(An exception occurred while processing your request. Please send the exception id to your portal administrator) while accessing BI reports through portal frequently.
We are unable to trace the error in the 'default trace' log file and although refreshing the cache solves this issue, it is difficult to explain this to every user individually.
After many such errors, We found one log entry, which we are now not yet sure if it is relevant. The error states:
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><BWLauncherComponent[PORTAL_URL]>;jsessionid=<Request.JSessionID>?sap-ext-sid=<ID[url_ENCODE]>&Language=<Request.Language>&theme=<LAF.Theme[url_ENCODE]>&sap-lafversions=<LAF.AllVersions[url_ENCODE]>&<Authentication>&<Report>&<BusinessParameters>'; the problem occured at position 230. Cannot process expression <LAF.AllVersions>
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
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:540)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:423)
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)
Content pass of Application Integrator failed.
Component Name: 'com.sap.portal.appintegrator.sap.BWReport',
Context Name (iView): <iview name location>
Top Layer: 'BWReport/TopLayer',
Producer ID (FPN): 'null',
System Alias: 'Sap_bw',
2.
The cluster server element 111111 is not added in the EP cluster context,
 because prtbridge on 111111 is stopped or not yet started (maybe the server is starting or shuting down).
Please suggest us if the above logs are related to the issue or not
Kindly provide us any inputs or solutions.

Hi All,
We are also having similiar type of error in our portal.
com.sap.engine.services.prtbridge##com.sap.engine.services.prtbridge
#######SAPEngine_System_Thread[impl:5]_13##0#0#Error#1#/System/Server#Plain###
The cluster server element 125898350 is not added in the EP cluster context,
 because prtbridge on 125898350 is stopped or not yet started
(maybe the server is starting or shuting down).
We have implemented the FPN using RRA.
This error comes only for few users when they navigate in Portal. After clearing the cache, it works for all. Kindly help us to resolve this issue.
Regards,
Venkatesh

Portal Runtime Error when creating a new iView

Hi, all.
Our env is like the following.
EP 2004s(7.0) SPS07
From the Content Administration, when we try to create new iView, we
sometimes(these days frequently!) got the following error.
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
The exception was logged. Inform your system administrator..
Exception id: 09:51_16/05/06_0062_9690550
See the details for the exception ID in the log file
And the detail in the defaultTrace.trc says like the following.
Exception ID:09:51_16/05/06_0062_9690550
[EXCEPTION]
com.sapportals.portal.prt.runtime.PortalRuntimeException: PortalRuntimeException
     at com.sapportals.portal.prt.core.PortalRequestManager.handleRequestException(PortalRequestManager.java:921)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:803)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
     at java.security.AccessController.doPrivileged(Native Method)
     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.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:316)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:372)
     at com.sapportals.appdesigner.appdesignerfw.TabContentComponent.doOnNodeReady(TabContentComponent.java:110)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
     at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
     at java.security.AccessController.doPrivileged(Native Method)
     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)
Does anyone have any idea or advice?
Best Regards.

Sejoon,
Does this happen for only specific users? Or is it global and apparent for all users?
Regards,
James

Portal Runtime Error in ESS iview

Hi All,
I have implemented ESS 50.4 on EP 6.0 SP9. For SAP IAC iviws i am getting following error.
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/AFDB/Role/ESSRole/Office/SAPInbox/SAPInbox
Component Name : com.sap.portal.appintegrator.sap.IAC
Error in executing a process for compilation.
Exception id: 03:10_06/05/06_0031_4156850
See the details for the exception ID in the log file.
In the log file i am getting following error message.
com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "SAPEPPDB" is stopped or not started, 2) Connector service is stopped or has not been started.
Please help me to resolve the problem its very urgent.
Regards,
Vaishali

Hi Vaishali,
Nice to hear from you again.
Hope you are doing good.
I am not sure whether the error that you mentioned is the right one for this issue, but if this is the case, just to inform you that a new note has been released in this regard. Please check sap note: 1600085 as well and set the parameters accordingly.
Usually we need to see what kind of code is using the concerned connection.
Incase the issue persists, proceed as follows (it wil be better to do this when the value of the number of connections is really high, so that identifying the root cause can be easy.
1)
Set the severity of "com.sap.engine.services.connector.jca.ConnectionHashSet" to DEBUG.
You can change the severity of a location using the guide in the link below:
http://help.sap.com/saphelp_nwce72/helpdata/en/47/af551efa711503e10000000a42189c/frameset.htm
2)
- connect to the AS-JAVA via telnet
- then execute these commands:
> add connector
> switch_debug_mode SAPEPPDB (or the datasource name)
> jump (to go to the next servernode if you have multiple ones)
> add connector
> switch_debug_mode SAPEPPDB
... and so on on all the servernodes
- then wait for a few hours in order to see the connections not being
released
- go back to the telnet console and call:
> list_conn SAPEPPDB -showTrace > server0.txt
> jump
> list_conn SAPEPPDB -showTrace > server1.txt
... and so on on all the servernodes
The serverX.txt files will be generated in the ../j2ee/cluster/server directories. Just check them to get more info.
Thank you!
Kind Regards,
Hemanth
SAP AGS

Portal Runtime Error while clicking on value selector

Hi,
I am facing problem while clicking on value selector on Picklist search iview and also any lookup table value selector.
If I assign the same role to my portal user(Admin rights) working fine...but if I assign it to end users...not accessible on popup and giving portal runtime error.
Currently i have assigned standard "eu_role" to the end users...Do I need to give any special permissions to some of end users?
Appreciate all your help in this regard.
Thanks,
Pooja

System Administration > Permission > Security Zones >
com.sap.pct.mdm.appl.masterviews > high_safety >
com.sap.pct.mdm.appl.masterviews > low_safety >
com.sap.pct.mdm.tech.systems > high_safety
com.sap.pct.mdm.tech.wizards > high_safety
give Read / Write and End User access to the custom role/standard role that has to access MDM Views.
Regards,
Nitin

Portal Runtime error in assigning a role to a user by UME

Hi ALL,
I am assigning a role to a user through UME using this piece of code:
String uids = userFactory.getUserByUniqueName("Shilpa").getUniqueID();
String roleid = roleFact.getRoleByUniqueName("pcd:portal_content/administrator/content_admin/content_admin_role").getUniqueID();
roleFact.addUserToRole(uids,roleid);
The userid and role is beinf fetched successfully but at the assignment of the role to the user , I am gettign Portal runtime error.
The error log is following.
 java.lang.NoClassDefFoundError: com/sap/abc/network/util/InfEPLog
 at UserListeners.userAssigned(UserListeners.java:27)
 at com.sap.security.core.imp.RoleFactory.assignUserPerformed(RoleFactory.java:1466)
 at com.sap.security.core.persistence.imp.DistributedTransaction.doCacheUpdateAndNotificationForMembers(DistributedTransaction.java:565)
 at com.sap.security.core.persistence.imp.DistributedTransaction.doCacheUpdateAndNotificationForMembers(DistributedTransaction.java:815)
 at com.sap.security.core.persistence.imp.DistributedTransaction.doCacheUpdateAndNotification(DistributedTransaction.java:465)
 at com.sap.security.core.persistence.imp.DistributedTransaction.afterCompletion(DistributedTransaction.java:252)
 at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:414)
 at com.sap.engine.services.ts.jta.impl.TransactionManagerImpl.commit(TransactionManagerImpl.java:316)
 at com.sap.engine.services.ts.transaction.TxManager.commitLevel(TxManager.java:581)
 at com.sap.engine.services.ts.transaction.TxManagerImpl.commitLevel(TxManagerImpl.java:63)
 at com.sap.transaction.TxManager.commitLevel(TxManager.java:237)
 at com.sap.security.core.persistence.imp.DistributedTransaction.commit(DistributedTransaction.java:2742)
 at com.sap.security.core.imp.Role.commit(Role.java:337)
 at com.sap.security.core.imp.RoleFactory.addUserToRole(RoleFactory.java:1338)
 at com.sap.user.UserAdded.doContent(UserAdded.java:63)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.doPreview(AbstractPortalComponent.java:240)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:168)
 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)
Please tell me where I am wrong.
Regards,
Shilpa.

Hi Shilpa,
The error "java.lang.NoClassDefFoundError" means that your classpath is not set correctly. This is likely due to a missing reference. The class file may be in the jar, but at runtime the component (your component) needs to have access to the jar file which contains the class.
Try adding the servlet.jar, activation.jar file in your project and also through your ADd external libraries at 'java build path'. also please ensure tht WAS and NWDS at the same SP level.
Hope this might help you.
Regards,
Shaila

Portal runtime error while accessing BI Report as URL iView

Hi All,
I created an URL Iview with the URL of BI report, when i am trying to access it then getting portal runtime error.
I had check the log it is showing the following details about the error, could you please help me out what is the root cause based on the log details...??
Thanks in advance.
Logfile Details
1) 08:48_14/09/10_0049_139354050*
*[EXCEPTION]*
*com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.ConnectionString>'; the problem occured at position 0. Cannot process expression <System.ConnectionString> because Invalid System Attribute:*
*System: &#39;SAP_LocalSystem&#39;,*
*Attribute: &#39;ConnectionString&#39;.*
*at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)*
*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:235)*
*at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)*
*at java.security.AccessController.doPrivileged(AccessController.java:246)*
*at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)*
*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(AccessController.java:219)*
*at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)*
*at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
2) Full Message Text*
*Content pass of Application Integrator failed.*
*Component Name: 'com.sap.portal.appintegrator.sap.Transaction',*
*Context Name (iView): 'pcd:portal_content/net.ea.epson.BI_ROLES/com.epson.financeuser/ZB(3a)FINANCE_USER/com.Epson.UnitandGrossProfit',*
*Top Layer: 'Transaction/DragAndRelateLayer',*
*Producer ID (FPN): 'null',*
*System Alias: 'BIDCLNT100',
Thanks,
Kalki Reddy.

Hi Avadh,
Thanks for your reply.
I tested thru connection test of the system , it was tested successflly without any issues. all are into tick mark only.
but when i am trying to use the system alias name while creating Trasaction iview also i am not able to get the system alias name in the dropdown for selecting the system alias.
but system alias what ever it is "BIDCLNT100" is in active and connection test is done correctly without any issues.
Please let me know the problem why i am not able to get the same system alias name "BIDCLNT100" not able to get in the drop down list while creating the transaction IView??
Please reply , Thanks in advance
Thanks,
Kalki Reddy

Portal Runtime Error: Unable to parse template

Hi!
I integrated SAP BW system with SAP Portal. All the connection tests (Sap Web AS connection, ITS connection, Connection Test for connectors) run successfully.
I also installed a BI add on u201CBI Administratoru201D on Portal and performed all the steps on SAP BI system.
When I try to access one of the functions of BI Administrator I get Portal Runtime Exception on all the windows in Portal (bellow, in the middle, etc.).
BI System Selection
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 12:26_20/01/09_0013_21754250
Refer to the log file for details about this exception.
I have looked into log file for Portal and detected the following error text:
#1#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/bw/BEx?sap-client=<System.client>&sap-language=<Request.Language>&accessibility=<User.Accessibility
[SAP_BOOL]>&style_sheet=<LAF.StylesheetUrl[url_ENCODE]>&<TrayInformation[IF_true PROCESS_RECURSIVE]>&<Authentication>&<Report>&<BusinessParameters>&\#39;; the problem occured at position 82. Cannot process expression <System.client> because Invalid System Attribute:
System: &\#39;SAP_LocalSystem&\#39;,
Attribute: &\#39;client&\#39;.
Question:
How can I correct this error?
Any helpful information will be very appreciated!
Axel

Hi Alex,
It seems that the iview (of the type Application intergrator) cannot read or interperet the "client" parameter from your system object.
I can also see that the systemobject-alias that is reffered to is "SAP_LocalSystem".
Find the System Object called SAP_BW and see if all settings to connect to the backend are correct.
In addition in the iview try to set the system-alias from SAP_LocalSystem to SAP_BW and retry.
Good Luck.
Benjamin

Got a Portal runtime error while using JSPDynepage

Hi,
Please help me out in the this error which I got when I tried to run the component developed based on JSPDynePage. I developed the component in the Developer Studio (version 2.0.4) in my local machine, built the project and deployed in the remote server using the option "Quick PAR Upload".
It says JSP file could not be found.
Thanks in advance
Sushma
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
Cannot find JSP file: JSPFileInfo :27242692 JSP File : D:\usr\sap\NPL\JC03\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\Bean_Test1\pagelet\BeanJsp.jsp Class Name: sapportalsjspBeanJsp Java File : D:\usr\sap\NPL\JC03\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\Bean_Test1\work\pagelet\_sapportalsjsp_BeanJsp.java Package Name : pagelet Class File : D:\usr\sap\NPL\JC03\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\Bean_Test1\work\pagelet\_sapportalsjsp_BeanJsp.class Is out dated : true.
Exception id: 01:45_03/11/04_0004_37482850
See the details for the exception ID in the log file

Hi,
I am also facing the same problem.
1) EP6 SP7
2) As mentioned in the error message there is no work directory in the mentioned path.
3) Please find beow portalapp.xml and log file.

<?xml version="1.0" encoding="utf-8"?>
<application>
<application-config>
 <property name="SharingReference" value="com.sap.portal.htmlb"/>
</application-config>
<components>
 <component name="default">
 <component-config>
 <property name="ClassName" value="Ex1"/>
 <property name="SecurityZone" value="Ex1/low_safety"/>
 </component-config>
 <component-profile>
 <property name="tagLib" value="/SERVICE/htmlb/taglib/htmlb.tld"/>
 </component-profile>
 </component>
</components>
<services/>
</application>

Exception:
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
Component : Ex1.default
Component class : Ex1
User : Administrator
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
at com.sapportals.portal.htmlb.page.JSPDynPage.doOutput(JSPDynPage.java:76)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:109)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
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:627)
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:232)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
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:153)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:337)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:315)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:815)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:238)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
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:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:151)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: Cannot find JSP file: JSPFileInfo :16447115
JSP File : D:
usr
sap
P66
JC00
j2ee
cluster
server0
apps
sap.com
irj
servlet_jsp
irj
root
WEB-INF
portal
portalapps
Ex1
pagelet
Ex1.jsp
Class Name: sapportalsjspEx1
Java File : D:
usr
sap
P66
JC00
j2ee
cluster
server0
apps
sap.com
irj
servlet_jsp
irj
root
WEB-INF
portal
portalapps
Ex1
work
pagelet
_sapportalsjsp_Ex1.java
Package Name : pagelet
Class File : D:
usr
sap
P66
JC00
j2ee
cluster
server0
apps
sap.com
irj
servlet_jsp
irj
root
WEB-INF
portal
portalapps
Ex1
work
pagelet
_sapportalsjsp_Ex1.class
Is out dated : true
at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:96)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:931)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
... 38 more
#1.5#000C76EEC65400440000000F000001E80003E8A8BBC24BD7#1100236331418#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#99#####SAPEngine_Application_Thread[impl:3]_26##0#0#Info##Plain###UserAgentHook: component com.sap.portal.runtime.system.hooks.ErrorComponent supports (*, *, *) #
#1.5#000C76EEC654004400000010000001E80003E8A8BBC250B2#1100236331418#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#99#####SAPEngine_Application_Thread[impl:3]_26##0#0#Info##Plain###------PRT AbstractPortalComponent: calling doContent for portal component: com.sap.portal.runtime.system.hooks.ErrorComponent#
#1.5#000C76EEC654005B00000005000001E80003E8A8BC0E32CF#1100236336397#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#96#####SAPEngine_Application_Thread[impl:3]_2##0#0#Info##Plain###UserAgentHook: component com.sap.portal.runtime.admin.logviewer.default supports (*, *, *) #
#1.5#000C76EEC654004D0000000C000001E80003E8A8C46CFCDD#1100236476698#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#96#####SAPEngine_Application_Thread[impl:3]_0##0#0#Info##Plain###UserAgentHook: component com.sap.portal.runtime.admin.logviewer.default supports (*, *, *) #

Portal Runtime Error connecting MDM (Employee repository)

Similar Messages

Maybe you are looking for