Iview Personalization Error

Hi Expert,
We are having trouble in accessing iview personalization, normally when doing ctrl + right klik, the personalization screen would came up. Recently we had an issue with ume (we can not create new users) and we fixed it with applying sap note and upgrade the EA-HR component . However the personalization wont work now, it just showing a loading animation with endless looping. Can somebody help? Thanks in Advance.
Best Regards

Hi all, thanks for the reply so far. I've solved this problem with updating the EA-HR to the latest version along with other component.
Best Regards

Similar Messages

Webdynpro for ABAP iView personalization not sticking?

We are currently on EP7 and are having a very odd issue with ABAP Webdynpro iView personalization.
For our Java Webdynpro iViews, we have used iView personalization quite a lot to change field labels, add text, change button text, etcc. all via portal content administration (ctrl+rightclick to make changes from iView preview). These changes would show as custom iView parameters settings on the Java Webdynpro iViews. Then we could put these iViews into our own portal packages and move them to other portals (QA, Production, etc).
However, this is not working quite right with our ABAP Webdynpro iViews. We personalized an iView on our DEV portal. The personalization changes showed just fine for all users (ie. changes to input field labels). However, no new parameter settings show for the iView for the personalization. Also, after packaging, exporting and then importing the iView into the other portals (like moving from DEV to QA), the personalization is gone. We had to manually recreate this on the QA system. However, we do NOT want to do this on the production portal of course nor do we want this to be the method/solution going forward.
So has anyone seen this? Is this some issue/difference between the ABAP and Java webdynpro iView templates?

If it is WebDynPro ABAP iview, if you do the personalization, then your personalization is persisted in ABAP stack. You need to transport it in ABAP i.e R/3 development system to R/3 Quality system. Transporting only iview is not enough.
Note : If you do the personalization for the ABAP iview, it will not be saved in the portal, it will be stored in the ABAP stack.
Thanks
Manoj K

Java Iview Runtime error after logon

