Skip to Content

SAP Portal runtime Error- Root cause analysis to troubleshooting the issue



Summary:-

The information of this document contains how to check the logs in SAP Net weaver portal 7.3 and how to analyze, when the login page URL throwing “Portal runtime Error” issue and how to fix it.

Author: Brindavan Mookaiah


Designation: SAP BASIS Consultant


Table of content :-


1) Analysing the error at OS level …………………………..

2) Analysing the error at NWA………………………………



1) Analysing the error at OS level

Login page issue:–


While accessing the portal login page URL http:/<hostname>:<portno>/irj/portal and getting the below error then follow the step to find the root cause analysis  at OS level.


1) If the below error occurred while accessing the portal URL, then check the defualt trace log … dev_server0 log, dev_jsmon..etc..application log..etc..

then main log is default trace which you identified the issue appropriated the sap component to fix the issue.


Capture.PNG


Action :-


First check the JAVA server running fine or not using Jsmon command

1) Go to the directories /sapmnt/SID/profile and execute the below command

$ JSMON pf = <Instance profile>

Capture2.PNG

type ” process view”

Capture1.PNG

If the server running fine then check the default trace log with Exception ID : 36946350.

Capture3.PNG


you have to find the exact component to re-deploy.


Possible to reason to fix the issue


Portal Runtime Error – Login Error after installation or upgrade or any new component deployment

com.sapportals.portal.prt.runtime.PortalRuntimeException: PortalRuntimeException

at com.sapportals.portal.prt.core.PortalRequestManager.handleRequestException(PortalRequestManager.java:829)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:715)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:209)

Caused by Portal not finding the correct par file.

PAR File Name: com.sap.portal.navigation.service.par

Solution: After removing the BAK file com.sap.portal.navigation.service.par.bak the file which got converted after deploying PAR file com.sap.portal.navigation.service.par. Redeploy the PAR file com.sap.portal.navigation.service.par in <j2ee_home>/cluster/server/services/ servlet_jsp/work/jspTemp/irj/root/WEB-INF/deployment\pcd after stopping EP.


Deploy the SAP component cab be used either JSPM nor telnet.

Find the following link how to use telnet to deploy the sap component.

Deploy .sda Files without JSPM

(JSTSG)(Telnet)DeployController Commands – Technology Troubleshooting Guide – SCN Wiki


Portal Runtime Error

An exception occurred while processing a request for:iView : N/AComponent Name : N/A
Could not find portal application com.sap.portal.dotnet.framework.Exception id: See the details for the exception ID in the log file.

Here the com.sap.portal.dotnet.framework have some issue.

Solution :

Deploy the com.sap.portal.dotnet.framework.sda andcom.sap.portal.dotnet.services.systems.sda files to the portal.


Portal Runtime Error

An exception occurred while processing a request for:iView : N/AComponent Name : N/A
iView not found: PAR.PortalComponent.

Solution :


Deploy the requested portal component to the portal.


There are many issue can be highlighted and to troubleshoot is such case error “An error occurred in iview: N/A component.”

The following is very help to troubleshoot this kind of issue.

Troubleshooting – Technical Operations Manual for SAP NetWeaver – SAP Library


There are many issue can be highlighted and to troubleshoot is such case error “An error occurred in iview: N/A component.”

The following is very help to troubleshoot this kind of issue.

2) Analysing the error at NWA

If the error throws only for some other component while choosing the application navigation then it can be analyze through NWA.

Logon into the URL http://<server>:<port>/nwa  once you login with user-id and password

Then select System management tab –> select Monitoring –> select link and log and trace

You can access the default trace to find the error Exception ID message without login at OS level.

You can use the Exception ID of the error message displayed on the portal screen and find the exact component or error message line to fix the issue.

In some case that you have to find the caused issue in sap component inside the program line like space, null value sued to trim and ; various issue can be highlighted  in developer studio to fix the program issue.

Capture4.PNG

It might be some other issue with user mapping with back-end system will cause portal runtime error issue will appear. you have to analyse and find the exact issue to fix it.  I hope his information will helpful for troubleshooting  this kind of issue.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply