Portal runtime error. in PAR application

Hello Gurus,
i developed my own portal application for change portal password.
I used the follow blog for made it:
A Change Password Application
I compiled (without errors) and deploied application on my portal and i created a new iview based on my PAR file but when i try to launch preview i have follow error:
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 11:43_24/06/10_0007_7875550
Refer to the log file for details about this exception.
have you any idea?
in Log monitor i don't find any interesting suggestion
Alex

ok Thanks!!!
now work correctly!
But i have a problem:
When i press the botton for confirm the change pwd, the browser don't refresh target browser but open a new one session.
i think the broblem is in this instruction:
window.top.location.href="/irj/servlet..........."
any suggestion?
Thanks in advance
Alex

Similar Messages

Portal Runtime error when modifying: com.sap.portal.runtime.logon.par

Hello,
We need some help because we get 'Portal Runtime error: iView: N/A Component Name:N/A' error when trying to access portal logon screen.
This is what we've done:
We've modified com.sap.portal.runtime.logon.par file and we've uploaded it but it doesn't work. Because of the error, we've overwritten this file with the original one but now it's imposible to access portal.
The situation it seems to be like before the modification of the .par file but we get the same error and can't access portal.
Please, do you know what could be the problem?
Thanks in advance

Hi Belen,
Here are the steps you would need to take
1. import the original par file into the NWDS and name the project as
    com.sap.portal.runtime.logon
2. Make sure the project name is com.sap.portal.runtime.logon
3. use winzip/winrar to extract the com.sap.portal.runtime.logon.par file in
    a local directory
4.Under the lib you would find two jar files copy them and paste them in your project
   under dist>PORTAL-INF>lib directory
5.move the files cert....till umResetPass....jsp into the PORTAL-INF directory
6. export the par to the server in question
7. restart your server
This should solve your problem..
Thanks,
Gokul

Portal runtime error after modifying masthead par file

Hi experts,
i tried to upload com.sap.portal.navigation.masthead.par in the portal (productive system) after modifying tooltip text of u201CHelpu201D link. i used Archive uploader.
After upload, status messages are correct.
But now in the masthead area, i have red message :
"Portal runtime error"
"An exception occurred while processing your request"
I cannot also access the Browse Deploymentu2026
So now i cannot log off from the portal (except by restart computer)
In development system where I used the same procedure, everything is OK.
Please help!

Dev,
Please ensure that the changes are correct by to upload the orignial par.
The other way of modifying the par is as below,
*Upload the PAR into NWDS and add the jars htmlb.jar, com.sap.portal.htmlb_api.jar and servlet.jar through java build path of your par project and add the jar com.sap.portal.navigation.masthead_core.jar (you can get this by extracting your par and navigate to the folder PORTAL-INF -> lib) in PORTAL-INF -> lib folder of your project.
Make changes
Build project
Export into portal
Ram

Portal runtime error-std. masthead par file

Hi,
 If i am executing the components of Portalapp.xml file in the std. masthead par file,i am getting the following error.
 Can any body give some suggestion to rectifying this error.
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
com.sapportals.portal.navigation.HeaderiView.
Exception id: 04:43_05/12/07_0010_4968150
Regards,
Ravi.

hi,
 Thanks for your valuable suggestion.
 Where can i get the particular jar file "com.sap.portal.navigation.masthead_core.jar",if you have that jar file,
kindly send to me.
Mail id:[email protected]
Thanks in advance,
Regards,
Ravi.

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 (*, *, *) #

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

Portal Runtime error - Customization

Hi,
How to customize the Portal runtime error message page in portal.
Is it required to modify any standard par file for this? If so what par file needs to be modified.
Ramganesan Karuppaiyah

Ramganesan,
check these links
How to the Change the Application Stopped Message
How to Change the Dispatcher Running, No Server Connected Message
https://www.sdn.sap.com/irj/scn/wiki?path=/display/ep/customizing%252berror%252bmessages%252bin%252bportal
http://help.sap.com/saphelp_nw70/helpdata/en/65/18fc3f9ec4e669e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/47/1d5a4390524403e10000000a1553f6/frameset.htm
Thanks
Bala Duvvuri

Modified Login Page - "Portal Runtime Error".

Dear All,
I need to Customize the Portal Login Page. To do so, I followed the below steps.
1. Navigated to <J2EE_Engine_Instance>\j2ee\cluster\server<X>\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd. Found com.sap.portal.runtime.logon.par.bak.
 2. Make a copy of com.sap.portal.runtime.logon.par.bak and rename it renamed to delta.new.logon.par.
 3. Imported the Par File to NWDS as "delta.new.logon" in the EP Perspective and Modified the umLogonPage.jsp.
4. Deployed the imported portal application "delta.new.logon".
5. Copy delta.new.logon.par back to <J2EE_Engine_Instance>\j2ee\cluster\server<X>\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd.
6. Downloaded Authschemes.xml file from configtool and renamed as authschemes_delta.xml.
7. In the "authschemes_delta.xml", I replaced all occurrences of the string u201Ccom.sap.portal.runtime.logonu201D with u201Cdelta.new.logonu201D in the tags <frontendtarget> and save the file.
8. Then uploaded "authschemes_delta.xml" to the configtool under com.sap.security.core.ume.service node.
9. Then changed the "login.authschemes.definition.file" property custom value to authschemes_delta.xml
and restarted the server.
(NOTE: while making all the above changes , I didn't shutdown the server. The server was running.Only after completed all modifications, I restarted the server).
But after restarting , When i tried to open the login page with the url, "http://host:port/irj/portal",
I am getting an "Portal Runtime Error".
What would be the problem?
Thanks,
Eben Joyson

Eben,
Please try deploy the renamed file into portal from NWDS.
Steps are Here,
1. Download the latest par file from System Admin -> support -> Portal Runtime -> Browse Deploment -> download the logon par file. The file format would be par.bak/ .par format.
2. Store the file into your local computer.
3. Open NWDS and import the downloaded file into NWDS in different Name and press Finish button
4. Extract the locally stored par file and store the extracted file into a folder. Navigate to PORTAL-INF -> lib folder and copy the jars files.
5. Navigate to PORTAL0INF -> lib folder of your renamned project stucture in NWDS and paste the jar files there.
6. Right click on the project stucture and press excport to deply the file.
Done!
Ram

Portal runtime error while selecting page layout in WPC editor

Hello,
in web page composer, editing page, when i click on "select page layout" I have a portal runtime error popup.
The logfile shows the following :
#1.5 #005056834112005E0000000C00000FA800048E28A94966CC#1282205196819#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#1016#149##n/a##7ff9c93eab6811dfa9c70000003307de#SAPEngine_Application_Thread[impl:3]_15##0#0#Error##Java###10:06_19/08/10_0010_3344350
[EXCEPTION]
#1#com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error occurs during the rendering of jsp component
Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error in java compiling
Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: E:
usr
sap
EPD
JC00
j2ee
cluster
server0
apps
sap.com
irj
servlet_jsp
irj
root
WEB-INF
portal
portalapps
com.sap.netweaver.bc.util
lib
bc.util.public_api.jar(com/sapportals/wcm/WcmException.java):24: class WcmException is public, should be declared in a file named WcmException.java
(source unavailable)
1 error
I have the same by clicking on "check assignments"
Any help ?
Thanks

Hello Jego.
We faced the same issue after upgrade to EHP1 SP07 last week and managed to solve it by modification of layout.jsp and com.sap.nw.wpc.layoutmanager.LayoutBean within com.sap.nw.wpc.designtime.par. SAP's code requires an additional catch handler, so it is better to rise an OSS message.
As a workaround you may change a default layout for wpc main page (good for new pages) or manually edit output.xml for existing pages.
Best regards,
Aliaksandr Zhukau

Portal Runtime Error while checking the Transaction in Portal

Hi all,
We r in the phase of setting the configuration of Portal. We did the the template installer but when iam checking the transactions in Portal ( System Administration--> Support--->SAP Apllication) , it is throwing me the following error.
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
Missing Property 'ClassName' in property file for layer'Transaction/WinguiSSOLayer'..
See the details for the exception ID in the log file
Can anybody help me in this regard.
Thank in Advance.

Hi Niyati,
I guess check through -->
Under "Personalize > User Profile" the checkbox "Activate Accessibility Feature" must be unchecked!
as, people earlier also faced this issue and SAP provided this solution.
Also an alternative solution for this is like --
Go to:
<Drive>\usr\sap\<SID>\JC<Instance No.>\j2ee\cluster\server<Server No.>\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\property\Transaction
and see the content of the 'WebGuiSSOLayer.properties' file.
One of the entries is ''ClassName'. The value on a 'valid' portal is: com.sapportals.portal.sapapplication.itsdetection.ITSDetectionLayer
If it's not the case, then go to:
<Drive>\usr\sap\<SID>\JC<Instance No.>\j2ee\cluster\server<Server No.>\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd
rename the file 'com.sap.portal.appintegrator.sap.par.bak' to 'com.sap.portal.appintegrator.sap.par' open the par file and edit the file ''WebGuiSSOLayer.properties' (add the relevant entry for ClassName).
Save the file (still with the par extension)
Restart the portal (if everything is OK then the bak extension will be added to the filename).
Just try this, hope it works.
Reward points if helpful
Regards,
Shailesh Nagar
Edited by: Shailesh Kumar Nagar on Jan 22, 2008 7:16 AM

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 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 when opening Webflow workitem in UWL

Hi,
I have recently configured the UWL to pick up workitems from SAP workflow on a background system. The workitems are appearing OK in the Task folder. However, when I try to open a workitem by double-clicking on it, I get the following error:
Portal Runtime Error
An Exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 05:33_30/09/10_0010_24209150
Refer to the log file for details about this exception.
NB. This only seems to happen for items that would be shown via the SAP GUI (E.g. a Confirming a task completion or user decision). The workitem runs OK if it is for a task that is visualised as a Web Dynpro app and specified in transaction SWFVISU.
I have not configured Delta Refresh options in the Workflow Administrator so do not know if this is a possible reason (I assumed that this would not cause a problem and would simply mean that refreshes only occur once every 60 seconds). Any help would be greatly appreciated. I am fairly new to Portal & UWL I would also be grateful if someone could tell where I can find the relevant log files referenced in the original error.
Regards
Simon

Hey Simon,
Welcome to UWL :). Portal Runtime Errors in UWL don't always signify that there is a UWL issue. This could be a permissions problem, etc. I'm not sure what version of the portal that you are using. But here is a little trick for you when checking logs...you can enter in the following: irj/servlet/prt/portal/prtroot/com.sap.portal.runtime.admin.logviewer.default
and check the log file with the id that was given in the error.
Exception ID: 05:33_30/09/10_0010_24209150 is your exception id. Search for the log files in the default trace and see what the exact error message is. If you can post this here it would be great.
The log files can be found in the following location:
/usr/sap/<SID>/JC<InstanceNumber>/j2ee/cluster/
server<number>/log
or by entering the URL that I mentioned above.
Please let me know in the next reply what the portal version is:
You can get this information by doing the following:
a. log on to the portal
b. backspace out the irj/portal section of the URL
c. click enter.
d. You are now at the J2EE administration page.
e. Next, click on the system information link
f. Please click on the all components link
g. Please attach this information to the message.
I am interested mostly in the UWLJWF component but if you can attach the full software component info to this post that would be great...
Please note, that note number 1133821 is an important note that is needed in the UWL. Did you maintain your RFC destination accordingly?
Here is some additional information to help you too since you are new to UWL:
[UWL Wiki|https://www.sdn.sap.com/irj/scn/wiki?path=/display/bpx/uwl+faq]
[UWL Forums|SAP Enterprise Portal: Application Integration;
[Business Task Management|http://help.sap.com/saphelp_nw70/helpdata/en/9e/ccf62fff3e4a45a634e592dabb45d5/frameset.htm]
[Using Universal Worklist|http://help.sap.com/saphelp_nw04s/helpdata/en/57/c223be82104792a15c2df11377b9ed/frameset.htm]
[JavaDocs UWL API|http://help.sap.com/javadocs/NW04S/current/uw/overview-summary.html]
I hope that you find this information useful!
Best Regards,
Beth Maben
EP - Senior Support Consultant
AGS Primary Support, Business Suite & Technology
Please see the UWL Wiki @
https://www.sdn.sap.com/irj/scn/wiki?path=/display/bpx/uwl+faq ***

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

Portal runtime error while trying to run a MSS report

Hello gurus!!
 I setup the MSS reports launchpad and now I am seeing all the list of reports on the reports launchpad. I am able to click on all the links and each link opens up the relevant page and the selection criteria also comes up. However, on the last screen, I get a portal runtime error after I click on the report result button.
The trace file shows the following errors:
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[./log/defaultTrace.trc]/>
<!PATTERN[defaultTrace.trc]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!FILESET[17, 20, 10485760]/>
<!PREVIOUSFILE[defaultTrace.16.trc]/>
<!NEXTFILE[defaultTrace.18.trc]/>
<!LOGHEADER[END]/>
#1.5 #0050568444360067000005D2000005D400049F27DC8DD843#1300893459438#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#sap.com/tcwddispwda#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#SSUBBARAO#113523##n/a##ae3b7a53556011e0cd95000000191d7e#SAPEngine_Application_Thread[impl:3]_23##0#0#Fatal#1#/Applications/Xss#Java###null
[EXCEPTION]
#1#com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE
 at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
 at com.sap.xss.hr.cat.record.blc.RfcManager.rfcExecute(RfcManager.java:453)
 at com.sap.xss.hr.cat.record.blc.RfcManager.init(RfcManager.java:820)
 at com.sap.xss.hr.cat.record.blc.wdp.InternalRfcManager.init(InternalRfcManager.java:280)
 at com.sap.xss.hr.cat.record.blc.FcCatRecordInterface.onInit(FcCatRecordInterface.java:353)
 at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface.onInit(InternalFcCatRecordInterface.java:268)
 at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface$External.onInit(InternalFcCatRecordInterface.java:542)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
 at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendar.onInit(VcCatCalendar.java:251)
 at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendar.onInit(InternalVcCatCalendar.java:194)
 at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendarInterface.onInit(VcCatCalendarInterface.java:162)
 at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface.onInit(InternalVcCatCalendarInterface.java:146)
 at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface$External.onInit(InternalVcCatCalendarInterface.java:222)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
 at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
 at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
 at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
 at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
 at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
 at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1346)
 at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
 at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
 at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:595)
 at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:867)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java: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)
Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE
 at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
 at com.sap.xss.hr.cat.general.model.slim.CatsModelSlim.hrxss_Cat_Wd_Record(CatsModelSlim.java:245)
 at com.sap.xss.hr.cat.general.model.slim.Hrxss_Cat_Wd_Record_Input.doExecute(Hrxss_Cat_Wd_Record_Input.java:137)
 at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
 ... 64 more
Could anybody please guide me how to fix this error and get the reports working properly?
Any help with this is much appreciated.
Thank you!
~Maria Kutty~

Hi,
Please refer to note 878440.
Thanks
Prashant

Portal runtime error. in PAR application

Similar Messages

Maybe you are looking for