Java-iViews-Errors in BP for CRM

After importing BP 6.0 for CRM 4.0, the Java iViews (e.g. Today's Activities or My Tasks) don't work. Instead we get an error like this:
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
com/sap/pct/crm/generics/context/CRMContextException.
Exception id: 08:52_11/10/04_0004
See the details for the exception ID in the log file
The WAS and ITS iViews of the BP are running fine and the import log of the BP says the iViews are correctly installed.
Is there something wrong with the JCO?

Hi Marko,
I don't know the BP, but this exception clearly states that within the method getPage within the class ListPortalComponent a CRMContextException is referenced (probably should be thrown), which in fact does not exist within the classpath.
If I would have the BP at hand (and you have, that's your advantage), just check if the class exists. If not, you could try a workaround and check the cause for the exception, if you achieve that it should not be thrown, the JVM won't complain...
Is the BP delivered within one or within several PAR's? If it takes several PAR's, maybe CRMContextException is in one, ListPortalComponent in another PAR and no SharingReference could be set (but I wouldn't call this very probable for the common package com/sap/pct/crm/generics; nevertheless, it's an idea).
Just try to analyze around this...
Hope it helps
Detlev
PS: You didn't mark your question as question?!

Similar Messages

Error in BP for CRM

Hello Community,
After importing BP 6.0 for CRM 4.0, the Java iViews (e.g. Today's Activities or My Tasks) don't work. Instead we get an error like this:
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
com/sap/pct/crm/generics/context/CRMContextException.
Exception id: 08:52_11/10/04_0004
See the details for the exception ID in the log file
The WAS and ITS iViews of the BP are running fine and the import log of the BP says the iViews are correctly installed.
Thanks.
Kind Regards,
OR

Hi Olaf,
please see Java-iViews-Errors in BP for CRM and CRMContextException (here especially Michael Healey's reply).
Hope it helps,
Detlev

News iviews in business package for CRM

Hi ,
I have uploaded the standard business package for CRM . In the first workset for "Home" the page for "news" has ivews like
1) press releases referring to the path /sapcrmnews/Partnernews/PressReleases
2) partner news referring to the path /sapcrmnews/Partnernews/PartnerNews
3) success stories referring to the path /sapcrmnews/Partnernews/SuccessStories
etc ...
All of these iviews do not display the content and show an error message "Item not found . The item you are attempting to access is not available. Check that the name or link is correct. You might also check whether the associated repository is currently accessible."
When I go to the KM content I can only see the folder /sapcrmnews but the directory structure that these iviews are looking for cannot be located . Should not the directory structure required by these iviews get created automatically when the business package is uploaded ? If not then do we need to manually create the directory structure ? How does the content get displayed in the iviews for the standard business package ?
Regards
Deepak Singh

Hi Thomas,
You have posted in the wrong forum. A solution has been already provided in "CRM Development" forum for this issue. Check out this,
Re: CRMC_BLUEPRINT_C/ PCUI Attachments Viewable

SAP_BASIS IMPORT_PROPER Error during SPAM for CRM Upgrade

Hi All,
During SPAM IMPORT_PROPER for component SAP_BASIS, encountered error. Checking the Import Logs of the queue, we see error logs in Activate inactive runtime objects. Sample message below.
May we ask how to fix the error for us to be able to continue the upgrade? Thanks.
   Activation of sample nametabs with appended fields
   06:17:30: Retcode 512: error in DDL statement for ALCCMCUSTP                     - repea
   t
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of ALCCMCUSTP
   06:17:42: Retcode 512: error in DDL statement for ALCCMCUSTV                     - repea
   t
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of ALCCMCUSTV
   06:17:55: Retcode 512: error in DDL statement for ARC_DESTR_VETO                 - repea
   t
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of ARC_DESTR_VETO
   06:18:07: Retcode 512: error in DDL statement for DB6_OPTPROFILE                 - repea
   t
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of DB6_OPTPROFILE
   06:18:19: Retcode 512: error in DDL statement for FDT_TRACE_0200                 - repea
   t
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of FDT_TRACE_0200
   06:18:31: Retcode 512: error in DDL statement for FDT_TRACE_0201                 - repea
   t
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of FDT_TRACE_0201
   06:18:43: Retcode 512: error in DDL statement for GE071KF_OLD_NT                 - repea
   t
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of GE071KF_OLD_NT
   06:18:55: Retcode 512: error in DDL statement for GTABKEYEXC20                   - repea
   t
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of GTABKEYEXC20
   06:19:07: Retcode 512: error in DDL statement for GTABKEY_CASCADE                - repea
   t
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of GTABKEY_CASCADE
   06:19:19: Retcode 512: error in DDL statement for GTABKEY_COMPEXCL               - repea
   t
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of GTABKEY_COMPEXCL
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of GTABKEY_COMPSETS
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of GTABKEY_C_SYS
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of GTABKEY_EXT
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLS
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of IACXU
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLS
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of IACXUT
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLS
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of IACXU_C1
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of IACXU_C_TEMP
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of STORE_HELP
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of STORE_LINK_IND
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of SWWOUTBOX
   Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
   Error in DDL statement for when executing ADD-FIELD of
           (dummy, do not translate)
   No DDL commands found for activation of SWWWITEXT
           21 shadow nametab activations resulted in errors
   Begin: Activation of shadow nametabs with DDL (2014/03/19 06:17:30)
   End:    Activation of shadow nametabs with DDL (2014/03/19 06:19:31)
   Begin: Activation of shadow nametabs with DDL (2014/03/19 06:19:31)
           (dummy, do not translate)
Regards,
Philip

Hi Philip,
Could you please check the below SAP Note. It is a composite notes which has listing of various errors during upgrade
822379 - Known problems with Support Packages in SAP NW 7.0x AS ABAP
Hope this will be useful
Thanks and Regards
DJ

Error in BP for External Procurement

Hi together,
I've set up the BP for External Procurement 60.2 as described in the manual. From all pages only the iViews "Overview-Purchasing" and the iView Vendor Confirmations on the Overview works without error. The other iViews wouldn't displayed (Page cannot displayed).
I'm using EP 6.0 SP13 and ECC 5.0. The BSP's are activated in SICF.
If I test the iView i got in the default trace the error "java.lang.NumberFormatException: For input string: "10985373858"". I haven't any idea, from which point this number will come.
Have anybody experince with this package?
Regards Thomas

Hi Olaf,
please see Java-iViews-Errors in BP for CRM and CRMContextException (here especially Michael Healey's reply).
Hope it helps,
Detlev

Error in Installation of JAVA Add-in for CRM system

Hi All,
During the installation of Java Core Upgrade 6.20 for CRM, I am encountering problems during the SDM deploymentt stage.
The error is as follows:

See 'C:\j2sdk1.4.2_08\bin\java -Xmx64M -Djava.ext.dirs="E:\SAPCRMInstallables\J2EE_WAS620\SDM/libs" -jar "E:\SAPCRMInstallables\J2EE_WAS620\SDM/SDM.jar" autoupdate "sdmHome=E:/usr/sap/<SID>/DVEBMGS00/SDM/program" "popDir=E:\SAPCRMInstallables\J2EE_WAS620\SDM"' output in 'C:\SAPinstMSSQLSAPINST\java.log'.
ERROR 2005-08-19 15:05:56
MOS-01012 PROBLEM: 'C:\j2sdk1.4.2_08\bin\java -Xmx64M -Djava.ext.dirs="E:\SAPCRMInstallables\J2EE_WAS620\SDM/libs" -jar "E:\SAPCRMInstallables\J2EE_WAS620\SDM/SDM.jar" autoupdate "sdmHome=E:/usr/sap/<SID>/DVEBMGS00/SDM/program" "popDir=E:\SAPCRMInstallables\J2EE_WAS620\SDM"' returned with '4' which is not a defined as a success code.
Any pointers in solving this problem would be of great help. Thanks in advance,
Regards,
Prasenjit

Please advice if you were able to find a solution.

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

Java Session error occurred

Hi Experts,
We are in process of upgrading CRM 4.0 to CRM 7.0, sometimes we face " Java session error occurred" popup in CRM 7 while working on pricing or in some tabs of CRMD_ORDER
Any idea why this is error is happening, we checked all IPC routines and are also woking fine.
Expert advise needed.
Thanks.
Abhishek

Thanks for reply Leon,
Just got the log of the java messages in SM53 Log Administration, and found that Shared Closure has no space to create or save the session. Obviously the problem is lack of space.
I dont have idea how to set the space profiling for the shared closure, can you please guide me on this or how to find resolution for this space related issue.
Thanks in advance.
Abhishek

Portal Runtime Error when previewing iViews from BP for CRM 4.0 (60.2)

Hello,
We have imported Business Package for CRM 4.0 (60.2) into EP 6.0 (Version: 6.0.19.0.0) according to the installation guide(InstGuide_EN_CRM40_502.pdf). We have also defined SAP_CRM and SAP_R3 Systems in Portal System Landscape Editor. And we have also set the permissions for the user with which we are logged in on the "Portal Content->Migrated Content->EP 5.0" folder with "Read" permission and checked the "End User" option.
Now when we do a test preview for "Portal Content->Migrated Content->EP 5.0->iViews->SAP CRM 4.0: Sales->Activities" iView in PCD i get Portal Runtime Error in a new window with following information:
Portal Runtime Error
An exception occurred while processing a request for :
iView : com.sap.portal.appintegrator.sap.BSP
Component Name : com.sap.portal.appintegrator.sap.BSP
Error occurs during the rendering of jsp component.
Exception id: 08:40_22/01/07_0001_6052850
See the details for the exception ID in the log file

We get this similar message for few other iViews as well. Following is the details from the log file for this exception ID:
###Exception ID:08:40_22/01/07_0001_6052850
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
Component : com.sap.portal.appintegrator.sap.BSP
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : <USER_ID>
 at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
 at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
 at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
 at com.sapportals.portal.appintegrator.Utils.includeJSP(Utils.java:199)
 at com.sapportals.portal.appintegrator.layer.HTTPRenderLayer.render(HTTPRenderLayer.java:249)
 at com.sapportals.portal.appintegrator.LayerProcessor.processContentPass(LayerProcessor.java:226)
 at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:100)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
 at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
 at com.sapportals.portal.sapapplication.bwc.AbstractBWCComponent.doContent(AbstractBWCComponent.java:63)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
 at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
 at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
 at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
 at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
 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:156)
 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:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
 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:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: Error occurs during the compilation of java generated from the jsp
 at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:108)
 at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:140)
 at com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:291)
 at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:141)
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
 at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
 ... 46 more
Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error occurs during the rendering of jsp component
 at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2189)
 at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:81)
 ... 52 more

Why am i getting this error page and how to resolve this? Please help. Thanks.
Regards,

I am facing one more problem now. I tried to create a new user in Portal and when i try to login with this new account i get following error message:
Portal Runtime Error
An exception occurred while processing a request for :
iView : com.sap.portal.runtime.logon.default
Component Name : com.sap.portal.runtime.logon.default
Error occurs during the rendering of jsp component.
Exception id: 10:04_22/01/07_0010_6052850
See the details for the exception ID in the log file
Following is the error message snippet from the log file for this exception ID:

###Exception ID:10:04_22/01/07_0010_6052850
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
Component : com.sap.portal.runtime.logon.default
Component class : com.sapportals.portal.ume.component.logon.SAPMLogonComponent
User : J2EE_GUEST
 at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:444)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:527)
 at com.sapportals.portal.prt.component.AbstractComponentResponse.include(AbstractComponentResponse.java:89)
 at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:232)
 at com.sap.security.core.logonadmin.ComponentAccessToLogic.gotoPage(ComponentAccessToLogic.java:109)
 at com.sap.security.core.sapmimp.logon.SAPMLogonLogic.executeRequest(SAPMLogonLogic.java:251)
 at com.sapportals.portal.ume.component.logon.SAPMLogonComponent.doContent(SAPMLogonComponent.java:37)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
 at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
 at com.sapportals.portal.ume.component.logon.SAPMLogonCertComponent.doContent(SAPMLogonCertComponent.java:33)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
 at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
 at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
 at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
 at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
 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:156)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
 at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
 at com.sap.portal.navigation.Gateway.service(Gateway.java:101)
 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:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
 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:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: Error occurs during the compilation of java generated from the jsp
 at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:108)
 at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.run(JSPCompiler.java:140)
 at com.sapportals.portal.prt.core.broker.JSPComponentItem.compileJSP(JSPComponentItem.java:291)
 at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:141)
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
 at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:934)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
 ... 49 more
Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error occurs during the rendering of jsp component
 at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPParser.parse(JSPParser.java:2189)
 at com.sapportals.portal.prt.servlets_jsp.server.jsp.JSPCompiler.compile(JSPCompiler.java:81)
 ... 55 more
