Azure API Management developer portal runtime error
Hi,
I'm trying to use the Microsoft Azure API Management functionality just announced in the TechEd 2014 americas.
I was able to create my namespace for Azure API Management in the Azure Mgmt Portal.
But now, when I click on the Management Console or Developer Portal, I got a runtime error (ASP.Net Runtime Error).
I tried from a PC where I'm not authenticated in Azure and it works until I reach the login page, and then I got this Runtime Error again and again.
My subscription is a MSDN subscription.
Any ideas or workarounds here?
Hi,
The problem still exists but it appears only when I'm authenticated.
For example, I open the Windows Azure Management Portal with my admin account, goes to the API Management and click on the Management Console. I'm redirected to the https://middleway.portal.azure-api.net/admin URL and here I got a Runtime Error ASP.Net...
Strange no?
Similar Messages
-
Alert Mail configuration in Solution Manager 7.1 for Portal Runtime errors
Dear Friends,
We have EP7.01 SP5 installed on windows environment with Oracle DB. Also we have SAP EHP 1 for SAP Solution Manager 7.0.
Please help to provide steps to configure
proactive mail alert configuration ,
GRMG for High availability
Any portal runtime errors
for PORTAL services in Solution Manager.
Regards,
Venkat.Hello Venkat,
You will have to include the Portal system in the Central System administration of your Solution Manager.
As the EP system will be monitored by a sapccmsr running with -j2ee option this one can be configured separately. The agent will be started using the monitoring segment of the J2EE instance and therefore can be started more than once.
Here you should also use the latest sapccmsr agents.
The following link provides details on the required agents:
http://help.sap.com/saphelp_nw2004s/helpdata/en/ca/118110ff542640b7c86b570cc61ae3/frameset.htm
Please refer the below notes.
214247 RZ20: Questions on configuration of monitoring data
704349 Activating the CCMS monitoring for TREX 6.1 (NW2004
Note the EP system can only be monitored by using the SAPCCMSR agents. and then by implement a central autoreaction method you can generate e-mails from CCMS.
Automatic emails will get generated when certain thresholds are met. You must configure the thresholds from the central monitoring system for the nodes that you want email to be generated.
Please follow the steps in the note to configure central auto reaction.
429265 CCMS monitor architecture: Central auto-reaction
In the central monitoring system ( Solution Manager in your case ), Goto RZ20, choose the monitor for the nodes that you are monitoring. Select the node, click properties, & check the threshold values.
Also refer to the following notes:
547024 - Transfer the EP 5.0 Monitoring-Data to SAP CCMS
644783 -P 6.0 Monitoring via CCMS / SolMan
Also, check the following link that has information on portal monitoring :
http://service.sap.com/~sapidb/011000358700002004322004E
I guess this is a whole lot of information to assimilate and will be helpful to you to setup what you intend to.
Regards
Amit -
SUPM 2. 0 - Automated script management - Portal runtime error
Hi,
Whenever I click on "Automated Script Management" I receive this message:
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 11:14_15/06/11_0008_11133350
Refer to the log file for details about this exception.
When I look at the log history, I see 1 error: "No hierarchy maintained for object type".
What do I have to do to resolve the issue?
Thanks,
FrançoisHi..
Since you are getting an error of Hierarchy, you have to follow the following steps:
1. After specifying the Hierarchy name in SPRO, Login to SuPM and go to "Settings" tab and select the tab "Default Hierarchy"
2. Here, you have to select the Hierarchy which you want it to be used by SuPM application
3. Then, you have to go to "Application Properties" and select "Data Source Administration"
4. You have to Refresh All the Data Sources to reflect the changes.
Now, Try using the application, it will not throw you any error.
Hope it helps,
Regards,
Raghunandan GV -
Portal runtime error while creating rooms
Hi,
I installed collaboration and content management on my portal instance
and started basic configuration. Now while creating rooms , i get the
portal runtime error. I have enclosed the screen shot of the error.
I have enclosed the steps that can be followed to reproduce the error.
Portal Runtime Error
An exception occurred while processing a request for :
iView :
pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.content_administration/com.sap.portal.content_admin_ws/com.sap.netweaver.coll.colcontent/com.sap.netweaver.coll.RoomCreation/com.sap.netweaver.coll.RoomCreationWizard
Component Name : com.sap.netweaver.coll.appl.ui.room.RoomCreationWizard
The exception was logged. Inform your system administrator..
Exception id: 10:23_07/02/07_0037_818308650
See the details for the exception ID in the log fileHi Detlev,
Thanks a lot. I have enclosed the information from default trace.
<< item 0 : >>#1.5#00306E0AA058008600000060000044AC000428E704E99CFE#1170872586724#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#SAPOSS#13800##srv006_W81_818308650#SAPOSS#11f658b0b6d811db93c800306e0aa058#Thread[PRT-Async 3,5,PRT-Async]##0#0#Error#1#/System/Server#Java###Exception ID:10:23_07/02/07_0037_818308650
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.content_administration/com.sap.portal.content_admin_ws/com.sap.netweaver.coll.colcontent/com.sap.netweaver.coll.RoomCreation/com.sap.netweaver.coll.RoomCreationWizard
Component class : com.sap.ip.collaboration.roomui.api.rcwizard.RcWizardComponent
User : SAPOSS
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:377)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:390)
at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
at java.lang.Thread.run(Thread.java:534)
Caused by: com.sapportals.wdf.WdfError
at com.sapportals.wdf.WdfCompositeController.buildComposition(WdfCompositeController.java:678)
at com.sapportals.htmlb.AbstractCompositeComponent.preRender(AbstractCompositeComponent.java:33)
at com.sapportals.htmlb.Container.preRender(Container.java:118)
at com.sapportals.htmlb.Container.preRender(Container.java:118)
at com.sapportals.htmlb.Container.preRender(Container.java:118)
at com.sapportals.portal.htmlb.PrtContext.render(PrtContext.java:413)
at com.sapportals.htmlb.page.DynPage.doOutput(DynPage.java:237)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:129)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
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)
... 7 more
Manoj -
Portal Runtime Error when opening Webflow workitem in UWL
Hi,
I have recently configured the UWL to pick up workitems from SAP workflow on a background system. The workitems are appearing OK in the Task folder. However, when I try to open a workitem by double-clicking on it, I get the following error:
Portal Runtime Error
An Exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 05:33_30/09/10_0010_24209150
Refer to the log file for details about this exception.
NB. This only seems to happen for items that would be shown via the SAP GUI (E.g. a Confirming a task completion or user decision). The workitem runs OK if it is for a task that is visualised as a Web Dynpro app and specified in transaction SWFVISU.
I have not configured Delta Refresh options in the Workflow Administrator so do not know if this is a possible reason (I assumed that this would not cause a problem and would simply mean that refreshes only occur once every 60 seconds). Any help would be greatly appreciated. I am fairly new to Portal & UWL I would also be grateful if someone could tell where I can find the relevant log files referenced in the original error.
Regards
SimonHey Simon,
Welcome to UWL :). Portal Runtime Errors in UWL don't always signify that there is a UWL issue. This could be a permissions problem, etc. I'm not sure what version of the portal that you are using. But here is a little trick for you when checking logs...you can enter in the following: irj/servlet/prt/portal/prtroot/com.sap.portal.runtime.admin.logviewer.default
and check the log file with the id that was given in the error.
Exception ID: 05:33_30/09/10_0010_24209150 is your exception id. Search for the log files in the default trace and see what the exact error message is. If you can post this here it would be great.
The log files can be found in the following location:
/usr/sap/<SID>/JC<InstanceNumber>/j2ee/cluster/
server<number>/log
or by entering the URL that I mentioned above.
Please let me know in the next reply what the portal version is:
You can get this information by doing the following:
a. log on to the portal
b. backspace out the irj/portal section of the URL
c. click enter.
d. You are now at the J2EE administration page.
e. Next, click on the system information link
f. Please click on the all components link
g. Please attach this information to the message.
I am interested mostly in the UWLJWF component but if you can attach the full software component info to this post that would be great...
Please note, that note number 1133821 is an important note that is needed in the UWL. Did you maintain your RFC destination accordingly?
Here is some additional information to help you too since you are new to UWL:
[UWL Wiki|https://www.sdn.sap.com/irj/scn/wiki?path=/display/bpx/uwl+faq]
[UWL Forums|SAP Enterprise Portal: Application Integration;
[Business Task Management|http://help.sap.com/saphelp_nw70/helpdata/en/9e/ccf62fff3e4a45a634e592dabb45d5/frameset.htm]
[Using Universal Worklist|http://help.sap.com/saphelp_nw04s/helpdata/en/57/c223be82104792a15c2df11377b9ed/frameset.htm]
[JavaDocs UWL API|http://help.sap.com/javadocs/NW04S/current/uw/overview-summary.html]
I hope that you find this information useful!
Best Regards,
Beth Maben
EP - Senior Support Consultant
AGS Primary Support, Business Suite & Technology
Please see the UWL Wiki @
https://www.sdn.sap.com/irj/scn/wiki?path=/display/bpx/uwl+faq *** -
Hi,
I am a portal programmer beginner and i am triying to develop a portal component that retrieve information from sap r/3.
I get the next message when i use the iview:
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
com/sap/portal/services/api/connectorgateway/IConnectorGatewayService.
Exception id: 04:05_05/07/06_0005_8919850
See the details for the exception ID in the log file
My question is: where are located the log files in order to obtain more information about the error?
Best Regards
João FernandesHI,
you can see the error log from portal by browsing to
System Administration -> support -> portal runtime -> log viewer
copy paste the exception id against appropriate date and time in defaultTrace.x.trc and click search. you will get the details of log.
or
You can find the detailed error log in this path
D(installed drive):\usr\sap\J2E\JC00\j2ee\cluster\server0\log
arrange the log files according to date check in the latest log file for your portal logon id to find your error. -
Azure API Management Usage Pattern for Enterprise - Grouping APIs
Consider the following scenario:
I have a 100 people in one org with 4 divisions
I create on Azure API Management instance
All 100 people are developing APIs and adding them to this single API management instance
Can I achieve following? If yes, how?
I want to group the APIs by those 4 division. Allow access of APIs only if it is added by people in their division. When I say allow access, basically I mean search the APIs and call the APIs.You can achieve this by using "Groups". First, you need to have a group per division. You can either manually create the groups and add users to them or if you use Azure Active Directory and enable developers to login with AAD to the portal, then
their existing group membership will also be available to use.
Once you have the group set up you need to have a product for each group. You can set the visibility settings of the product so that only members of a given group can see it. Then you can set which APIs the product contains and thus complete the mapping
of groups to APIs. -
Portal runtime error while selecting page layout in WPC editor
Hello,
in web page composer, editing page, when i click on "select page layout" I have a portal runtime error popup.
The logfile shows the following :
#1.5 #005056834112005E0000000C00000FA800048E28A94966CC#1282205196819#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#1016#149##n/a##7ff9c93eab6811dfa9c70000003307de#SAPEngine_Application_Thread[impl:3]_15##0#0#Error##Java###10:06_19/08/10_0010_3344350
[EXCEPTION]
#1#com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error occurs during the rendering of jsp component
Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error in java compiling
Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: E:
usr
sap
EPD
JC00
j2ee
cluster
server0
apps
sap.com
irj
servlet_jsp
irj
root
WEB-INF
portal
portalapps
com.sap.netweaver.bc.util
lib
bc.util.public_api.jar(com/sapportals/wcm/WcmException.java):24: class WcmException is public, should be declared in a file named WcmException.java
(source unavailable)
1 error
I have the same by clicking on "check assignments"
Any help ?
ThanksHello Jego.
We faced the same issue after upgrade to EHP1 SP07 last week and managed to solve it by modification of layout.jsp and com.sap.nw.wpc.layoutmanager.LayoutBean within com.sap.nw.wpc.designtime.par. SAP's code requires an additional catch handler, so it is better to rise an OSS message.
As a workaround you may change a default layout for wpc main page (good for new pages) or manually edit output.xml for existing pages.
Best regards,
Aliaksandr Zhukau -
Got a Portal runtime error while using JSPDynepage
Hi,
Please help me out in the this error which I got when I tried to run the component developed based on JSPDynePage. I developed the component in the Developer Studio (version 2.0.4) in my local machine, built the project and deployed in the remote server using the option "Quick PAR Upload".
It says JSP file could not be found.
Thanks in advance
Sushma
<b>Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
Cannot find JSP file: JSPFileInfo :27242692 JSP File : D:\usr\sap\NPL\JC03\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\Bean_Test1\pagelet\BeanJsp.jsp Class Name: sapportalsjspBeanJsp Java File : D:\usr\sap\NPL\JC03\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\Bean_Test1\work\pagelet\_sapportalsjsp_BeanJsp.java Package Name : pagelet Class File : D:\usr\sap\NPL\JC03\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\Bean_Test1\work\pagelet\_sapportalsjsp_BeanJsp.class Is out dated : true.
Exception id: 01:45_03/11/04_0004_37482850
See the details for the exception ID in the log file</b>Hi,
I am also facing the same problem.
1) EP6 SP7
2) As mentioned in the error message there is no work directory in the mentioned path.
3) Please find beow portalapp.xml and log file.
<B>
<?xml version="1.0" encoding="utf-8"?>
<application>
<application-config>
<property name="SharingReference" value="com.sap.portal.htmlb"/>
</application-config>
<components>
<component name="default">
<component-config>
<property name="ClassName" value="Ex1"/>
<property name="SecurityZone" value="Ex1/low_safety"/>
</component-config>
<component-profile>
<property name="tagLib" value="/SERVICE/htmlb/taglib/htmlb.tld"/>
</component-profile>
</component>
</components>
<services/>
</application>
</B>
Exception:
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Resource
Component : Ex1.default
Component class : Ex1
User : Administrator
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.htmlb.page.JSPDynPage.doOutput(JSPDynPage.java:76)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:109)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
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:627)
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:232)
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:153)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:337)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:315)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:815)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:238)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
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:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:151)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: Cannot find JSP file: JSPFileInfo :16447115
JSP File : D:
usr
sap
P66
JC00
j2ee
cluster
server0
apps
sap.com
irj
servlet_jsp
irj
root
WEB-INF
portal
portalapps
Ex1
pagelet
Ex1.jsp
Class Name: sapportalsjspEx1
Java File : D:
usr
sap
P66
JC00
j2ee
cluster
server0
apps
sap.com
irj
servlet_jsp
irj
root
WEB-INF
portal
portalapps
Ex1
work
pagelet
_sapportalsjsp_Ex1.java
Package Name : pagelet
Class File : D:
usr
sap
P66
JC00
j2ee
cluster
server0
apps
sap.com
irj
servlet_jsp
irj
root
WEB-INF
portal
portalapps
Ex1
work
pagelet
_sapportalsjsp_Ex1.class
Is out dated : true
at com.sapportals.portal.prt.core.broker.JSPComponentItem.getComponentInstance(JSPComponentItem.java:96)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.service(PortalComponentItemFacade.java:355)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.service(PortalComponentItem.java:931)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:435)
... 38 more
#1.5#000C76EEC65400440000000F000001E80003E8A8BBC24BD7#1100236331418#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#99#####SAPEngine_Application_Thread[impl:3]_26##0#0#Info##Plain###UserAgentHook: component com.sap.portal.runtime.system.hooks.ErrorComponent supports (*, *, *) #
#1.5#000C76EEC654004400000010000001E80003E8A8BBC250B2#1100236331418#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#99#####SAPEngine_Application_Thread[impl:3]_26##0#0#Info##Plain###------PRT AbstractPortalComponent: calling doContent for portal component: com.sap.portal.runtime.system.hooks.ErrorComponent#
#1.5#000C76EEC654005B00000005000001E80003E8A8BC0E32CF#1100236336397#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#96#####SAPEngine_Application_Thread[impl:3]_2##0#0#Info##Plain###UserAgentHook: component com.sap.portal.runtime.admin.logviewer.default supports (*, *, *) #
#1.5#000C76EEC654004D0000000C000001E80003E8A8C46CFCDD#1100236476698#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#96#####SAPEngine_Application_Thread[impl:3]_0##0#0#Info##Plain###UserAgentHook: component com.sap.portal.runtime.admin.logviewer.default supports (*, *, *) # -
Portal Runtime Error - Access Denied
Hi Gurus,
I have developed a simple model using two BAPIs in the VC.
Once I save and deplay the model, I am getting a message 'Deployed Successfully'. But when i click on the Run <My model> link, i am not getting the Portal screen with the layout i have designed. I am getting an empty screen.
When i do a preview for my model in the portal, I get the following error:
" Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
Access denied (Object(s): portal_content/com.sap.gm.cnt/vcmodels/com.myComp.myProduct.2L.USER_LIST/com.myComp.myProduct.iviews/com.myComp.myProduct.2M.Userlist).
Exception id: 10:04_23/12/06_0005_83777250
See the details for the exception ID in the log file "
can somebody tell me what am i doing wrong? Or what should I do to correct this?
Regards,
Ravihi Ravi,
Check whether you have connected to a portal server. In the right hand top corner you get a small button to connect to portal server. If it says it have deployed successfully then in the contentadmin->portalcontent->visualcomposer folder you can see your iView created there.
Regards,
Gopi -
Portal Runtime Error : Any ideas?
Hello There,
Please help. I'm having a 'Portal Runtime Error' and would appreciate any lead: This is appearing in the MSS overview Page..
Portal Runtime Error
An exception occurred while processing your request
Exception id: 10:37_27/03/08_0005_7368050
See the details for the exception ID in the log file.
Here's what i cld get from the log file: Notice the exception id in bold.
Thanks.
#1.5 #001CC4D8C23E005F000000370000145000044968C5923ABE#1206614246811#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#MANAGER1#102##LBBEPDEV_EPD_7368050#MANAGER1#a6d16470fbe711dcc1bd001cc4d8c23e#SAPEngine_Application_Threadimpl:3_24##0#0#Error#1#/System/Server#Java###Exception ID:10:37_27/03/08_0005_7368050
EXCEPTION
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.roles/com.sap.pct.erp.mss.manager_self_service/com.sap.pct.erp.mss.manager/overview/com.sap.pct.erp.mss.work_overview/com.sap.pct.erp.mss.workoverview/com.sap.pct.erp.common.key_figure_monitor
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : MANAGER1
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
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:645)
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:524)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
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: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESIDURL_ENCODE>?sap-ep-iviewhandle=007<ESIDHASH>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.AccessibilitySAP_BOOL>&sap-rtl=<LAF.RightToLeftSAP_BOOL>&sap-ep-version=<Portal.VersionURL_ENCODE>&<ProducerInfo>&sap-explanation=<User.ExplanationSAP_BOOL>&<StylesheetIntegrationIF_true PROCESS_RECURSIVE>&<Authentication>&<DynamicParameterPROCESS_RECURSIVE>&<ForwardParametersQUERYSTRING>&<ApplicationParameterPROCESS_RECURSIVE>&\#39;; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System: &\#39;SAP_LocalSystem&\#39;,
Attribute: &\#39;client&\#39;.
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
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)
... 29 more
#1.5 #001CC4D8C23E005F000000390000145000044968C5924083#1206614246811#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#MANAGER1#102##LBBEPDEV_EPD_7368050#MANAGER1#a6d16470fbe711dcc1bd001cc4d8c23e#SAPEngine_Application_Threadimpl:3_24##0#0#Error##Java###10:37_27/03/08_0005_7368050
EXCEPTION
#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template &\#39;<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESIDURL_ENCODE>?sap-ep-iviewhandle=007<ESIDHASH>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.AccessibilitySAP_BOOL>&sap-rtl=<LAF.RightToLeftSAP_BOOL>&sap-ep-version=<Portal.VersionURL_ENCODE>&<ProducerInfo>&sap-explanation=<User.ExplanationSAP_BOOL>&<StylesheetIntegrationIF_true PROCESS_RECURSIVE>&<Authentication>&<DynamicParameterPROCESS_RECURSIVE>&<ForwardParametersQUERYSTRING>&<ApplicationParameterPROCESS_RECURSIVE>&\#39;; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System: &\#39;SAP_LocalSystem&\#39;,
Attribute: &\#39;client&\#39;.
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
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:645)
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:524)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
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)Looks like the issue is related to the system that is referencing the ERP System. Check if the connection tests of the system is passing.
Verify the hostname and ports of the R3 System. Also check the system referencing the Netweaver Application Server.
Also check if SSO is working fine.
Regards,
Abhishek -
Portal Runtime Error : in CRM BP iview
Hi
I installed Business package for crm in portal and assigned the role sales manager to an user xyz and when I go to analytics -> incentives and commissions -> My Teams Commisions-> the first iview "Closed Deals by Sales Office/Rep" shows the error
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/com.sap.portal.migrated/ep_5.0/roles/com.sap.pct.crm.SalesManager/Analysis_2/IncentivesCommissions/MyTeam/com.sap.pct.crm.salesmgrlistdeals
Component Name : com.sap.pct.crm.salesmgrlistdeals.default
The exception was logged. Inform your system administrator..
Exception id: date/........
See the details for the exception ID in the log file
and when i referred the log file, it shows the following trace.
pcd:portal_content/com.sap.portal.migrated/ep_5.0/roles/com.sap.pct.crm.SalesManager/Analysis_2/IncentivesCommissions/MyTeam/com.sap.pct.crm.salesmgrlistdeals
Component class : com.sap.pct.crm.incentivescommissions.salesmgrdeals.SalesMgrDealsDyn
user: xyz
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
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: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:154)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:392)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
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:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Caused by: java.lang.NullPointerException
at java.text.StringCharacterIterator.<init>(StringCharacterIterator.java:58)
at java.text.StringCharacterIterator.<init>(StringCharacterIterator.java:47)
at sun.text.Normalizer.setText(Normalizer.java:1537)
at java.text.CollationElementIterator.setText(CollationElementIterator.java:469)
at java.text.RuleBasedCollator.compare(RuleBasedCollator.java:401)
at java.text.Collator.equals(Collator.java:322)
at com.sap.pct.crm.incentivescommissions.salesmgrdeals.SalesMgrDealsCreation.createTableView(SalesMgrDealsCreation.java:383)
at com.sap.pct.crm.incentivescommissions.salesmgrdeals.SalesMgrDealsCreation.createReport(SalesMgrDealsCreation.java:159)
at com.sap.pct.crm.incentivescommissions.salesmgrdeals.SalesMgrDealsDynPage.retrieveData(SalesMgrDealsDynPage.java:182)
at com.sap.pct.crm.incentivescommissions.salesmgrdeals.SalesMgrDealsDynPage.doProcessBeforeOutput(SalesMgrDealsDynPage.java:167)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:123)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
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)
... 29 more
AFAIK i could see the null pointer exception, but donno the reason, as it is standard iview by SAP. did someone face this problem. if so, could you please lemme know how did u resolve it
or any other suggestions seeing the error??
Thank youhi
sorry for the delay..yep i configured it already with BW system with alias SAP_BW, ofcourse i dont have any crm data loaded in bw.
what i expect to see is a form giving a criteria for searching (for ex: startdate and enddate). but i see this error there.
any suggestions -
Portal Runtime Error in Performance Overview
Hi Experts ,
I am getting portal runtime error while accessing performance overview and this error is occurring in test system not in prod. I have only passed our custom parameter in "ViewGroup" and "ViewID" , which comes under property Editor of Performance Overview Iview.
Please find the server log :-
#0002A58CD85E00460000018900000C240004A6BED67C6350#1309238479307#com.sap.portal.prt.request#sap.com/irj#com.sap.portal.prt.request#sudad59#121793##n/a##6903e340a14611e09ecb0002a58cd85e#Thread[PRT-Async 2,5,PRT-Async]##0#0#Error#1#/System/Server#Java###Exception in PortalRequestManager.dispatchRequest without timeout
[EXCEPTION]
#1#java.lang.NoSuchMethodError: com.sap.pct.hcm.objectanddataprovider.CFTableViewModel.getClickableObjects()Lcom/sap/pct/hcm/objectanddataprovider/proxyclasses/Hrwpc_S_KeyobjecTypeList;
at com.sap.pct.hcm.teamviewer.TeamViewerPage.getJSArrayOfObjects(TeamViewerPage.java:1005)
at com.sap.pct.hcm.teamviewer.TeamViewerPage.getJSCodeOnLoad(TeamViewerPage.java:1031)
at com.sap.pct.hcm.teamviewer.TeamViewerPage.getJavaScriptCode(TeamViewerPage.java:839)
at com.sap.pct.hcm.teamviewer.TeamViewerPage.doProcessBeforeOutput(TeamViewerPage.java:512)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:123)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
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.component.CachablePortalComponent.service(CachablePortalComponent.java:273)
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.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:375)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:388)
at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
at java.lang.Thread.run(Thread.java:
Let me know if you need any further information.
Any help will be really appreciated with points.
-Regards
AK
Edited by: Khamari_alok on Jun 30, 2011 10:32 AM
Edited by: Khamari_alok on Jun 30, 2011 12:42 PMthere is an issue with the object and data provider evaluation path ie OADP
Please check using standard
Other mySAP.com components>Business Packages / Functional
Packages>Manager Self-Service>Object and Data Provider>Restrict Nuber
of Navigation Objects.
https://wiki.sdn.sap.com/wiki/display/ERPHCM
/DifferentfeaturesofOADPbasedonECC+6.0
You can debug in backend using FM HRWPC_GET_OBJECTS_FROM_ROOTS -
I am trying to access the UWL from Home -> Work -> UWL.
However, for non administrators, this gives a Portal Runtime error.
Portal Runtime Error
An exception occurred while processing your request
Exception id: 01:57_27/02/08_0051_11774250
See the details for the exception ID in the log file.
I knw most probably this error is due to missing permissions, but i have set the permissions for the End User Content folder.
I have also tried assigning permissions for the entire Portal Content folder with End user permissions, however, this does not work.
Any suggestions?
This is verrrry urgent.
Regards,
Preksha.Hi,
Thanks for the reply..
I managed by assigning permission for the iview
pcd:portal_content/every_user/general/uwl/com.sap.netweaver.bc.uwl.uwlSapWebDynproLaunch
Its working now.
Regards,
Preksha -
Portal runtime error. in PAR application
Hello Gurus,
i developed my own portal application for change portal password.
I used the follow blog for made it:
A Change Password Application
I compiled (without errors) and deploied application on my portal and i created a new iview based on my PAR file but when i try to launch preview i have follow error:
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 11:43_24/06/10_0007_7875550
Refer to the log file for details about this exception.
have you any idea?
in Log monitor i don't find any interesting suggestion
Alexok Thanks!!!
now work correctly!
But i have a problem:
When i press the botton for confirm the change pwd, the browser don't refresh target browser but open a new one session.
i think the broblem is in this instruction:
window.top.location.href="/irj/servlet..........."
any suggestion?
Thanks in advance
Alex
Maybe you are looking for
-
ITunes Library search won't find song actually in library
i have the problem with iTunes 7.5 it won't find some of the songs in my library when i search them. i can see them in the library, but when i type a word from artist or album it won's show anything. any ideas? also, why doesn't the album cover chang
-
Hi All, I am new to xml. I need to develop a xml parser in C which would parse an xml file of the format given below. <?xml version="1.0" encoding="utf-8"?> <fw version="FW 0.0.05"> <commandgroup name="ControlCommands"> <command name="1">start(0,1)</
-
I have been Happy with my IMac, and with the Leopard, but as soon as Apple Released, the Lion, I Was a Complete Stupid and downloaded, My Computer seems to be another one, maybe a 10 years old computer, and a Fool One, first when I turn On, come to l
-
How to print the PLD document in A5*2 paper size?
Dear All, I am trying to print the pld Document in A5*2 paper size. Is it possible in SAP B1 PLD? please help me. Thanks & Regards, Mahendra
-
Table extension not being saved
Hi, I have implemented Table extension at item level for SC and from the config perspective all looks fine. 1) Created Append struture with required fields First step: appending the field to the correct structure in SE11 or via transaction SPRO. Stru