- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- Error Bex webapplication designer with saving repo...
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Error Bex webapplication designer with saving reports
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 10-15-2008 1:00 PM
Dear all,
At a customer I am having an issue with an error message which is comming up when changing a report in the Bex web application designer (7.10).
Some history:
A functional consultant changes a report but in the first place gets an error message: 'java-communication error: error when opening an RFC connection'
When he clicks this away with OK he will come into his designer screen. Here he opens a webreport and when he changes and save it it won't show up with the new change but still with the old. When he saves it under a new name and than shows it on his screen after another RFC java message error he gets te right output. When he deletes the old one with the wrong value again he gets the java rfc error and than it is gone. But not true, after saving the content to the 'old' name again it gives the rfc error and when we display that one it shows the content of the one we had deleted before.
Anyone any idea?
below it the last lines of the default.trc file on the OS (where usernames have been changed to *)
I read the notes in this trace file but they only tell to sent the message to SAP
#
#1.#001708D132BA006B000000500000129700045946E323197F#1224061005151#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#******#50
341##sapbwp00.cs_PB1_1682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Se
rver#Java###Exception ID:10:56_15/10/08_0004_1682850
[EXCEPTION]
#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: PortalRuntimeException
at com.sapportals.portal.prt.core.PortalRequestManager.handleRequestException(PortalRequestManager.java:921)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:803)
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(ApplicationSessionMessag
eListener.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: java.lang.OutOfMemoryError
#
#1.#001708D132BA006B000000520000129700045946E3232916#1224061005156#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###com.sapportals.portal.prt
.runtime.PortalRuntimeException: Exception in connection#
#1.#001708D132BA006B000000530000129700045946E3232BBB#1224061005157#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at com.sapportals.po
rtal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:304)#
#1.#001708D132BA006B000000540000129700045946E3232C22#1224061005157#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at com.sapportals.po
rtal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)#
#1.#001708D132BA006B000000550000129700045946E3232C67#1224061005157#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at java.security.Acc
essController.doPrivileged(Native Method)#
#1.#001708D132BA006B000000560000129700045946E3232CAB#1224061005157#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at com.sapportals.po
rtal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)#
#1.#001708D132BA006B000000570000129700045946E3232CF0#1224061005157#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at javax.servlet.htt
p.HttpServlet.service(HttpServlet.java:853)#
#1.#001708D132BA006B000000580000129700045946E3232D34#1224061005157#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at com.sap.engine.se
rvices.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)#
#1.#001708D132BA006B000000590000129700045946E3232D79#1224061005157#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at javax.servlet.htt
p.HttpServlet.service(HttpServlet.java:853)#
#1.#001708D132BA006B0000005A0000129700045946E3232DDB#1224061005157#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at com.sap.engine.se
rvices.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)#
#1.#001708D132BA006B0000005B0000129700045946E3232E21#1224061005157#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at com.sap.engine.se
rvices.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)#
#1.#001708D132BA006B0000005C0000129700045946E3232E67#1224061005158#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at com.sap.engine.se
rvices.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)#
#1.#001708D132BA006B0000005D0000129700045946E3232EAB#1224061005158#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at com.sap.engine.se
rvices.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)#
#1.#001708D132BA006B0000005E0000129700045946E3232EF1#1224061005158#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at com.sap.engine.se
rvices.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)#
#1.#001708D132BA006B0000005F0000129700045946E3232F56#1224061005158#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at com.sap.engine.se
rvices.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)#
#1.#001708D132BA006B000000600000129700045946E3232F9B#1224061005158#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at com.sap.engine.se
rvices.httpserver.server.Client.handle(Client.java:95)#
#1.#001708D132BA006B000000610000129700045946E3232FE2#1224061005158#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at com.sap.engine.se
rvices.httpserver.server.Processor.request(Processor.java:175)#
#1.#001708D132BA006B000000620000129700045946E3233026#1224061005158#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at com.sap.engine.co
re.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)#
#1.#001708D132BA006B000000630000129700045946E323306E#1224061005158#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at com.sap.engine.co
re.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)#
#1.#001708D132BA006B000000640000129700045946E32330B5#1224061005158#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at com.sap.engine.co
re.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.#001708D132BA006B000000650000129700045946E3233118#1224061005158#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at java.security.Acc
essController.doPrivileged(Native Method)#
#1.#001708D132BA006B000000660000129700045946E323315B#1224061005158#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at com.sap.engine.co
re.thread.impl3.SingleThread.execute(SingleThread.java:102)#
#1.#001708D132BA006B000000670000129700045946E32331AE#1224061005158#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at com.sap.engine.co
re.thread.impl3.SingleThread.run(SingleThread.java:172)#
#1.#001708D132BA006B000000680000129700045946E3233551#1224061005159#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###Caused by: com.sapportals
.portal.prt.runtime.PortalRuntimeException: PortalRuntimeException#
#1.#001708D132BA006B000000690000129700045946E323359C#1224061005159#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### at com.sapportals.po
rtal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:284)#
#1.#001708D132BA006B0000006A0000129700045946E3233602#1224061005159#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain### ... 20 more#
#1.#001708D132BA006B0000006B0000129700045946E323364B#1224061005160#System.err#sap.com/irj#System.err#******#50341##sapbwp00.cs_PB1_1
682850#******#1b077b709a9611dda793001708d132ba#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###Caused by: java.lang.OutO
fMemoryError#
#1.#001708D132BA00710000004A00001297000459474B9E63CF#1224062758366#com.sap.ip.bi.webapplications.runtime.impl.Page#sap.com/irj#com.s
ap.ip.bi.webapplications.runtime.impl.Page#*****#50552##sapbwp00.cs_PB1_1682850#*****#09fd33609a9b11ddbad4001708d132ba#SAPEngine_A
pplication_Thread[impl:3]_30##0#0#Fatal#1#/Applications/BI#Plain###Exception caught: java.lang.NullPointerException
java.lang.NullPointerException
#
#1.#001708D132BA00710000004C00001297000459474B9ECCAC#1224062758392#com.sap.ip.bi.webapplications.runtime.impl.Page#sap.com/irj#com.s
ap.ip.bi.webapplications.runtime.impl.Page#*****#50552##sapbwp00.cs_PB1_1682850#*****#09fd33609a9b11ddbad4001708d132ba#SAPEngine_A
pplication_Thread[impl:3]_30##0#0#Fatal#1#/Applications/BI#Plain###Error while ending a BI application; see SAP Notes 937697 and 948
490#
#1.#001708D132BA006B0000006C00001297000459474DC03D0F#1224062794134#com.sap.ip.bi.webapplications.runtime.impl.Page#sap.com/irj#com.s
ap.ip.bi.webapplications.runtime.impl.Page#*****#50341##sapbwp00.cs_PB1_1682850#*****#1b077b709a9611dda793001708d132ba#SAPEngine_A
pplication_Thread[impl:3]_39##0#0#Fatal#1#/Applications/BI#Plain###Exception caught: java.lang.NullPointerException
java.lang.NullPointerException
#
#1.#001708D132BA006B0000006E00001297000459474DC03FB1#1224062794135#com.sap.ip.bi.webapplications.runtime.impl.Page#sap.com/irj#com.s
ap.ip.bi.webapplications.runtime.impl.Page#*****#50341##sapbwp00.cs_PB1_1682850#*****#1b077b709a9611dda793001708d132ba#SAPEngine_A
pplication_Thread[impl:3]_39##0#0#Fatal#1#/Applications/BI#Plain###Error while ending a BI application; see SAP Notes 937697 and 948
490#
#1.#001708D132BA00680000003D0000129700045947A3970F25#1224064234120#com.sap.ip.bi.webapplications.runtime.impl.Page#sap.com/irj#com.s
ap.ip.bi.webapplications.runtime.impl.Page#******#50411##n/a##b61320809a9e11ddb9f7001708d132ba#SAPEngine_Application_Thread[impl:3]_
20##0#0#Fatal#1#/Applications/BI#Plain###Exception caught: java.lang.NullPointerException
java.lang.NullPointerException
#
#1.#001708D132BA00680000003F0000129700045947A3972837#1224064234127#com.sap.ip.bi.webapplications.runtime.impl.Page#sap.com/irj#com.s
ap.ip.bi.webapplications.runtime.impl.Page#******#50411##n/a##b61320809a9e11ddb9f7001708d132ba#SAPEngine_Application_Thread[impl:3]_
20##0#0#Fatal#1#/Applications/BI#Plain###Error while ending a BI application; see SAP Notes 937697 and 948490#
#1.#001708D132BA00770000005500001297000459482B7F5937#1224066514127#com.sap.ip.bi.webapplications.runtime.impl.Page#sap.com/irj#com.s
ap.ip.bi.webapplications.runtime.impl.Page#******#50614##n/a##051095f09aa411ddb415001708d132ba#SAPEngine_Application_Thread[impl:3]_
15##0#0#Fatal#1#/Applications/BI#Plain###Exception caught: java.lang.NullPointerException
java.lang.NullPointerException
#
#1.#001708D132BA00770000005700001297000459482B7F6E1E#1224066514133#com.sap.ip.bi.webapplications.runtime.impl.Page#sap.com/irj#com.s
ap.ip.bi.webapplications.runtime.impl.Page#******#50614##n/a##051095f09aa411ddb415001708d132ba#SAPEngine_Application_Thread[impl:3]_
15##0#0#Fatal#1#/Applications/BI#Plain###Error while ending a BI application; see SAP Notes 937697 and 948490#
#1.#001708D132BA00690000005E000012970004594840F59960#1224066874122#com.sap.ip.bi.webapplications.runtime.impl.Page#sap.com/irj#com.s
ap.ip.bi.webapplications.runtime.impl.Page#******#50601##n/a##dba376a09aa411dda996001708d132ba#SAPEngine_Application_Thread[impl:3]_
34##0#0#Fatal#1#/Applications/BI#Plain###Exception caught: java.lang.NullPointerException
java.lang.NullPointerException
#
#1.#001708D132BA006900000060000012970004594840F59DB6#1224066874123#com.sap.ip.bi.webapplications.runtime.impl.Page#sap.com/irj#com.s
ap.ip.bi.webapplications.runtime.impl.Page#******#50601##n/a##dba376a09aa411dda996001708d132ba#SAPEngine_Application_Thread[impl:3]_
34##0#0#Fatal#1#/Applications/BI#Plain###Error while ending a BI application; see SAP Notes 937697 and 948490#
- SAP Managed Tags:
- BW Business Explorer (SAP BEx)
Accepted Solutions (0)
Answers (2)
Answers (2)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
solved by completely deinstalling it and onsite SAP support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Bults,
Usually this issue occurs when the log for the Java Server gets filled and the RFC crashes - check the RFC connection to the Java System and also see if the logs are filled - if the logs are filled - you will need to clear the logs...
Arun
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello Arun,
I cannot find what you ment with the log being filled with RFC crashes.
If you mean that it should be in dev_rd there is nothing on RFC crashes.
I also tried to trace via rstt on the user, but found no trace at all.
Also some notes on to set traces for SAP seem a bit strange as per note 888687 via the Visual Admin you can set some traces in the log configurator, but when I check that I see no options as described in the note.
- Crystal Reports text clipping issue. PDF created by Business Obj on Red Hat Enterprise Linux (RHEL) in Technology Q&A
- Crystal Reports Server - Restful API & Parameters in Technology Q&A
- Generate Custom Legal Certificates in SAP DRC in Technology Blogs by SAP
- Command line options for Crystal in Technology Q&A
- Crystal Reports 2020 for Eclipse - Java - Custom paper size for Zebra Label Printer in Technology Q&A
| User | Count |
|---|---|
| 90 | |
| 10 | |
| 10 | |
| 10 | |
| 7 | |
| 7 | |
| 6 | |
| 5 | |
| 4 | |
| 3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.