Runtime error 104

My former manager created a helpfile using Adobe Robohelp for
HTML 7. The helpfile is now off being tested on XP and Vista, and
on a handful of pages (out of hundreds), runtime error message 104
is displayed.
Line: 104
Error: Expected ')'
Yes/No.
If you click No then the help page is displayed successfully,
however I'd like to get rid of this bug. Looking in Robohelp, I get
the same error, so am assuming it is a bug generated by Robohelp...
I'm a bit new to all this, so apologies if I'm appearing stupid -
any ideas how I go about resolving it?
Many thanks, Mike

Thanks guys!
I've had a look at the pages and didn't see anything that
separated these pages from any others - but it would be fair to say
I don't really know what I am looking for.
It definitely isnt due to double clicking, so I think we can
eliminate that.
I'm going to try and regenerate the primary layout on my
machine to see if the problem was caused by something on my former
manager's machine. If it doesn't, I found a utility on the web
called regcure which I can download and it claims to fix runtime
errors. I'd need the IT guys to run it in Administrator mode tho.
Worth a try? Any other suggestions?
Mike

Similar Messages

DAC-104/JBO-110 Runtime Error.

What does the following runtime error mean (how can I fix the
problem?)?
DAC-104: ImmediateAccess setAttribute failed. ColumnView:
LNAME
JBO-110: Cannot update Read only attribute.
I get this error when trying to update a row using
Infoswing-based components.
NOTE: The code worked a moment ago, but I must have messed
something up! Any ideas?
Thanks,
Matt
null

Matt,
I'm not sure what went wrong. Is this repeatable? Were you the
only one accessing the database at that time?
FYI: You can assign different levels of locking for the
SessionInfo control (via the Inspector). You can have optimistic,
pessimistic or no locking at all.
Regards,
Matt Larson (guest) wrote:
: What does the following runtime error mean (how can I fix the
: problem?)?
: DAC-104: ImmediateAccess setAttribute failed. ColumnView:
: LNAME
: JBO-110: Cannot update Read only attribute.
: I get this error when trying to update a row using
: Infoswing-based components.
: NOTE: The code worked a moment ago, but I must have messed
: something up! Any ideas?
: Thanks,
: Matt
null

Runtime Error in Portal Application

Can any body help me in resolving the following runtime error in portal application, (Netweaver Version : 7.0)
Full Message Text
03:21_21/09/11_0002_6275851
[EXCEPTION]
java.lang.NoClassDefFoundError: org.apache.commons.httpclient.methods.RequestEntity
at java.lang.J9VMInternals.verifyImpl(Native Method)
at java.lang.J9VMInternals.verify(J9VMInternals.java:69)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:131)
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:152)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:271)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)
at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:387)
at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:488)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:607)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:540)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:423)
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:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
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(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: java.lang.ClassNotFoundException: org.apache.commons.httpclient.methods.RequestEntity
Found in negative cache

Hi,
this exception seems caused by a missing interface org.apache.commons.httpclient.methods.RequestEntity. Please the following ones:
http://www.jarfinder.com/index.php/java/info/org.apache.commons.httpclient.methods.RequestEntity
Br,
Javier

Portal Runtime Error while accessing BW reports through portal

Hi,
We are facing portal runtime error(An exception occurred while processing your request. Please send the exception id to your portal administrator) while accessing BI reports through portal frequently.
We are unable to trace the error in the 'default trace' log file and although refreshing the cache solves this issue, it is difficult to explain this to every user individually.
After many such errors, We found one log entry, which we are now not yet sure if it is relevant. The error states:
1.
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname><BWLauncherComponent[PORTAL_URL]>;jsessionid=<Request.JSessionID>?sap-ext-sid=<ID[url_ENCODE]>&Language=<Request.Language>&theme=<LAF.Theme[url_ENCODE]>&sap-lafversions=<LAF.AllVersions[url_ENCODE]>&<Authentication>&<Report>&<BusinessParameters>'; the problem occured at position 230. Cannot process expression <LAF.AllVersions>
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
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:540)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:423)
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:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Content pass of Application Integrator failed.
Component Name:       'com.sap.portal.appintegrator.sap.BWReport',
Context Name (iView): <iview name location>
Top Layer:            'BWReport/TopLayer',
Producer ID (FPN):    'null',
System Alias:         'Sap_bw',
2.
The cluster server element 111111 is not added in the EP cluster context,
   because prtbridge on 111111 is stopped or not yet started (maybe the server is starting or shuting down).
Please suggest us if the above logs are related to the issue or not
Kindly provide us any inputs or solutions.

Hi All,
We are also having similiar type of error in our portal.
com.sap.engine.services.prtbridge##com.sap.engine.services.prtbridge
#######SAPEngine_System_Thread[impl:5]_13##0#0#Error#1#/System/Server#Plain###
The cluster server element 125898350 is not added in the EP cluster context,
   because prtbridge on 125898350 is stopped or not yet started
(maybe the server is starting or shuting down).
We have implemented the FPN using RRA.
This error comes only for few users when they navigate in Portal. After clearing the cache, it works for all. Kindly help us to resolve this issue.
Regards,
Venkatesh

Portal runtime error while accessing BI Report as URL iView

