cancel
Showing results for 
Search instead for 
Did you mean: 

Portal runtime error

Former Member
0 Kudos

Dear Experts,

                 I had applied some add-on fourm ,wiki and required components  on sap netviewer portal 7.3 for EHP1.Now I am getting below run-time error.

An exception occurred while processing your request. Send the exception ID to your portal administrator.

Exception ID 07:33_31/12/13_1637350

See log file for details about this exception

How can I resolve error.Please do Needful.

Accepted Solutions (0)

Answers (7)

Answers (7)

Former Member
0 Kudos

Dear friends,

            I could not solve my problem.Please do needful.I had posted to SAP too. Still it's under processing since long time.

Thanks a lot for your replies.

Former Member
0 Kudos

HI Sahil

u had already good ideas here above but let me join this thread... Don't you have any chances to restore the portal as before patches?

Silly question, it's my ipad or there is not trace uploaded (perhaps i see few moderator activities....)

was the service pack update successful? (if im not wrong there should be also a good log at the end of the activity)

last but not least, Samuli mentioned lack of resources, did you check this part?

let us know

a

Former Member
0 Kudos

hi sahil ,

can you check once  with system alias and chk it properly and assign proper roles in portal with everyone role and try once

Former Member
0 Kudos

hi sahil ,

assign proper roles in portal and r3 for the user ur trying on to...... kindly chk in SU01 for that user with proper role assignment and in portal side also .....and kindly assign correct user in 105 infotype in  0001 subtype ........

Reagan
Advisor
Advisor
0 Kudos

Hello

The exception ID you first provided is 07:33_31/12/13_1637350

I was unable to find the exception ID which you have provided in your initial post in the default trace.

I could find exception ID's starting from 11:40_31/12/13_1637350 and this is what I could see:


#2.0 #2013 12 31 23:40:30:968#0-800#Error#com.sap.portal.prt.runtime#

#EP-PIN-PRT#tc~epbc~prtc~api#C000AC1091CE080E0000000000000F68#1637350000000004#sap.com/com.sap.portal.runtime.system.hooks#com.sap.portal.prt.runtime#snehal#238##A4F609A572B711E380F100000018FBE6#f20101c872b711e3b80500000018fbe6#f20101c872b711e3b80500000018fbe6#0#Thread[2042720949|com.sap.portal.runtime.system.hooks.ErrorComponent\#pcd%3aportal_content%2fevery_user%2fgeneral%2fdefaultAjaxframeworkContent%2fcom%2esap%2eportal%2econtentarea.content.pcd%3aportal_content%2fadministrator%2fsystem_admin%2fsystem_admin_role%2fcom%2esap%2eportal%2esystem_admin_ws%2fcom%2esap%2eportal%2esystem_configuration%2fcom%2esap%2ekm%2eAdminConfig%2fcom%2esap%2ekm%2eAdminConfigCM%2fcom%2esap%2ekm%2eConfigCM,5,Dedicated_Application_Thread]#Plain##

11:40_31/12/13_1637350

[EXCEPTION]

com.sapportals.portal.prt.runtime.PortalRuntimeException: There is no portal component associated with the following context: pcd:portal_content/administrator/system_admin/system_admin_role/com.sap.portal.system_admin_ws/com.sap.portal.system_configuration/com.sap.km.AdminConfig/com.sap.km.AdminConfigCM/com.sap.km.ConfigCM

Check whether this SAP note is relevant for this issue.

1730031 - Portal runtime error in HTML Viewer room part

Also there were other errors I have noticed in the default trace log. So I am not sure whether they are related or not.

I suggest you to consult these SAP notes as well.

1800616 - Some applications fail to start during server startup

1840895 - Failed components after upgrade to SAP Netweaver Portal 7.30

870234 - Portal doesn't come up during/after SP13 upgrade

1834097 - Error: "Failed to lookup External Link for:" in the portal – how to proceed the investigat...

A small suggestion would be to check the latest default trace with the exception ID when the issue happens.

Regards

RB

Former Member
0 Kudos

His AS JAVA has far more severe issues. For one component sap.com/com.sap.km.cm.main isn't running because of missing resources. I think someone who shouldn't be working on basis issues has.

Former Member
0 Kudos

Thanks a lot for your reply.

Should I undeploy component which are failed?

Reagan
Advisor
Advisor
0 Kudos

If that is the only option then yes.

But I would raise an OSS message and get this confirmed as well.

Regards

RB

Former Member
0 Kudos

I would generate a stack XML file in MOPZ, download all files and install everything with SUM. That way you will have a working AS JAVA again.

Former Member
0 Kudos

Hi  Samuli Kaski, Thank a lot for your reply. My system in not added in solman.That's why this problem occured.

Former Member
0 Kudos

This message was moderated.

Former Member
0 Kudos

I guess I should have instructed you to include only relevant parts of the defaulTrace as an attachment, not embedded in your response. Anyway, the problem you are seeing is because the components haven't been properly deployed. I suggest you get help from someone who knows what to do rather than trying to fix it yourself.

former_member185239
Active Contributor
0 Kudos

Dear Sahil,

Please paste the content of latest default and application log

With Regards

Ashutosh Chaturvedi

Reagan
Advisor
Advisor
0 Kudos

Hello

Check the latest default trace when this issue happens.

Regards

RB

Former Member
0 Kudos

Locate the entry from the defaultTrace and post here. The exception ID itself tells nothing. Have you tried restarting the portal? When do you get the error? When logging in, navigating somewhere, clicking on something? I suggest you learn how to create proper discussion threads if you want people to help you.