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

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 applying patch 12 to portal

hi experts,
i m getting following error
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.content_administration/com.sap.portal.content_admin_ws/com.sap.portal.webdynpro_ws/com.sap.portal.content_administrator/com.sap.portal.wd_content_administrator
Component Name : com.sap.portal.appintegrator.sap.WebDynpro
Exception in SAP Application Integrator occured: ApplicationIntegratorException.
Exception id: 09:30_22/01/08_0005_16892850
See the details for the exception ID in the log file
after applying patch 12 in portal
i m getting this error in guided procedures,Universal worklist ,webdynpro workset undfer content administration
Please suggest me the solution
regards,
vani

Hi Vani,
Just go to the System Configuration and UME configuration.
Now go to user mapping tab, and remove the entry for a reference system. Then check for the issue if persists, restart system.
Hope this helps!
regards
Atul Shrivastava

Portal runtime error after migrating to 7.3

Hi,
We have an enterprise portal --> portal application standalone type DC. We have been able to migrate the DCs to 7.3. The problem we are facing currently is that one of the applications does not load in the portal giving a portal runtime error. Looking at the log files, the errors being shown are to do with one specific type of class.
setClientEvent(com.sapportals.htmlb.enum.EventTrigger,java.lang.String) in com.sapportals.htmlb.EventValidationComponent cannot be applied to (com.sapportals.htmlb.enums.EventTrigger,java.lang.String)
CustomerInput.setClientEvent(com.sapportals.htmlb.enums.EventTrigger.ON_KEYDOWN, "onCustomerEnter()");
The above error shows that at runtime, it is trying to resolve 'com.sapportals.htmlb.enum.EventTrigger' but this class is deprecated in 7.3. The code which we have written has the right package which is com.sapportals.htmlb.enums.EventTrigger.
I am not sure why it is still trying to resolve with an older version. If I try to change the code and use the 'enum' package instead of 'enums', then the application fails again with the runtime error.
Thanks & Regards,
Vaishnavi

Closing this thread as it was solved. Apparently, there is a java method setClientEventExt() which takes an eventtrigger and an event as inputs.
Regards,
Vaishnavi

Portal Runtime Error after Upgrade 7.01 to 7.3

Hi,
i have a Problem after Upgrade a BW 7.01 to 7.3 SP5 the,
abap works fine but the Java Portal bring up Error on many time by choosing any funktion
for example:
try to use Portalcontent -> Systemlandscape -> SAP_BW
this error is shown.
Portal Runtime Error
Tracefile:
2011 11 24 13:05:51:546#+0100#Error#com.sap.portal.prt.connection#
#EP-PIN-PRT#tcepbcprtc~api#C0000A11295500740000000000E900F2#9281050000000004#sap.com/irj#com.sap.portal.prt.connection#FREYAD#3##8D780B5716941 1E1C8790000008D9E1A#a6e61adf169411e1cab50000008d9e1a#a6e61adf169411e1cab50000008d9e1a#0#Thread[HTTP Worker [@904797166],5,Dedicated_Application_ Thread]#Plain##
Exception ID:01:05_24/11/11_0004_9281050
[EXCEPTION]
com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Application name : com.sap.portal.appdesigner.framework
Component : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.pcmEditor
Component class : com.sap.portal.admin.propertyeditor.core_functionality.PCMEditor
-all Funktions in NWA are working
-Diagnose an Supporttool is Green !
Thanks Steven

Hi Raj,
You need to redeploy the patches in the message from Alexandra.
How to redeploy same component with JSPM?
JSPM does not allow to deploy an SCA with the same version (release, SP-level, patch-level) as an already deployed component. However, in some special cases you may need to redeploy an SCA with the same version. Use command line:
go "-config=/jspm/forceMode=true" "-config=/jspm/deployVersionRule=updateAll" to redeploy all SDAs. See note #1123333 for more options.
regards
Steven

Portal Runtime Error after Portal SP21 Patch Update