Hi All,
I created an URL Iview with the URL of BI report, when i am trying to access it then getting portal runtime error.
I had check the log it is showing the following details about the error, could you please help me out what is the root cause based on the log details...??
Thanks in advance.
Logfile Details
1) 08:48_14/09/10_0049_139354050*
*[EXCEPTION]*
*com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.ConnectionString>'; the problem occured at position 0. Cannot process expression <System.ConnectionString> because Invalid System Attribute:*
*System:    &#39;SAP_LocalSystem&#39;,*
*Attribute: &#39;ConnectionString&#39;.*
*at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)*
*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:235)*
*at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:541)*
*at java.security.AccessController.doPrivileged(AccessController.java:246)*
*at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)*
*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:386)*
*at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)*
*at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)*
*at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)*
*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(AccessController.java:219)*
*at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)*
*at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
2) Full Message Text*
*Content pass of Application Integrator failed.*
*Component Name:       'com.sap.portal.appintegrator.sap.Transaction',*
*Context Name (iView): 'pcd:portal_content/net.ea.epson.BI_ROLES/com.epson.financeuser/ZB(3a)FINANCE_USER/com.Epson.UnitandGrossProfit',*
*Top Layer:            'Transaction/DragAndRelateLayer',*
*Producer ID (FPN):    'null',*
*System Alias:         'BIDCLNT100',
Thanks,
Kalki Reddy.

Hi Avadh,
Thanks for your reply.
I tested thru connection test of the system , it was tested successflly without any issues. all are into tick mark only.
but when i am trying to use the system alias name while creating Trasaction iview also i am not able to get the system alias name in the dropdown for selecting the system alias.
but system alias what ever it is "BIDCLNT100" is in active and connection test is done correctly without any issues.
Please let me know the problem why i am not able to get the same system alias name "BIDCLNT100" not able to get in the drop down list while creating the transaction IView??
Please reply , Thanks in advance
Thanks,
Kalki Reddy

Portal runtime error while trying to run a MSS report

Hello gurus!!
   I setup the MSS reports launchpad and now I am seeing all the list of reports on the reports launchpad. I am able to click on all the links and each link opens up the relevant page and the selection criteria also comes up. However, on the last screen, I get a portal runtime error after I click on the report result button.
The trace file shows the following errors:
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[./log/defaultTrace.trc]/>
<!PATTERN[defaultTrace.trc]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!FILESET[17, 20, 10485760]/>
<!PREVIOUSFILE[defaultTrace.16.trc]/>
<!NEXTFILE[defaultTrace.18.trc]/>
<!LOGHEADER[END]/>
#1.5 #0050568444360067000005D2000005D400049F27DC8DD843#1300893459438#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#sap.com/tcwddispwda#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#SSUBBARAO#113523##n/a##ae3b7a53556011e0cd95000000191d7e#SAPEngine_Application_Thread[impl:3]_23##0#0#Fatal#1#/Applications/Xss#Java###null
[EXCEPTION]
#1#com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
     at com.sap.xss.hr.cat.record.blc.RfcManager.rfcExecute(RfcManager.java:453)
     at com.sap.xss.hr.cat.record.blc.RfcManager.init(RfcManager.java:820)
     at com.sap.xss.hr.cat.record.blc.wdp.InternalRfcManager.init(InternalRfcManager.java:280)
     at com.sap.xss.hr.cat.record.blc.FcCatRecordInterface.onInit(FcCatRecordInterface.java:353)
     at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface.onInit(InternalFcCatRecordInterface.java:268)
     at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface$External.onInit(InternalFcCatRecordInterface.java:542)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
     at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendar.onInit(VcCatCalendar.java:251)
     at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendar.onInit(InternalVcCatCalendar.java:194)
     at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendarInterface.onInit(VcCatCalendarInterface.java:162)
     at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface.onInit(InternalVcCatCalendarInterface.java:146)
     at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface$External.onInit(InternalVcCatCalendarInterface.java:222)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1346)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
     at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:595)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:867)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     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:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     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:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Exception condition "PROFILE_NOT_INITIALIZED" raised., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
     at com.sap.xss.hr.cat.general.model.slim.CatsModelSlim.hrxss_Cat_Wd_Record(CatsModelSlim.java:245)
     at com.sap.xss.hr.cat.general.model.slim.Hrxss_Cat_Wd_Record_Input.doExecute(Hrxss_Cat_Wd_Record_Input.java:137)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
     ... 64 more
Could anybody please guide me how to fix this error and get the reports working properly?
Any help with this is much appreciated.
Thank you!
~Maria Kutty~

Hi,
Please refer to note 878440.
Thanks
Prashant

ABAP Runtime Error : STRING_LENGTH_TOO_LARGE In Solution Manager 7.0