Though i am still able to login with any of my old accounts, but not with the newly created ones. I thought this might have been because of the new roles that i assigned, but i see the above error message even when i haven't assigned any role. How do i get rid of this one now?
Thanks and Regards,

Permanent solution for Java iView Runtime error ?

Hi
I have SAP IDES installed in my system...recently i am getting following error when i am trying to login Portal :
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 searched SDN many discussions say that restart server and check memory and...etc......etc
My system also if i restart server problem is solved temprarely....
My system memory is not a problem because i have 16GB Ram amd 1 Tera hard disk still i have 500 GB hard diskk free space...
If i restart simply MMC my J2ee table will not connected so i have to restart hole sytem them start MMC .....then server is up and i can connect to portal .......it seems connection for j2ee table are getting lost.....
Can some one suggest me permanent solution
thanks in advance

Hi Maya,
BEx Web Analyzer requires Portal and is basically a Web template called 0ANALYSIS_PATTERN.
Is Portal configured in your system landscape? If yes try to see if its configured probably using transaction RSPOR_CUST01.
If you have access to SM59, you can test the RFC connection to the portal by running the Test Connection for the corresponding RFC destination ID that you see in RSPOR_CUST01 transaction.
Assign points if helpful
Regards, Uday

Java Iview runtime error for WAD 7.0

