cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

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

Former Member
0 Likes
9,051

Hi All,

I create a new user in SAP Netweaver Portal, and I have assigned a role to this user which has a webdynpro application. I'm using Webdynpro for ABAP.

Now the problem is when I login into the newly created user and when I click on the role I am getting an exception. I have attached the snapshot of exception below. Please check it and solve the issue. I'm strucked here from yesterday. I'm not able to solve this problem.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Likes

Thanks to all for your valuable reply.

The problem is solved

Former Member
0 Likes

Hi,

Please elaborate on your actual error found in logs and resolution to fix this?

That way the thread may be helpful to others.

Johan

Former Member
0 Likes

The problem was with the mapping. We should have same user in EP system as well as the Backend system. So I created an user in the EP and same user in the Backend system also. But password can be different, password doesn't matter. This user must be mapped.

Former Member
0 Likes

Hi Satish,

I am getting the same error can you help me the same

Regards,

Prasad

Steffi_Warnecke
Active Contributor
0 Likes

Hello ,

did you see Satishs reply, how he resolved it?

The problem was with the mapping. We should have same user in EP system as well as the Backend system. So I created an user in the EP and same user in the Backend system also. But password can be different, password doesn't matter. This user must be mapped.

Did you check that and also the other suggestions, that were made in this thread?

Regards,

Steffi.

Former Member
0 Likes

I had created same user in R3 and Portal and mapped 105 also same but still i am getting this error

Regards,

Prasad

Steffi_Warnecke
Active Contributor
0 Likes

Hello Prasad,

Did you look the error up in the log files on the server or in the NWA like suggested here? There you get more information what is causing the error.

Regards,

Steffi.

divyanshu
Discoverer
0 Likes
Hi i got the same error can you please share the solution for better understanding.

Answers (3)

Answers (3)

Former Member

Hi Satish,

As they have suggessted in your log directory search for that except in the grep -l exception *.log as example.

Via the Netweaver administrator: http://<host>:<port>/nwa -> Monitoring -> logs and traces. Check for relevant timestamps.

- On the operating system level if you have access: ..\usr\sap\<SID>\JCxx\j2ee\server0\logs. Check the application logs and default traces. As they have suggessted in your log directory search for that except in the grep -l exception *.log as example.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c00249bc-190f-2d10-0a82-c46cf0994...

Also view this once you have found more details.

http://help.sap.com/saphelp_nw70/helpdata/en/95/f4ec418afa6430e10000000a1550b0/content.htm

Johan

Former Member
0 Likes

Thankx Johan...

Former Member
0 Likes

Hi satish,

I can see that you are getting an exception ID in the error message. Can you please search for this exception ID in the defaulttrace file and check what is the root cause of this issue.

If you paste that error from the trace file , i will be able to help you.

Regards

Shrikant

SrinivasanVelumani
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi,

Is the User Mapping done for the user which you have logged in. 

And also post the logs from nwa..

One more thing always use fully qualified domain name to access the portal..

Regards,

Srinivasan V