Dear GURU's,
Greetings!
We have installed and configured SAP Netweaver 2004 WAS Java and have EP 6.0 SR1 - SP9 system on Windows Server 2003, Enterprise Edition Service Pack 2 and MS SQL Server 2005 Service Pack 2.
We had connected the server to the backend R3 system and completed all the configurations for an HCM implementation with KMC. We had updated the SP level from SP9 to SP21.
When we were trying to access the portal system today we found a Portal Runtime Error when we launched the Portal URL. The error is mentioned below.
Portal Runtime Error
An exception occurred while processing your request
Exception id: 07:02_06/11/08_4102050
See the details for the exception ID in the log file.
We had not changed any of the configurations in the system, we also had experienced the same error in the UWL Administration link in the portal system and our portal consultant was working on the same.
Please help us in solving the error. We would be glad to know the reason of the error and also the measures to avoid the same in the future.
Expecting your reply at the earliest.
Thank you
Regards,
Vineeth

Dear Ravi & Vamshi,
Thank you very much for the reply.
I solved this error.
This is caused due to insufficient permissions that is configured in the security zones of the portal system.
The below mentioned document specifies further details and inital permission settings,
https://www.sdn.sap.com/irj/sdn/nw-portalandcollaboration?rid=/library/uuid/00bfbf7c-7aa1-2910-6b9e-94f4b1d320e1
Thank you
Regards,
Vineeth

Portal Runtime Error after System Refresh

Did a system refresh and now when I select a BI workbook that executed before the refresh I receive the error
"portal runtime error
an exception occurred while processing your request
exception id:09:27_07/02/11_0018_2780350
see the details for the exceptio id in the log file".
Queries run without erroring only the workbooks give this error... apprecitate any help - thanks

Hi Annette,
Did you clear all the cache, closed the browser and try again?
If the error still appears, check the error log.
Where are you checking the BI workbook? Is it through portal is it through an iview? If yes then check if the
application runs when the iview is previewed directly.

Portal Runtime Error after Login into EP

Hi all,
when i login into SAP Enterprise Portal,It is throwing Portal Runtime Error.
Error as follows :
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
com.sapportals.portal.navigation.INavigationNode.getHashedName()Ljava/lang/String;.
Exception id: 04:59_17/06/06_0022_1660050
See the details for the exception ID in the log file
How to Rectify this Error,Plz help me Out.
I will reward with the Points.
Thanks and Regards
Santosh Saraf

Hi Santosh,
This is related to memory issue...delete all the cookies and restart ur server..
regards
Amit

Can't See com.sap.portal.runtime.logon in list of PAR Files in Iview Wizard

Hello All,
I am trying to create an iview from PAR file com.sap.portal.runtime.logon which is the logon par file that has the logon page. But when I right click a folder in the PCD and click on New From PAR Iview I try to find on the list of available par files and I don't find the one named com.sap.portal.runtime.logon
Can anyone tell me if this has to do with the portalapp.xml file from com.sap.porta.runtime.logon.par file.? or with the Security Zones defined in portalapp.xml? Or does someone know why this PAR file doesn't appear on the list and how can I make it appear on this list of par files?
Any helpful ideas to solve this issue will give rewarding points.
Thanks
Luis

Hello,
What I want to do is to put the logon page in the light framework page so that the users can login from the anonymous portal. After I customize the logon page I want to create aniview in the detailed navigation.
If you want to see the jsp files that the com.sap.portal.runtime.logon.par file you have to go to the file system and copy the .par.bak file , rename it to .zip and all the files are there.
But my question is if this is a par file that is deployed in the portal , why I cant create an iview from this par file? From other forums I have read they say that creating an iview from this par file it will put the logon page where you want. But when I try to create an iview from PAR File the com.sap.portal.runtime.logon doesn't appear in the list of available par files.
Please help me on this and will give rewarding points.
Thanks
Luis

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-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.

Runtime error after uploading .par file