Hi,
When I try to open Web Application designer of 7.0 from Start>Programs>Business explorer> Web application designer, the system is popping up to enter the userid &password after entering it , I cannot see any screen, when I asked my team member about this he told that the IT still did not release the 7.0 Web application designer and he told me to use 3.X Web application designer ,but when I try to open in rrmx my going to meu oprtion BEX Analyzer>Tools -->BEx web analyzer then its opening in the internet explorer and giving me the message
Java iView Runtime
An exception occured while processing your request.
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in connection
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:304)
     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:156)
     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:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.NullPointerException
     at com.sapportals.portal.prt.service.authenticationservice.AuthenticationService.getLoggedInUser(AuthenticationService.java:333)
     at com.sapportals.portal.prt.connection.UMHandler.handleUM(UMHandler.java:96)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:186)
     ... 20 more
If this situation persists, please contact your system administrator
What could be the Problem

Hi Maya,
BEx Web Analyzer requires Portal and is basically a Web template called 0ANALYSIS_PATTERN.
Is Portal configured in your system landscape? If yes try to see if its configured probably using transaction RSPOR_CUST01.
If you have access to SM59, you can test the RFC connection to the portal by running the Test Connection for the corresponding RFC destination ID that you see in RSPOR_CUST01 transaction.
Assign points if helpful
Regards, Uday

PCUI: Authorization for Links in Java iViews (Favorites)