Hi All,
In SolMan 7.0 when i am using T-code Solution_Manager->Business process Monitoring tab System is give as give below ABAP DUMP . Please Share your idea to resolve this issue.
Runtime Errors                                                       STRING_LENGTH_TOO_LARGE
Except.                                                       CX_SY_RANGE_OUT_OF_BOUNDS
Date and Time                                                       24.11.2009                    12:16:08
     Short text
               Illegal access to a string (length too large)
     What happened?
               Error in the ABAP Application Program
               The current ABAP program "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP" had to be
                terminated because it has
               come across a statement that unfortunately cannot be executed.
     What can you do?
               Note down which actions and inputs caused the error.
               To process the problem further, contact you SAP system
               administrator.
               Using Transaction ST22 for ABAP Dump Analysis, you can look
               at and manage termination messages, and you can also
               keep them for a long time.
     Error analysis
               An exception occurred that is explained in detail below.
               The exception, which is assigned to class 'CX_SY_RANGE_OUT_OF_BOUNDS', was not
                caught in
               procedure "IF_HTTP_EXTENSION~HANDLE_REQUEST" "(METHOD)", nor was it propagated
                by a RAISING clause.
               Since the caller of the procedure could not have anticipated that the
               exception would occur, the current program is terminated.
               The reason for the exception is:
               In the running program "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP", part of a string was
                about to be accessed
               with an explicitly specified length.
               However, this length (8) exceeded the current length of the string
               (5).
               This kind of access is illegal.
     How to correct the error
               Reduce the length with which to access the string.
               If the error occurred in your own ABAP program or in an SAP
               program you modified, try to remove the error.
               If the error occures in a non-modified SAP program, you may be able to
               find an interim solution in an SAP Note.
               If you have access to SAP Notes, carry out a search with the following
               keywords:
               "STRING_LENGTH_TOO_LARGE" "CX_SY_RANGE_OUT_OF_BOUNDS"
               "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP" or "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CM004"
               "IF_HTTP_EXTENSION~HANDLE_REQUEST"
               If you cannot solve the problem yourself and want to send an error
               notification to SAP, include the following information:
               1. The description of the current problem (short dump)
                  To save the description, choose "System->List->Save->Local File
               (Unconverted)".
               2. Corresponding system log
                  Display the system log by calling transaction SM21.
                  Restrict the time interval to 10 minutes before and five minutes
               after the short dump. Then choose "System->List->Save->Local File
               (Unconverted)".
               3. If the problem occurs in a problem of your own or a modified SAP
               program: The source code of the program
                  In the editor, choose "Utilities->More
               Utilities->Upload/Download->Download".
               4. Details about the conditions under which the error occurred or which
               actions and input led to the error.
               The exception must either be prevented, caught within proedure
               "IF_HTTP_EXTENSION~HANDLE_REQUEST" "(METHOD)", or its possible occurrence must
                be declared in the
               RAISING clause of the procedure.
               To prevent the exception, note the following:
     System environment
               SAP-Release 701
               Application server... ".........."
               Network address...... ""
               Operating system..... "Windows NT"
               Release.............. "5.2"
               Hardware type........ "8x AMD64 Level"
               Character length.... 16 Bits
               Pointer length....... 64 Bits
               Work process number.. 0
               Shortdump setting.... "full"
               Database server... "................."
               Database type..... "ORACLE"
               Database name..... "SM7"
               Database user ID.. "SAPSR3"
               Terminal.......... ".............."
               Char.set.... "C"
               SAP kernel....... 701
               created (date)... "Oct 12 2008 23:34:32"
               create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
               Database version. "OCI_10201_SHARE (10.2.0.2.0) "
               Patch level. 15
               Patch text.. " "
               Database............. "ORACLE 9.2.0.*.*, ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*"
               SAP database version. 701
               Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
                NT 6.0"
               Memory consumption
               Roll.... 16192
               EM...... 4189840
               Heap.... 0
               Page.... 0
               MM Used. 1513920
               MM Free. 2673296
     User and Transaction
               Client.............. 100
               User................ 182836
               Language Key........ "E"
               Transaction......... " "
               Transactions ID..... "09C5D8DE506DF14DB42D001E682F27BB"
               Program............. "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP"
               Screen.............. "SAPMHTTP 0010"
               Screen Line......... 2
               Information on Caller ofr "HTTP" Connection:
               Plug-in Type.......... "HTTP"
               Caller IP............. "10.226.33.101"
               Caller Port........... 8080
               Universal Resource Id. "/sap/bc/solman/defaultUser/graphic/solmangraphic.htm"
     Information on where terminated
               Termination occurred in the ABAP program "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP" -
                in "IF_HTTP_EXTENSION~HANDLE_REQUEST".
               The main program was "SAPMHTTP ".
               In the source code you have the termination point in line 130
               of the (Include) program "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CM004".
               The termination is caused because exception "CX_SY_RANGE_OUT_OF_BOUNDS"
                occurred in
               procedure "IF_HTTP_EXTENSION~HANDLE_REQUEST" "(METHOD)", but it was neither
                handled locally nor declared
               in the RAISING clause of its signature.
               The procedure is in program "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP "; its source
                code begins in line
               6 of the (Include program "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CM004 ".
     Source Code Extract
     Line               SourceCde
       100               *     url of its for WebGUI links (extension for portal cfs)
       101                     WHEN 'its'.
       102                       lv_its = ls_param_fields-value.
       103               *     name of transaction for WebGUI links (extension for portal cfs)
       104                     WHEN 'trans'.
       105                       lv_trans = ls_param_fields-value.
       106               *     name of transaction parameter for WebGUI links
       107               *     (extension for portal cfs)
       108                     WHEN 'trans_keyname'.
       109                       lv_trans_keyname = ls_param_fields-value.
       110               *     info block
       111                     WHEN gc_parameter_name-io.
       112                       lv_io = ls_param_fields-value.
       113               *     portal base url
       114                     WHEN gc_parameter_name-base_url.
       115                       lv_base_url = ls_param_fields-value.
       116
       117               * Note 834787-- Headers of Infoblocks are not translated in Fact sheet
       118               * display set the language
       119                     WHEN 'sap-language'.
       120                       try.
       121                           set locale language ls_param_fields-value.
       122                         catch CX_SY_LOCALIZATION_ERROR.
       123               * No language with this code is installed.
       124               * use the default one
       125                           SET LOCALE LANGUAGE SPACE.
       126                       endtry.
       127
       128                     WHEN OTHERS.
       129               *       additional types for selection
     >>>>>                       IF ls_param_fields-name(8) EQ 'sel-type'.
       131                         CLEAR ls_sel_param.
       132                         MOVE ls_param_fields-value TO ls_sel_param-name.
       133                         lv_num = ls_param_fields-name+8(*).
       134                         CLEAR lv_key.
       135                         CONCATENATE 'sel-value'
       136                                     lv_num
       137                                INTO lv_key.
       138                         READ TABLE lt_param_fields WITH KEY name = lv_key
       139                              INTO ls_param_fields.
       140                         IF sy-subrc = 0.
       141                           MOVE ls_param_fields-value TO ls_sel_param-value.
       142                         ENDIF.
       143                         APPEND ls_sel_param TO lt_sel_param.
       144                       ENDIF.
       145                   ENDCASE.
       146                 ENDLOOP.
       147
       148               * HTML error message if no business partner
       149                 IF bp IS INITIAL.
     Contents of system fields
     Name                         Val.
     SY-SUBRC                         0
     SY-INDEX                         1
     SY-TABIX                         3
     SY-DBCNT                         1
     SY-FDPOS                         17
     SY-LSIND                         0
     SY-PAGNO                         0
     SY-LINNO                         1
     SY-COLNO                         1
     SY-PFKEY
     SY-UCOMM
     SY-TITLE                         HTTP Control
     SY-MSGTY
     SY-MSGID
     SY-MSGNO                         000
     SY-MSGV1
     SY-MSGV2
     SY-MSGV3
     SY-MSGV4
     SY-MODNO                         0
     SY-DATUM                         20091124
     SY-UZEIT                         121608
     SY-XPROG
     SY-XFORM
     Active Calls/Events
     No.               Ty.                              Program                                                            Include                                   Line
                    Name
         4               METHOD                              CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP                                                            CL_CRM_CCKPT_CFS_SERVICE_HTTP=CM004                                     130
                    CL_CRM_CCKPT_CFS_SERVICE_HTTP=>IF_HTTP_EXTENSION~HANDLE_REQUEST
         3               METHOD                              CL_HTTP_SERVER================CP                                                            CL_HTTP_SERVER================CM00G                                     574
                    CL_HTTP_SERVER=>EXECUTE_REQUEST
         2               FUNCTION                              SAPLHTTP_RUNTIME                                                            LHTTP_RUNTIMEU02                                     942
                    HTTP_DISPATCH_REQUEST
         1               MODULE (PBO)                              SAPMHTTP                                                            SAPMHTTP                                      13
                    %_HTTP_START
     Chosen variables
     Name
               Val.
     No.                   4                    Ty.                         METHOD
     Name               CL_CRM_CCKPT_CFS_SERVICE_HTTP=>IF_HTTP_EXTENSION~HANDLE_REQUEST
     SERVER
               {O:2*\CLASS=CL_HTTP_SERVER_NET}
             F0000000
             D0002000
     LS_PARAM_FIELDS-NAME
               _appl
             56776
             F100C
             00000
             00000
     SY-REPID
               CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP
             4454545444555445554554445455534522222222
             3CF32DF33B04F363F3526935F8440D3000000000
             0000000000000000000000000000000000000000
             0000000000000000000000000000000000000000
     SPACE
             2
             0
             0
             0
     GC_PARAMETER_NAME-BASE_URL
               ep_base_url
             67566765776
             50F2135F52C
             00000000000
             00000000000
Regards
Suresh
Edited by: Suresh Kumar on Nov 24, 2009 3:21 PM

Hi Naveen,
Please find given below BBPCRM & SAP_BW version..
BBPCRM     500     0013     SAPKU50013     BBPCRM     BBP/CRM Supp. Pack.
SAP_BW     701     0003     SAPKW70103     SAP Business Warehouse     Component Supp. Pkg.
This problem is not only with Bussiness process tab (T-Code: Solution_manage) also System monitoring Still i searching solution for this But once we are restarting System that time this problem is not occuring but after some time system is giving this DUMP
Regards,
Suresh

Runtime error in Universal Worklist in portal

Hi!
An error occurs when I open the page Universal Worklist -
Administration under System Administration > System Configuration >
Universal Worklist & Workflow. The error message is:
Portal runtime error.
An exception occurred while processing your request. Send the exception
ID to your portal administrator.
Exception ID: 09:44_02/10/08_0004_221082950
Refer to the log file for details about this exception.
This error is also displayed when opening the page Portal Eventing,
Portal Navigation under System Administration > Support > Web Dynpro
Test Tools > Application Integrator Tests.
The portal UME is configured with ADS as data source and we are using
the dataSourceConfiguration_ads_readonly_db_with_krb5.xml configuration
file. Single Sign-On using SAP logon tickets with user mapping to
reference system is also implemented.
Users have different users IDs in the SAP System than in the portal,
and scenario 2 from SAP Help "Single Sign-On to SAP Systems"
(http://help.sap.com/saphelp_nw04/helpdata/en/4d/dd9b9ce80311d5995500508b6b8b11/frameset.htm) is implemented
"Scenario 2: Single Sign-On using SAP logon tickets with user mapping."
The problem occurred after changing the UME with ADS and implemented
Single Sign-on.
Error messages from log:
Date : 10/03/2008
Time : 10:08:56:057
Message : Content pass of Application Integrator failed.
Component Name:       com.sap.portal.appintegrator.sap.WebDynpro,
Context Name (iView): pcd:portal_content/every_user/general/uwl/com.sap.netweaver.bc.uwl.uwlSapWebDynproLaunch,
Top Layer:            WebDynpro/TopLayer,
Producer ID (FPN):    null,
System Alias:         SAP_LocalSystem,
[EXCEPTION]
com.sapportals.portal.appintegrator.ApplicationIntegratorException: ApplicationIntegratorException
     at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:104)
     at com.sapportals.portal.appintegrator.accessor.system.SAP_LocalSystemAccessor.getAuthenticationData(SAP_LocalSystemAccessor.java:91)
     at com.sapportals.portal.appintegrator.layer.authenticationmethod.AbstractAuthenticationMethod.getUserCredentials(AbstractAuthenticationMethod.java:54)
     at com.sapportals.portal.appintegrator.layer.authenticationmethod.SAPLogonTicket.computeAuthentication(SAPLogonTicket.java:31)
     at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:45)
     at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:159)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
     at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
     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:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     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:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.security.api.umap.NoLogonDataAvailableException: (No text available)
     at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:329)
     at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:99)
     ... 33 more