Hello,
we are facing some problem regarding our EP 7.0 SP13. We have an anonymous page as our home page, with some anonymous ivews, like "help", "news", etc and one iview with authentication set to default where users log into the portal and access to the private section of the portal.
That ivew does a redirection to /irj/portal and since the user is athenticated it will led him to the private home. The problem is that after logon, a Java iview runtime error appears, and users must refresh the browser to access the private section. (user is logged before the error appears).
We have checked this is not happening with users with "super admin" o "content admin" role. They are able to log into the portal, and redirection is working fine. So we think there can be some problem with security zones or authentication somewhere in the portal, but since this is the standard logon component i don´t know why is this not working.
We have checked that the redirection is working, and we have made some tests with different kind of iviews like KM iviews, URL iviews, pictures, etc. Only admin users are able to log in correctly, the others get the java iview runtime error, so we think the problem is with to standard logon...
Here goes a trace of our problem (defaultrace.trc):
#1.5 #000802B3F434005C00000434000024680004646E64997E00#1236325203820#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection#
#1.5 #000802B3F434005C00000435000024680004646E64998C55#1236325203820#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:304)#
#1.5 #000802B3F434005C00000436000024680004646E64998E05#1236325203820#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)#
#1.5 #000802B3F434005C00000437000024680004646E6499900A#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
#1.5 #000802B3F434005C00000438000024680004646E64999183#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)#
#1.5 #000802B3F434005C00000439000024680004646E649992D1#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5 #000802B3F434005C0000043A000024680004646E6499941A#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)#
#1.5 #000802B3F434005C0000043B000024680004646E6499955B#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5 #000802B3F434005C0000043C000024680004646E64999690#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)#
#1.5 #000802B3F434005C0000043D000024680004646E6499984F#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)#
#1.5 #000802B3F434005C0000043E000024680004646E6499999C#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)#
#1.5 #000802B3F434005C0000043F000024680004646E64999AEB#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)#
#1.5 #000802B3F434005C00000440000024680004646E64999C2F#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)#
#1.5 #000802B3F434005C00000441000024680004646E64999D76#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)#
#1.5 #000802B3F434005C00000442000024680004646E64999EDA#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)#
#1.5 #000802B3F434005C00000443000024680004646E6499A01D#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)#
#1.5 #000802B3F434005C00000444000024680004646E6499A15E#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)#
#1.5 #000802B3F434005C00000445000024680004646E6499A30A#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)#
#1.5 #000802B3F434005C00000446000024680004646E6499A479#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.5 #000802B3F434005C00000447000024680004646E6499A5B7#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
#1.5 #000802B3F434005C00000448000024680004646E6499A718#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
#1.5 #000802B3F434005C00000449000024680004646E6499A855#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
#1.5 #000802B3F434005C0000044A000024680004646E6499B6CC#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: PortalRuntimeException#
#1.5 #000802B3F434005C0000044B000024680004646E6499B86B#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:284)#
#1.5 #000802B3F434005C0000044C000024680004646E6499BA7E#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     ... 20 more#
#1.5 #000802B3F434005C0000044D000024680004646E6499CB8B#1236325203836#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.core.PortalRequestManagerException: PortalRuntimeException#
#1.5 #000802B3F434005C0000044E000024680004646E6499CD54#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:143)#
#1.5 #000802B3F434005C0000044F000024680004646E6499CE9B#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#
#1.5 #000802B3F434005C00000450000024680004646E6499CFDD#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)#
#1.5 #000802B3F434005C00000451000024680004646E6499D130#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ContentExceptionHandler.handleException(ContentExceptionHandler.java:100)#
#1.5 #000802B3F434005C00000452000024680004646E6499D277#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ContentExceptionHandler.handlePortalRuntimeException(ContentExceptionHandler.java:27)#
#1.5 #000802B3F434005C00000453000024680004646E6499D512#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.handleRequestException(PortalRequestManager.java:917)#
#1.5 #000802B3F434005C00000454000024680004646E6499D677#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:803)#
#1.5 #000802B3F434005C00000455000024680004646E6499D7F3#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)#
#1.5 #000802B3F434005C00000456000024680004646E6499D943#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     ... 20 more#
#1.5 #000802B3F434005C00000457000024680004646E6499EB58#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###Caused by: java.lang.UnsupportedOperationException: this implementation does not support getComponentContext()#
#1.5 #000802B3F434005C00000458000024680004646E6499ECFD#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.service.hook.RedirectNode.getComponentContext(RedirectNode.java:50)#
#1.5 #000802B3F434005C00000459000024680004646E6499EE40#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:343)#
#1.5 #000802B3F434005C0000045A000024680004646E6499EF97#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:238)#
#1.5 #000802B3F434005C0000045B000024680004646E6499F0E1#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#
#1.5 #000802B3F434005C0000045C000024680004646E6499F21D#1236325203852#System.err#sap.com/irj#System.err#javier#7063####017208f00a2211de8d53000802b3f434#SAPEngine_Application_Thread[impl:3]_23##0#0#Error##Plain###     ... 27 more#
can anyone help us with this problem?
Thanks in advance

The problem was solved, it was a permission problem.
The anonymous role which allow access to the anonymous section of the portal was assigned to anonymous user, but it hasn´t everyone permission. So anonymous users were able to see anonymous pages, but when they login they lose the role, and java iview error happened, unless they had admin rights.
Solved assigned by assigning everyone to that role.
Thanks

Issue of Personalization error while running Photoshop ver.8 on Win 7

I recently upgraded my operating system to Windows 7 Enterprise edition (ver 6.1.7600 Build 7600) from Windows XP Professional. Now the issue is that after installing the licensed version of Adobe Photoshop CS (Adobe Creative Suit CS) on Win 7, I am unable to open it due to recurring error which says "Could not complete your request because of missing or invalid personalization info." At the same time, I am able to open Adobe Imageready CS and Illustrator CS without any glitch. I can see the serial nos. on the splash screen. Also my Acrobat Reader is also not working due to personalization error.
I tried contacting the Adobe Tech support via Chat service, but the only reply I got from them was to upgrade to the latest version since Win 7 does not support Photoshop CS.
If there is any quick fix to this issue is greatly appreciated.

If you are not already, make sure to run with administrative privileges. Otherwise try compatibility mode for XP or even install the XP virtual machine...
Mylenium

IView Personalization (Web Dynpro Java) for Anonymous User

Hello All,
Is it possible for anonymous user to see iView personalization (Web Dynpro Java) when personalized by an administrator? What I did was create new role and iView making available to anonymous user. This work fine meaning I can view iView using URL http://<servername>:<port>/irj/portal/anonymous . But the personalization I made to iView using administrator mode launching iView in preview mode and then using personalization dialog by choosing Ctrl and secondary mouse button to personalize is not showing. Iu2019m currently on EP7 SP15 and using iView type Web Dynpro Java for the development component sap.com/tcsecumewdenduser application name LogonHelpApp.
Any help is very much appreciated.
Many Thanks,
Gary