Hello,
when I copy one of the roles delivered with CRM, modify and use it, there will be no hyperlinks shown in the so called 'Favorite' iViews (Java iViews) - e.g. 'My Favorites: Opportunities'.
When I add SAP_ALL to the test user hyperlinks will be shown.
Does anybody know which authorizations (RFC,...) I have to add in 'PFCG' to get hyperlinks working for Java iViews?
Thank you
Robert

Hello Gregor,
basically I did a trial'n'error approach. Added all roles and removed all roles via manual "BinarySearch" until I got a working role (-set). Mostly there are "*" entries in SAP standard roles for RFC calls.
Unfortunately I got your answer when I had already a working role. I agree, your way would be the correct way of minimizing number of autohorization entries in a role. Maybe I would have saved lots of time also...
Thank you so far.
Best regards
Robert

ISA iviews error in Channel Management Portal for partner portal

I am getting the following error while accessing any iview which uses the GenericISAComponent or GenericICSSComponent in the Partner Portal. I am using CRM 5.0 and SAP Portal 7.0 (2004s). What configuration needs to be done in order to make ISA iviews to work? If you have a link/document to configure ISA in the partner portal, please send me. I am using SAP provided business package for channel management. Any help is appreciated.
Errors displayed in the portal:
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/com.sap.pct/specialist/com.sap.pct.crm/com.sap.pct.crm.roles/com.sap.pct.crm.partnermanagercc/com.sap.pct.crm.chm.pmc.shop_management/com.sap.pct.crm.chm.isa.pmc.product_catalog
Component Name : com.sap.pct.crm.app.channelmgmt.GenericISAComponent
The exception was logged. Inform your system administrator..
Exception id: 06:45_07/08/07_0075_13177350
See the details for the exception ID in the log file
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/com.sap.pct/specialist/com.sap.pct.crm/com.sap.pct.crm.roles/com.sap.pct.crm.partnermanagercc/com.sap.pct.crm.chm.pma.service_center/com.sap.pct.crm.chm.isa.service
Component Name : com.sap.pct.crm.app.channelmgmt.GenericICSSComponent

I am still working on this one, but I think I ca help you a bit on the way.
Keywords: EP7, ISA CRM 5.0
When deploying BP for CRM in the portal the permissions on the component is set for the super_admin_role to be the owner.
If you check the super_admin_role and assigned action you will find the Action : AclSuperUser.
As a test you can assign this action, AclSuperUser, to the role you are using and it should work.
For production purposes I can not recommend to use AclSuperUser action to a normal user since this is very powerful action. I'm currentley investigation how to assign minimal permissions for the role I'm using to make the GenericICSSComponent work.
Best Regards
Jan-Erik Hov

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.

Urgent: Customize BP for Products Java iView

Hi,
We have implemented Business Package for Products 50.3.1 in EP 6.0.
I want to ewmove some buttons like create document and change materials in the Java iView provided in the Business Package.
I have no idea how this customization could be done?
Is there any configuration setting in the R/3 needs to be done?
Please share the documents if there is any for the customization.
Thanks and Best Regards,
Prashil

Hi Marko,
I don't know the BP, but this exception clearly states that within the method getPage within the class ListPortalComponent a CRMContextException is referenced (probably should be thrown), which in fact does not exist within the classpath.
If I would have the BP at hand (and you have, that's your advantage), just check if the class exists. If not, you could try a workaround and check the cause for the exception, if you achieve that it should not be thrown, the JVM won't complain...
Is the BP delivered within one or within several PAR's? If it takes several PAR's, maybe CRMContextException is in one, ListPortalComponent in another PAR and no SharingReference could be set (but I wouldn't call this very probable for the common package com/sap/pct/crm/generics; nevertheless, it's an idea).
Just try to analyze around this...
Hope it helps
Detlev
PS: You didn't mark your question as question?!

Java-iViews-Errors in BP for CRM

Similar Messages

Maybe you are looking for