Severity : Error
Category : /System/Server
Location : com.sap.portal.sapapplication
Application : sap.com/irj
Thread : SAPEngine_Application_Thread[impl:3]_18
Datasource : 1223021485930:N:\usr\sap\DPN\JC32\j2ee\cluster\server0\log\defaultTrace.trc
Message ID : 00145ED7E6460061000007830000B6B800045854D84A3E79
Source Name : com.sap.portal.sapapplication
Argument Objs : com.sapportals.portal.appintegrator.ApplicationIntegratorException: ApplicationIntegratorException
     at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:104)
     at com.sapportals.portal.appintegrator.accessor.system.SAP_LocalSystemAccessor.getAuthenticationData(SAP_LocalSystemAccessor.java:91)
     at com.sapportals.portal.appintegrator.layer.authenticationmethod.AbstractAuthenticationMethod.getUserCredentials(AbstractAuthenticationMethod.java:54)
     at com.sapportals.portal.appintegrator.layer.authenticationmethod.SAPLogonTicket.computeAuthentication(SAPLogonTicket.java:31)
     at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:45)
     at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:159)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
     at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
     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:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     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:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.security.api.umap.NoLogonDataAvailableException: (No text available)
     at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:329)
     at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:99)
     ... 33 more
Arguments : com.sapportals.portal.appintegrator.ApplicationIntegratorException: ApplicationIntegratorException
     at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:104)
     at com.sapportals.portal.appintegrator.accessor.system.SAP_LocalSystemAccessor.getAuthenticationData(SAP_LocalSystemAccessor.java:91)
     at com.sapportals.portal.appintegrator.layer.authenticationmethod.AbstractAuthenticationMethod.getUserCredentials(AbstractAuthenticationMethod.java:54)
     at com.sapportals.portal.appintegrator.layer.authenticationmethod.SAPLogonTicket.computeAuthentication(SAPLogonTicket.java:31)
     at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:45)
     at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:159)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
     at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
     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:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     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:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.security.api.umap.NoLogonDataAvailableException: (No text available)
     at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:329)
     at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:99)
     ... 33 more