Hello Michael,
Yes, the Web Dynpro for Java Personalization is working perfect for non-anonymous users. The issue is when I view same iView using anonymous URL http://<servername>:<port>/irj/portal/anonymous the personalization is not showing just defaults back to the original Web Dynpro Java application settings. The iView that I created and personalized is the new Logon Help Dynpro Java application (LogonHelpApp). Is there some permissions that restricts anonymous user to view personalization?
Koti Reddy Iu2019m using the Web Dynpro for Java Administrator Personalization. Here is the documentation [http://help.sap.com/saphelp_nw70/helpdata/en/42/ed3ce7f8593eebe10000000a1553f7/frameset.htm |http://help.sap.com/saphelp_nw70/helpdata/en/42/ed3ce7f8593eebe10000000a1553f7/frameset.htm ]
Thank You for your help,
Gary

Reading iview personalization language in Web Dynpro java

HI
How can i read Iview personalization language in webdynpro java netweaver 7 enviroement?
WDWebContextAdapter.getWebContextAdapter().getRequestParameter("sap-locale") is deprecated it seems.
regards
PG

Hi Pranav,
In that case why dont you try to use the PCD API to access iView properties
Check this link:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/314ae7a5-0c01-0010-c198-9c7c5e8cee46
/people/daniel.wroblewski/blog/2006/08/15/pcd-ii-creating-portal-objects
You would require following jars for accessing PCD data:
com.sap.portal.usermanagementapi.jar,
com.sap.portal.pcd.glserviceapi.jar,
com.sap.portal.ivs.api_iview_api.jar
This thread contains the links for accessig the PCD content properties. Please check this as well:
iView Properties
I hope this solves the issue.
Thanks and Regards,
Pravesh

Java iview runtime error occuring in EP

Dear Friends ,
We are currently getting java iview runtime error while trying to
access EP logon screen through one of our application server.
We are not facing any errors while trying to access the same logon
screen through the other 2 application servers.
Please look into this issue.
Regards
Gaurav

Hi,
Check whether is there any network problem between application server and CI.
This problem generally comes when there is a problem between connection of UME.
Thanks
Anil

IView Personalizations

Hello,
I made some Personalization changes to the Dev. Portal which worked fine , I then transported them to the QA Portal ,the changes are not visible there. I looked at the below thread:
http://forums.sdn.sap.com/thread.jspa?threadID=836417
So where can we change the User Language for Portal.
Also, when I manually tried to made the same Personalization Changes in QA Portal with Content Admin. , the changes are not getting reflected.
Any help would be highly Appreciated.

Hi
Please look at these links for handling transport packages with personalization:
[Exporting Personalization Data|http://help.sap.com/saphelp_nw70/helpdata/EN/e6/2cd4121a87405a90c91c09ec74cc8c/frameset.htm] and
[Creation of an EPA Archive for the Portal Export|http://help.sap.com/saphelp_nw70/helpdata/EN/cb/8a6b8d9048964db7c2e0721f4c42d5/frameset.htm] and [Iview Personalization Transport|http://forums.sdn.sap.com/thread.jspa?threadID=1617429]
Hope this helps!!
Best Regards
Vijay K

IView personalization example needed!

Hi guys,
I need an example of iview personalization. I know about the personalization of the pages and i can add iviews to it at the runtime.
I tried using iview personalization for a SAP Webdynpro Iview and SAP Transaction iview as well, however the only option coming at the time of personalization is to change the logon language, how can i add more options to it.
Or if someone can provide an example of iview personalization that would be really great. I do not want to edit portalapp.xml file right now. There must be some other options available.
regards
Justin

Hi Justin,
first: every WebDynpro iView has excactly one property that can be read by the WebDynpro application. All the parameters you want to send to your WD must be stored in this property. It's the property "Application Parameters". Your WD may need some values in here to change it's behaviour. The possible values depend on your specific WD application and may vary. Check the documentation of your WebDynpro application.
Second: What exactly is your business case? What do you want the user to personalize?
Third: As a complex work-around you may use PCD API from within your WD to change the properties of the WebDynpro iView. But I think you shouldn't do so.
Fourth: It is NOT possible to make the standard properties of a WebDynpro iView personalizable by configuration. You'll need to change the portalapp.xml of the wrapped around portal application.
HTH,
Carsten
P.S.: If you could post what your specific requirements are, maybe the community may have some more ideas.

IView Timeout Error in Production

Hi
We are having one application developed by JSPDynPage ...this application will do lots of DB transactions...Some times when the load is very high on the DB the users will get this Iview Timeout error and they will not see any thing in the portal Content Area.
Please help.
Thanks
Ajay

Hi,
Note however, that you should not create any threads on the java application server, this is not allowed by the Java EE specifiction since the application server is responsible for handling threads.
You could try to implement as a service (not sure if this will work), or a combination of a service and a message driven bean (service sends JMS message to MDB which process it, and sends back to the service which listens on a queue). Note however that the MDB solution has a high overheader (It does work, as I've implement it myself one time).
Dagfinn

BSP in EP6: How to provide/handle iView Personalization

Hi,
I have a custom BSP integrated into our EP6 portal and was wondering if there is a way to handle or allow the iView personalization dialog? Can a BSP personalized in the portal and if yes how?
Thanks for any insight!
Wolfgang

check the check box "<b>Supports Portal Integration</b>" in the BSP application properties.
in the BSP iview definition make sure
<b>Show 'Personalize' Option</b> is set to yes.
Regards
Raja

Portal Runtime Error in WD iViews during iView personalization

Hi,
I am using SAP's MDM iViews with some custom webdynpro application iViews in my netweaver portal 7.0. When I click on the personalize 'apply' button of any iView, the whole page gets refreshed. The standard SAP MDM iViews gets rendered without any problems. But the custom webdynpro iViews throw portal runtime error as shown below:
Portal Runtime Error
An exception occurred while processing your request
Exception id: 02:25_17/12/08_0106_18297950
Can anybody throw some light on this?
Regards,
Yuvaraj SG

Hi Yuvaraj,
Assign the user super admin role and see if the page opens fine or not.
If the page opens fine, remove the super admin role and check the permissions for the custom web dynpro applications.....
and see if enduser check box is marked or not.
And at the same time check the permissions of the content provided by SAP folder and your custom folder where you have similar roles or not.
For this navigate to System Administration - Permissions - Portal Content
For detailed analysis check nwa as suggested by Bala.
Hope this helps.
Cheers-
Pramod

WDA personalization error while creating a TR

Hi All,
Recently we have been doing some WDA Personalization by hiding a few fields on the WDA screens.
However, today while doing same thing for WDA HRASR00_PERSONNEL_FILE... everything is fine until you try to create a new TR.
From the drop down box when we select "Create a New TR" and say OK.. there is an error message displayed in the WDA screen as "Configuration 45FBD8A08069AF690DC6FD1ED096A36607 s"
We dont know what exactly is going on and not able to figure out the same.
Can anyone please help us?
Do let me know if you require other details.
Cheers,
Kunjal

Still Unsolved...

Java iview Runtime error in Portal Logon

hi
I login portal with
http://<ipaddress>:50000/irj/portal
Java iView Runtime
An exception occured while processing your request.
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
If this situation persists, please contact your system administrator.
Can any one help me,,,how to sort this error.
Regards
sushma

Hi Sushma,
It seems that there are problems with permissions in Security Zones.
Check this links below to know more:
http://help.sap.com/saphelp_nw04/helpdata/en/25/85de55a94c4b5fa7a2d74e8ed201b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ee/acd8403e37762ae10000000a155106/content.htm
Thanks
Mihir

Java Iview Runtime error at the time of logon

Hi All
i am getting the below error page instead of Portal log on Page.
At the same time when i am connecting to the NWA it is opening successfully,
There I am getting the login Page also.
But when i am trying http://<Server>:50000/irj/portal.
i am getting below error.
Java iView Runtime
Copyright 2002 SAP AG. All rights reserved.
An exception occured while processing your request.
If this situation persists, please contact your system administrator.
I have not touch the portal logon Page.
Neither i have modified any standard Portal page.
Kindly help me with you valuable suggestion and document.
It is effecting the business process of client.
Prashant krishen

Hi Robin,
Thanks for immediate response.
Please help me to find out the log.
i am using this path :
http://<Server>/irj/servlet/prt/portal/prtroot/com.sap.portal.runtime.admin.logviewer.defau
But here in the default trace there are so many default trace file like
defaultTrace.0.trc ;
defaultTrace.1.trc ;
defaultTrace.2.trc ;
defaultTrace.3.trc
defaultTrace.4.trc ;
defaultTrace.5.trc ;
in all the file date has not been maintained. That is why i am not able to send you the exact log .
kindly help me to find the log .
thanx in Advance.

Iview Personalization Error

Similar Messages

Maybe you are looking for