Hello experts,
I have a new problem with uploading the new .par file.
I have done following:
1. Download the .par file.
2. Import the par file to the NWDS
3. Import the private/lib folder structure manualy
3. Export the par file
4. Upload the par file(Systemadministration->Support->Portal Runtime->Administration Console
I haven`t modified anything at the par file. (Just for testing). I haven´t generate or build anything in the NWDS.
But after the sucessfull Upload I get a Portal Runtime Error in the Header Area with following ID:
Exception id: 10:04_10/09/08_5794550
Hope you can help me.
Thanks
Marco

hi,
With regard to your problem:
First of all the PAR might be uploaded properly.
Next you can look into the default trace log with the ID mentioned by you such that we can exactly figure out the problem.
try uploading your PAR files by using the following URL
http://<hostname>:<port number>/irj/servlet/prt/portal/prtroot/PortalAnywhere
Thank and regards,
Kris

Portal Runtime Error: Logon Page Modified!!!!

Hi all
I have modified the Logon Page to include a New Drop down.
I copied com.sap.portal.runtime.logon.par.bak to my NewParProject0.par and modified the Logon Page with the Following code addition:
 <tr>
 <td width="161" height="20">
 <label class=urLblStd for="logonCltfield">
 <%=logonLocale.get("CLIENT")%>
 *
 </label>
 </td>
 <td>
 <select id="clientType" class="DROPDOWN" style="width:2in">
 <option CLASS="DROPDOWN" value ="100" selected>100</option>
 <option CLASS="DROPDOWN" value ="110">110</option>
 <option CLASS="DROPDOWN" value ="120">120</option>
 <option CLASS="DROPDOWN" value ="130">130</option>
 </select>
 </td>
 </tr>
The above process is done as per the documentation given in the Customizing the Logon Screens
After building the new par file, I moved it into the ...\deployment\pcd
And i modified the authschemes.xml as per the details given in the help.sap.com(Changing the authschemes.xml File)
And even i tried changing value of the property login.authschemes.definition.file to the name of the new authschemes file.
I facing 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..
Help please!!!!!!
Thanks
Kam

Peter
My Logon screen will get 3 credentials from the User .
 1. User Id (Text appearing in the Screen is User)
 2. Password (Text appearing in the Screen is Password)
 3. Client (Text "CLIENT" should appear similar to the User Id and Password).
The Value field for the CLIENT should be of type DropDown.
Hope my requirement is clear. Please Advice on the procedure to be followed...
Thanks
Kam

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 in contentCatalogTree after applying SP11

HI,
I am getting a POrtal Runtime Error for the contentCatalogTree iView after I applied SP11. It was working fine before I patch the portal. Has anyone got a solution to this?
Here is the error stack:
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
iView not found: pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.content_administration/com.sap.portal.portal_content/com.sap.portal.contentCatalogTree.
Exception id: 09:49_11/04/05_0022_6990050
See the details for the exception ID in the log file
And the log file says:
#1.5#001279D06329005D0000000700000F280003F423583156CF#1112857570796#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#178####856f12c0a73311d9b39c001279d06329#SAPEngine_Application_Thread[impl:3]_23##0#0#Error#1#/System/Server#Java###Exception ID:03:06_07/04/05_0005_6990050
[EXCEPTION]
#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: iView not found: pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.content_administration/com.sap.portal.portal_content/com.sap.portal.contentCatalogTree
     at com.sapportals.portal.prt.deployment.DeploymentManager.getPropertyContentProvider(DeploymentManager.java:1937)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:230)
     at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
     at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
     at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:435)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:607)
     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:391)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
     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: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:162)
Anyone out there can help. Thanks in advance.

Hi all,
Apprantly it seems that the sequence to applying the SP Stacks plays a part. I reverted back to SP9 then went on to SP10, SP10 patch2 and then SP11 and it appears fine now.
Cheers

Portal runtime error after modifying masthead par file

Similar Messages

Maybe you are looking for