Dsr Component : n/a
Dsr Transaction : f52708e0912011ddb1e200145ed7e646
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives : /System/Server
Resource Bundlename :
Session : 32121
Source : com.sap.portal.sapapplication
ThreadObject : SAPEngine_Application_Thread[impl:3]_18
Transaction :
User : Asle.Gaarder
Date : 10/03/2008
Time : 10:08:56:026
Message : Cannot provide backend user ID and password for user "Asle Gaarder" (unique ID: "USER.CORP_LDAP.asle.gaarder") for system "SAP_ECC_REFERENCE" because these credentials could not be found in the user mapping data.
Severity : Info
Category :
Location : com.sap.security.core.umap.imp.UserMappingDataImp.enrich(Properties)
Application : sap.com/irj
Thread : SAPEngine_Application_Thread[impl:3]_18
Datasource : 1223021485930:N:\usr\sap\DPN\JC32\j2ee\cluster\server0\log\defaultTrace.trc
Message ID : 00145ED7E6460061000007820000B6B800045854D849CB92
Source Name : com.sap.security.core.umap.imp.UserMappingDataImp
Argument Objs : "Asle Gaarder" (unique ID: "USER.CORP_LDAP.asle.gaarder"),"SAP_ECC_REFERENCE",
Arguments : "Asle Gaarder" (unique ID: "USER.CORP_LDAP.asle.gaarder"),"SAP_ECC_REFERENCE",
Dsr Component : n/a
Dsr Transaction : f52708e0912011ddb1e200145ed7e646
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives :
Resource Bundlename :
Session : 32121
Source : com.sap.security.core.umap.imp.UserMappingDataImp
ThreadObject : SAPEngine_Application_Thread[impl:3]_18
Transaction :
User : Asle.Gaarder

Hi,
Check the logon type for systems SAP_LocalSystem and SAP_ECC_REFERENCE which must be set to SAPLOGONTICKET not UIDPWD.
It basically fails since the password doesn't exist for the mapping, as it is only dependent on trust.
There was a change in a recent SP which added an extra check in this area.
Dagfinn

Portal runtime error in MSS

In MSS portal -->Work Overview --> Key Figure Monitor section displays Portal runtime error as follows.
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 03:45_24/10/11_0126_6285950
Refer to the log file for details about this exception.
When I Traced the Log file I got the trace as follows
03:28_24/10/11_0125_6285950
[EXCEPTION]
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&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.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<FPNInfo[IF_false PROCESS_RECURSIVE]>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; 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:125)
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:545)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:434)
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:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
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(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
I am new to MSS Portal. Can anyone help me figure out the cause of this error.

Hi,
I am also facing the same issue .Getting runtime Erorr (Whilce Click on MSS--Budget/Projects/recruitment/team..etc...
Is this related to backend Configuraiton issue or Portal installtion error
Portal runtime error
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID 05:48_09/06/12_0165_22331150
See log file for details about this exception
we have installed the below BP's on (Netweaver 7.3 and backend EHP5)
BP_ERP5COM    1.51
BP_ERP5ESS    1.41
BP_ERP5MSS    1.51
BPERPESSWDA   1.50
SAP_ESS       633
SAP_MSS       630
SAPPCUI_GP    633
Please adivce..
thanks
Matt

KM runtime error in sap portal7.0

Hi Experts,
We are getting a runtime error in portal for all KM related screens like KM Content,Postal favorites not able to open any KM repository.Please find the below error log and let me know what can be done for this.
I have understood that utils class is missing but how to resolved this issue,.Please suggest
0}#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.km.AdminContent/com.sap.km.AdminContentExplorer/com.sap.km.AdminExplorer
Component class : com.sapportals.wcm.portal.component.base.ControllerComponent
User : Administrator
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:235)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:557)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:430)
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:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: java.lang.NoClassDefFoundError: com/sapportals/wcm/control/util/ExceptionUtil
at com.sapportals.wcm.portal.component.base.ControllerComponent.handleException(ControllerComponent.java:312)
at com.sapportals.wcm.portal.component.base.ControllerComponent.doContent(ControllerComponent.java:102)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:210)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:115)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
... 27 more

Hi Anusha
Could you refer the SAP Notes
1324531 - Portal Runtime Exception when delegating meeting
1223296 - System hangs during some WPC actions
BR
SS

Runtime Error - DBIF_RSQL_INVALID_RSQL - Too many OPEN CURSOR

When I try to train a Decision Tree Model via an APD process in RSANWB, I get a runtime error when my model is configured with too many parameter fields or too many leaves (with 2 leaves it works, with more it fails).
By searching SAP Notes I see that there are many references to this kind of runtime errors. But no note on occurences of it in RSANWB / RSDMWB .
Any information on this anyone?
Claudio Ciardelli
Runtime Errors         DBIF_RSQL_INVALID_RSQL
Date and Time          29.07.2005 16:19:21
|ShrtText                                                                                |
|    Error in RSQL module of database interface.                                                   |
|What happened?                                                                                |
|    Error in ABAP application program.                                                            |
|                                                                                |
|    The current ABAP program "SAPLRS_DME_DECISION_TREE_PRED" had to be terminated                 |
|     because one of the                                                                           |
|    statements could not be executed.                                                             |
|                                                                                |
|    This is probably due to an error in the ABAP program.                                         |
|                                                                                |
|Error analysis                                                                                |
|    The system attempted to open a cursor for a SELECT or OPEN CURSOR                             |
|    statement but all 16 cursors were already in use.                                             |
|    The statement that failed accesses table "/BIC/0CDT000030 ".                                  |
|    The erroneous statement accesses table "/BIC/0CDT000030 ".                                    |
|Trigger Location of Runtime Error                                                                 |
|    Program                                 SAPLRS_DME_DECISION_TREE_PRED                         |
|    Include                                 LRS_DME_DECISION_TREE_PREDU06                         |
|    Row                                     103                                                   |
|    Module type                             (FUNCTION)                                            |
|    Module Name                             RS_DME_DTP_EVALUATE                                   |
|Source Code Extract                                                                               |
|Line |SourceCde                                                                                |
|   73|* Prepare for Data evaluation                                                               |
|   74| CATCH SYSTEM-EXCEPTIONS OTHERS = 15.                                                      |
|   75|    CREATE DATA ref TYPE (i_enum_dbtab).                                                    |
|   76|    ASSIGN ref->* TO <fs_wkarea>.                                                           |
|   77|    ASSIGN COMPONENT gv_class_dbposit OF STRUCTURE                                          |
|   78|                      <fs_wkarea> TO <fs_class>.                                            |
|   79|    CREATE DATA ref TYPE TABLE OF (i_enum_dbtab).                                           |
|   80|    ASSIGN ref->* TO <ft_data>.                                                             |
|   81|                                                                                |
|   82| ENDCATCH.                                                                                |
|   83| IF sy-subrc = 15.                                                                         |
|   84|*   Error on Assignment.                                                                    |
|   85|    CALL FUNCTION 'RS_DME_COM_ADDMSG_NOLOG'                                                 |
|   86|      EXPORTING                                                                             |
|   87|        i_type    = 'E'                                                                     |
|   88|        i_msgno   = 301                                                                     |
|   89|        i_msgv1   = 'EVALUATION_PHASE'                                                      |
|   90|      IMPORTING                                                                             |
|   91|        es_return = ls_return.                                                              |
|   92|    APPEND ls_return TO e_t_return.                                                         |
|   93|    EXIT.                                                                                |
|   94| ENDIF.                                                                                |
|   95|                                                                                |
|   96|* For the un-trained Rec-Ids, evaluate.....                                                 |
|   97| REFRESH lt_recinp.                                                                        |
|   98| APPEND LINES OF i_t_records TO lt_recinp.                                                 |
|   99| SORT lt_recinp .                                                                          |
| 100|* Open Cursor..                                                                             |
| 101| DATA: l_curs TYPE cursor.                                                                 |
| 102| DATA: l_psize TYPE i VALUE 10000.                                                         |
|>>>>>| OPEN CURSOR WITH HOLD l_curs FOR                                                          |
| 104|   SELECT * FROM (i_enum_dbtab)                                                             |
| 105|     WHERE rsdmdt_recid NOT IN                                                              |
| 106|        ( SELECT rsdmdt_recid FROM                                                          |
| 107|             (i_learn_tab) ).                                                               |
| 108|                                                                                |
| 109|* Start Fetch...                                                                           |
| 110| DO.                                                                                |
| 111|    FETCH NEXT CURSOR l_curs                                                                |
| 112|      INTO CORRESPONDING FIELDS OF TABLE <ft_data>                                          |
| 113|      PACKAGE SIZE l_psize.                                                                 |
| 114|    IF sy-subrc NE space.                                                                   |
| 115|      EXIT.                                                                                |
| 116|    ENDIF.                                                                                |
| 117|                                                                                |
| 118|*     Process records...                                                                    |
| 119|    LOOP AT <ft_data> ASSIGNING <fs_wkarea>.                                                |
| 120|                                                                                |
| 121|*     Call Prediction Function.                                                             |
| 122|      CALL FUNCTION 'RS_DME_DTP_PREDICT_STRUCTURE'                                          |

Hi Claudio,
well the message is very clear and I think in your case you need to split your model into a few somehow equal models, each not having more than 2 leaves.
Another option might be to do more things serially instead of parallel.
Hope it helps
regards
Siggi

Runtime Error in Web Page Composer (WPC) : Page Editor

Hello,
We are using the Web page Composer to design our portal homepage. The portal version is 7.02 SP6.
We created a site, some site content like banners and articles, and a blank web page. When we try to add the site content to the web page from the "Page Editor" by clicking on the pencil icon -> "Add", a runtime error occurs on the Web Content Browser pop up page. The drag and drop feature to add content is not working either.
The error message is as follows:
Runtime Error
An exception occured while processing the request.
Additional information: null
Exception ID = 0076b5e1-fea6-2e10-b49e-9e1f27bd085c
Runtime Error
An exception occured while processing the request.
Additional information: null
Exception ID = 30ebb5e1-fea6-2e10-7d8e-b34b3229cd35
ANy idea what the problem could be?
Thanks and Regards,
Reena

Hello,
Below is an extract from the trace file for the exception ID:
Exception ID = 60843375-7baa-2e10-2097-c764acd6ad4c java.lang.NullPointerException
at com.sapportals.wcm.portal.component.base.ControllerComponent.prepareRequest(ControllerComponent.java:229)
at com.sapportals.wcm.portal.component.base.ControllerComponent.getPage(ControllerComponent.java:124)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:114)
at com.sapportals.wcm.portal.component.base.ControllerComponent.doContent(ControllerComponent.java:83)
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:545)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:434)
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:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
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(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Any clue?
Regards,
Reena

Transaction Code F.50 Runtime Error

Dear Friends,
While executing T.code F.50, I am getting the following Error
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Exceptn                CX_SY_OPEN_SQL_DB
Date and Time          25.06.2009 11:27:31
ShrtText
The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
Error in ABAP application program.
The current ABAP program "SAPLF049" had to be terminated because one of the
     statements could not be executed.
This is probably due to an error in the ABAP program.
Error analysis
An exception occurred. This exception is dealt with in more detail below
     . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
      neither
caught nor passed along using a RAISING clause, in the procedure
      "SICHERN_IN_DB" "(FORM)"
Since the caller of the procedure could not have expected this exception
      to occur, the running program was terminated.
     The reason for the exception is:
     If you use an ABAP/4 Open SQL array insert to insert a record in
     the database and that record already exists with the same key,
     this results in a termination.
      (With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
Program                                 SAPLF049
Include                                 LF049F00
Row                                     74
Module type                             (FORM)
Module Name                             SICHERN_IN_DB
gger Location of Exception
Program                                 SAPLF049
Include                                 LF049F00
Row                                     86
Module type                             (FORM)
Module Name                             SICHERN_IN_DB
rce Code Extract
e SourceCde
56 *      Insert von RF048 aus CRF048 (bei Commit Work)                   *
57 *----
58 FORM RELATION_SAVE.
59
60   CHECK NOT CRF048[] IS INITIAL.
61   INSERT RF048 FROM TABLE CRF048.
62   REFRESH CRF048.
63
64 ENDFORM.                    "RELATION_SAVE
65
66
67
68 *eject
69 *----
70 *      Form SICHERN_IN_DB                                             *
71 *----
72 *      Masseninsert/update aus Z-Tabellen                              *
73 *----
74 FORM SICHERN_IN_DB.
75
76 * Lokale Daten
77 DATA:
78       ld_xnetb   TYPE xnetb,
79       anz_belnr TYPE i.
80
81 *------ Aufteilungstabellen -
82
83 * Einfügen                                                             *
84
85 * BFIT_A0
>>>   INSERT BFIT_A0 FROM TABLE ZBFIT_A0.
87   IF SY-SUBRC <> 0.
88     MESSAGE A153.
89   ENDIF.
90
91 * BFIT_A
92   INSERT BFIT_A FROM TABLE ZBFIT_A.
93   IF SY-SUBRC <> 0.
94     MESSAGE A154.
95   ENDIF.
96
97 * BFOD_A
98   INSERT BFOD_A FROM TABLE ZBFOD_A.
99   IF SY-SUBRC <> 0.
100     MESSAGE A155.
101   ENDIF.
102
103 * BFOD_AB
104   INSERT BFOD_AB FROM TABLE ZBFOD_AB.
105   IF SY-SUBRC <> 0.
How to reslove the error? Please advise.
Thanks and Regards
Sridhar

Hi,
Well it looks quite difficult to understand.......The only thing it says clearly that this is happening because of duplicate Primary Key insertion.

Runtime error Dynpro_not_found

Hi experts,
I get the following runtime error when trying to open a Z table under SM30.
Short text
     Dynpro does not exist
Error analysis
    The system attempted to use dynpro 0100 in program "SAPLZGET_ORG".
    This dynpro does not exist.
User and Transaction
Client.............. 100
    User................ "ARUN"
    Language key........ "E"
    Transaction......... "SM30 "
    Transactions ID..... "4976D21BC7F841F0E1000000C0A80046"
Program............. "SAPLZGET_ORG"
    Screen.............. " "
    Screen line......... 0
Line SourceCde
97             i_messnbr = '288'.
   98           ELSE.                        "customer system
   99             i_messnbr = '289'.
100           ENDIF.
101         ENDIF.
102         MESSAGE ID 'AM' TYPE 'I' NUMBER i_messnbr
103                         WITH vim_addr_basetable
104                              vim_addr_bastab_field
105                              vim_tsadrv-tablename
106                              vim_tsadrv-fieldname.
107         CLEAR x_header-adrnbrflag. MODIFY x_header INDEX 1.
108       ELSE.                            "entry in TSADRV is complete
109         vim_addr_group = vim_tsadrv-addr_group.
110         IF x_header-adrnbrflag EQ 'O'.
111           CALL FUNCTION 'ADDR_GET_STATUS_INFO'
112             TABLES
113               status_table = i_statetab.
114           READ TABLE i_statetab WITH KEY
115                constant = vim_tsadrv-addr_group.
116           IF sy-subrc NE 0. CLEAR i_statetab-value. ENDIF.
117           TRANSLATE i_statetab-value USING ' OXN'.
118           x_header-adrnbrflag = i_statetab-value.
119           MODIFY x_header INDEX 1.
120         ENDIF.
121       ENDIF.
122     ENDIF.
123   ENDIF.
124   PERFORM vim_process_assigns.
125   IF <status>-initializd EQ space.     "not processed yet
126 * reset dropdown lists
>>>     CALL FUNCTION 'VRM_REFRESH_VALUES'.
128     IF x_header-frm_af_ini NE space.   "user exit exists AND
129 * set environment for user exit.
130       ASSIGN dba_sellist-sys TO <vim_sellist>.
131       vim_enqueue_range = x_header-subsetflag. assigned = 'X'.
132 * perform user exit -> 3.0B processed in JUSTIFY_ACTION_MODE
133       PERFORM (x_header-frm_af_ini) IN PROGRAM (sy-repid).
134     ENDIF.
135 * backup DBA_SELLIST
136 *    REFRESH vim_dba_sel_kept.                        "UF210200b
137 *    APPEND LINES OF dba_sellist TO vim_dba_sel_kept.
138 * remove multiple values for subsets
139     DELETE dba_sellist WHERE ddic = 'M'.
140     DESCRIBE TABLE dba_sellist.
141     IF sy-tfill GT 0.
142       READ TABLE dba_sellist INDEX sy-tfill.
143       CLEAR dba_sellist-and_or.
144       MODIFY dba_sellist INDEX sy-tabix.
145     ENDIF.                                                  "UF210200e
146   ENDIF.
Please kindly help me out with the issue.
Thank You.

Hi,
What is the screen number given when you created the maitenence generator? Over here it seems it is trying to open the table in sm30 using screen 0100.
Try to recreate the table maintenence generator. Delete the existing maintenence generator and when screen number is there select propose screen number so the system suggests the screen number.
Then try to maintain entries via sm30.
Hope this helps.
Regards,
Sachin

Portal runtime error exception ID: error in init method

Hi Experts
I am getting the portal runtime error http://<fqdn>:<port>/irj/portal, can anybody suggest me what to do.
"Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 02:27_06/09/10_68650050"
Here is the log file
02:27_06/09/10_68650050
[EXCEPTION]
com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.netweaver.coll.appl.ui.room.CollaborationDetailedNavigation
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:271)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)
at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:387)
at com.sapportals.portal.pb.PageBuilder.createIviewProfile(PageBuilder.java:443)
at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:233)
at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:635)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:815)
at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:703)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:235)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:523)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:412)
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:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.navigation.CollaborationNavTree of Portal Component com.sap.netweaver.coll.appl.ui.room.CollaborationDetailedNavigation because: Could not instantiate implementation class
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:269)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
... 35 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.netweaver.coll.appl.ui.room
at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
at com.sapportals.portal.prt.core.broker.PortalApplicationItem._refresh(PortalApplicationItem.java:507)
at com.sapportals.portal.prt.core.broker.PortalApplicationItem.getCoreLoader(PortalApplicationItem.java:1360)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getClassLoader(PortalComponentItem.java:569)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getClassLoader(PortalComponentItemFacade.java:102)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
... 39 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [PortalApplicationItem._prepare]: com.sap.netweaver.bc.rf.service
at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:427)
at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
... 44 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during start of application: SAPJ2EE::library:signature_lib
at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:323)
at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:387)
... 45 more
Caused by: com.sapportals.portal.prt.core.broker.SAPJ2EELibraryNotFoundException: Could not find Library SAPJ2EE::library:signature_lib
at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:277)
... 46 more. . .
Thanks in advance
Uday

Hi Tobias
Thanks for your response, i can able to access /nwa. The trace file while is posted got from /nwa.
I have restarted the portal. Can you please tell me where can we check the errors when portal started?
Thanks in advance
Uday

Runtime error 104

Similar Messages

Maybe you are looking for