The RFC iview error

Hi everyone, I want to created an iview with type of SAP RFC iview ,but after I Choose Function,I get the "Portal Runtime Error",
I can serch the function,but the next step I get the error:
Portal Runtime Error
An exception occurred while processing a request for :
iView : com.sap.portal.applications.enterprise.iviews.wizard.default
Component Name : com.sap.portal.applications.enterprise.iviews.wizard.default
com.sapportals.connector.metadata.structures.IStructureValue.
Exception id: 05:11_17/05/07_0043_8171850
See the details for the exception ID in the log file
the log:
#1.5#001125C0B174006A000002390013006C000430A5ACA4648B#1179388031023#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#HAN-CUIZHAO#8477##LGEDEV_LED_8171850#HAN-CUIZHAO#beb3d5e0044a11dc8b25001125c0b174#SAPEngine_Application_Thread[impl:3]_7##0#0#Error#1#/System/Server#Java###Exception ID:03:47_17/05/07_0037_8171850
[EXCEPTION]
#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: iView not found: :.default
at com.sapportals.portal.prt.deployment.DeploymentManager.getPropertyContentProvider(DeploymentManager.java:1937)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:222)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)
at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:435)
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:522)
at java.security.AccessController.doPrivileged(AccessController.java:242)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:215)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Message was edited by:
cui zhao

Hello Cui Zhao,
Have you create a reference system for RFC ? If not ,you should create a reference system first.
PS check this link for create reference system:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/ed/845896b89711d5993900508b6b8b11/frameset.htm">Defining an SAP Reference System for User Data</a>
PS: reward the points for helpful anwser.
BR,
Jianguo Chen

Similar Messages

ERROR in the RFC communication when parabatch is set to more 3 (default)

Hi experts,
We have a 10 blades BIA system connecting to our BW Production. When we set the parabatch to more than the default 3 (we set to 4 or 5), We keep getting 'Batchpara Error' and 'Error in the RFC Communication: Error when opening an RFC Connection' during the initial index build. Here are what we do and what we see:
1. set parabatch to 5 and build 1 initial index (cube is 46 mil rows, 22 GB in size) - Failed with the above errors
2. set parabatch back to 3 and build 1 initial index (same cube as above)- successful but slow
3. set parbatch back to 3 and build 2 initial indexes simultaneously (16 mil rows/4GB and 6 mil rows/2 GB) - Failed with the above errors.
In the BIA index log I see the following error:
Error in the RFC communication: Error when opening an RFC connection (TREX_BIP)
Message no. STREX005
In SM37 in one of the logs I see the followings:
Parabatch Error
Any light you can shed on why we are encountering this issue will be much appreciated. Also, I observed that there is a long idle time in all systems (BIA, DB2, BW) and seemed like their respective resources were not utilized at all. Once in a while I do see surge of cpu/memory usage in all systems but not too terrible. I'm puzzled by why there is such long interval of idle time in all systems while the initial index build is going on.
BTW...we did the same thing (set parabatch to 5, and run parallel initial builds) in our non-prod BIA (2 blades) and QA BW landscape and do not have any issue at all.
Thanks!
Kee

Hello
PLease check the sapnotes and check the developer trace for more information.
Note 314530 - Number of RFC/CPIC connections for external clients
Note: 1070034
It can also be because your system has reached it its max gateway connections...also check whether you are getting error message "Communication error, CPIC return code 017, SAP return code 450
" in sm21 ???
Regards
Karthikeyan.K

Steps to create RFC iview

Hi ,
I am new to create RFC iview,
So please let me know steps to create RFC iview and one Example.
regards
mmukesh

In its simplest steps:
1 Create an SAP system in the system landscape - don't use Conenction String as the type.
2 Give it an alias.
3 Set permissions so your administrators and endusers can access the system.
4 Use the RFC iView creation wizard and select the system alias and your RFC.
5 Make sure you do step 4 as a user who has RFC access to the SAP system.
6 Test it!
Please note that changing the RFC iView after creation is a little messy. You might be better off using the Visual Composer - it is much neater at displaying RFC table data than the RFC iView.
Cheers

Passing parameters to RFC iview

Hi
Can anyone let me know how to pass parameters to RFC iview ?
i want to pass the parameter through URL to the RFC iview (funtion_params_name1)
thanks

Hi Thanks for your reply. I have a RFC function module that accepts two input parameters, queries R3 database and returns table output. Need to create a Portal page for the end users out of those returned data. Your help is much appreciated!.
Hi
Well it is possible
try this....
Create a abap webdynpro application, here you can call the RFC function module as a supply function
get the data from the function module and display it on the webdynpro view
convert this webdynpro to a iview and attach this iview to the portal page.( this is just a few steps process)
thanks

RFC DeliveryException: error

Hi,
I am working on DB2(Asyn)-SAP(Sync)-DB2(Asyc) using BPM. I do understand based on the SAP notes 730870 that the either the XML-RPC format or the parameters to the funcation module might be incorrect.
In my message mapping from JDBC to RFC under the message tab of the mapping screen I have 1 for JDBC occurances and 0..unbounded for the RFC as I will be selecting multiple rows from db. Currently in the MI mapping I have source and target as 1 occurances each, when I change the occurances in the target side to "0...unbounded" I do not see the response when I read the interfaces.
In this case do I need to change any thing in my BPM and is this causing this error ?
Bye the way my BPM is : Receive- Synch Send - Send.
Error from SXMB_MONI:
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null></SAP:AdditionalText>
Appreciate your help in resolving this error.
Thanks
Steve.
Message was edited by: Steve Holland

Krishna,
When I changed the occurances to 1 and 1:1 mapping and tested MM using the payload from MONI, I am not getting any output at all.
Test result says cannot produce the target element(first element).
My source structure based on the db is
SOURCE_DT
<Rows> --- 1..unbounded.
<field1>
</Row>
When I tried the rows of multi-occurance with 1:N mapping and I had the RFC execution error, but mapping was working.
Thanks
Steve

RFC Communication error when doing initial indexing

Hello Everyone,
I have a quick question, when doing the initial index rollup for a BIA index the job is failing with RFC communication error.
We currently have the setting related to " TREXRfcServer threads" set to "Automatic Changes" in order to avoid the RFC Communication errors when loading big loads in BI system.
We currently are on Revision 49.
I also have referred to OSS Note 1138603.
The issue is when I am rolling up the BIA Index the rollup job is failing with RFC Communication errors.
The Global parameters within BIA are:
BATCHPARA - 2
NUMPROC - 5
PKGSIZE - 10000000
SUBPKGSIZE - 20000
We have two app servers with 52 Dialog processes and 25 Background processes.
Any help would be really appreciated.
Thanks
Dharma.

Removing references to systems and ports
Issue:
When the initial indexing is being carried out for an InfoCube to
create the BIA Index and there is more than one application server in
the system the job is failing with the http error.
Hello Everyone,
Thanks for the input, after the automatic changes was configured for concurrent requests the error is different right now.
The error message is,
"Remote communication failure with partner http://<Removed>:<removed>/indexCellTable"
Overview/Background:
When the indexing job is triggered as a background job the failure happens when the S table index is being filled.
In our system where we are trying to do the stress testing we currently have two app servers and one central instance.
When I limit the RFCGROUP in RSDDTREXADMIN table to one App server in terms of logon group the job finishes fine.
Whereas, when I do not limit the RFCGROUP and all app servers are open for access the background job finishes with the error message
Remote communication failure with partner http://<Removed>:<removed>/indexCellTable.
We have looked into the OSS Note 1102652 and our BASIS team confirmed that they were able to ping from BI App servers into BIA blades and vice versa.
We also confirmed if the local gateway was used for connectivity.
The above issue was not in other systems where we only had one server.
We currently are at Revision 49 and SP 13 in BI.
We have E5345 Clowertown blades (2 x 4) 16GB blades.
Please let us know if you need additional information.
Thanks in advance for the input.
Dharma.
Edited by: Arun Varadarajan on Apr 24, 2009 1:36 AM

Unable to create RFC iviews - connection test of the system failed

hello,
I always try to configure my system to run an RFC iView...
The connection of myt system is failed for 1 of the 4 tests.
i don't know why.
I have filled this fields :
- application host
- ITS host name
- ITS path
- ITS protocol
- Logical system name (not sure it's correct)
- Sap client
- Sap system ID
- SAP system number
- Server port (not sure it's correct)
- System type
- Web as host name
- Web as path
- Web as protocol
and i have this error :
SAP Web AS Connection
Test Details:
The test consists of the following steps:
1. Check the validity of the system ID in the system object
2. Check if the system can be retrieved
3. Check if a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Check HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. Retrieval of the system was successful
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (wsapv49.dhcp.xxx.xx.xxxx:8045)
5. HTTP/S connection successful
ITS Connection
Test Details:
The test consists of the following steps:
1. Check the validity of the system ID in the system object
2. Check if the system can be retrieved
3. Check if the system object has a valid system alias
4. Check if a SAP system is defined in the system object
5. Validate the following parameters: ITS protocol; ITS host name
6. Check the validity of any user mapping in the system object
7. Check HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. Retrieval of the system was successful
3. Retrieval of the default alias was successful
4. The system object represents an SAP system
5. The following parameters are valid: ITS Protocol (http) ITS Host Name (wsapv49.dhcp.xxx.xx.xxxx:8045)
6. HTTP/S connection successful
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure user mapping is set correctly and all connection properties are correct.
Test Connection through the DQE
Test Details:
The test consists of the following steps:
1. Checks the existence of a backend admin user ID/password in the system properties.
2. Checks the existence of a default alias for the system.
3. Checks the DQE connection.
Results
1. DQE admin user ID or password is missing in the system properties. Make sure those properties exist for this system object.
2. Default alias of the system exists.
3. DQE connection successful. If you continue to experience problems, verify the DQE admin user ID and password properties for this system object.
can you help me to end this configuration?
thanks a lot.
(reward points for helful answers...)
Adrien

doesn't work, doesn't work... :o(
I found this in "analysis" -> "Debug"
error 3 mai 2007 16:49:32:168 Failed to get connection for system final
/System/Server com.sap.portal.ivs.connectorService sap.com/irj admin ITEM-31892 Server 0 0_33638
error 3 mai 2007 16:49:32:168 (R3/BW) Failed to get connection. Please contact your admin.
/System/Server com.sap.portal.connectors.R3 sap.com/irj admin ITEM-31892 Server 0 0_33638
i found too a -BIG- file in the directories, "last block" of the file
#1.5#000D56D8CEA2005D0000001500000FC400042F9201A5E5D2#1178204046283#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Administrator#49##ITEM4531892.dhcp_J2E_3363850#admin#1a943a10f98511dbc5d6000d56d8cea2#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
The error is: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.
Exception id: [000D56D8CEA2005D0000001300000FC400042F9201A5E071]#
#1.5#000D56D8CEA2005D0000001600000FC400042F9201A76132#1178204046383#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#Administrator#49##ITEM4531892.dhcp_J2E_3363850#admin#1a943a10f98511dbc5d6000d56d8cea2#SAPEngine_Application_Thread[impl:3]_3##0#0#Error##Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.)]. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.
 at com.sap.engine.services.servlets_jsp.server.runtime.client.GzipResponseStream.write(GzipResponseStream.java:209)
 at com.sap.engine.services.servlets_jsp.server.runtime.client.GzipResponseStream.write(GzipResponseStream.java:193)
 at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.writeError(HttpServletResponseFacade.java:952)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.sendError(HttpHandlerImpl.java:955)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleGeneralException(HttpHandlerImpl.java:860)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.processError(HttpHandlerImpl.java:851)
 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:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#000D56D8CEA2005D0000001800000FC400042F9201A765B7#1178204046383#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Administrator#49##ITEM4531892.dhcp_J2E_3363850#admin#1a943a10f98511dbc5d6000d56d8cea2#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#/System/Server/WebRequests#Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.)].
The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.
Exception id: [000D56D8CEA2005D0000001600000FC400042F9201A76132]#
and with another test connector
#1.5#000D56D8CEA200600000001800000FC400042F921D02D625#1178204505301#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#SAPEngine_Application_Thread[impl:3]_14##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
The error is: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.
Exception id: [000D56D8CEA200600000001600000FC400042F921D02D1AE]#
#1.5#000D56D8CEA200560000001600000FC400042F921D39B77B#1178204508896#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoInit()-> enter#
#1.5#000D56D8CEA200560000001700000FC400042F921D3AE547#1178204508977#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###connectToSystem()->Selected Systemnull#
#1.5#000D56D8CEA200560000001800000FC400042F921D3BE964#1178204509037#com.sap.tc.lm.ctc.provider.configurationmanager.ConfigManagerReader#sap.com/tcwddispwda#com.sap.tc.lm.ctc.provider.configurationmanager.ConfigManagerReader#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###getElement(String, Filter, int):NamedLocatedElement!ConfigManagerReader.SEARCH_FOR!CTC#
#1.5#000D56D8CEA200560000001900000FC400042F921D414CF2#1178204509397#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoInit()-> leave success#
#1.5#000D56D8CEA200560000001A00000FC400042F921E69A639#1178204528816#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoModifyView()-> enter#
#1.5#000D56D8CEA200560000001B00000FC400042F921E69A953#1178204528816#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoModifyView()-> success#
#1.5#000D56D8CEA2006E0000010500000FC400042F9231C81C6F#1178204853786#com.sap.portal.connectors.R3#sap.com/irj#com.sap.portal.connectors.R3#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#SAPEngine_Application_Thread[impl:3]_9##0#0#Error#1#/System/Server#Plain###(R3/BW) Failed to get connection. Please contact your admin. #
#1.5#000D56D8CEA204E70000000100000FC400042F9231C90EA8#1178204853846#com.sap.engine.services.dqe#sap.com/irj#com.sap.engine.services.dqe#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#Thread[Log_Worker_6,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Server/DQE#Plain###mai 03, 2007 17:07:33.786 [SAP_HOST|4039|SAPEngine_Application_Thread[impl:3]_9] <CONNECTOR.ERROR> Error trying to establish connection to the EIS : final Connection Failed: Nested Exception. Failed to get connection. Please contact your admin. #
#1.5#000D56D8CEA200690000001E00000FC400042F92335B4C9E#1178204880215#com.sap.portal.connectors.R3#sap.com/irj#com.sap.portal.connectors.R3#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Server#Plain###(R3/BW) Failed to get connection. Please contact your admin. #
#1.5#000D56D8CEA200690000002000000FC400042F92335B4FE3#1178204880215#com.sap.portal.ivs.connectorService#sap.com/irj#com.sap.portal.ivs.connectorService#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Server#Java###Failed to get connection for system #1#final#
i happy to carry my life's number one goal with another guy
(thanks, again and again)
Adrien
Message was edited by:
 Adrien Loire

Error In EP RFC IVIEW

Dear Experts,
While executing a FM in EP RFC Iview I am getting this error. Can Anyone Help.
Function execution failed.
Exception message: Nested Exception.
Failure to execute native function. Connection Failed: Nested Exception.
Native connection to the back end system is broken.
Thanks & Regards
Rajiv Roshan

Whatever You have said is done.
Actually I want to open Microsoft Excel in EP. For this I created an RFC IView and there I am calling my RFC. The RFC name and parameters are coming fine. But While previewing I am getting this Error.
In The RFC I have written The following Code:
CALL METHOD cl_gui_frontend_services=>execute
EXPORTING
 DOCUMENT = iv_file
 APPLICATION =
 PARAMETER =
 DEFAULT_DIRECTORY =
 MAXIMIZED =
 MINIMIZED =
 SYNCHRONOUS =
 OPERATION = 'OPEN'
EXCEPTIONS
 CNTL_ERROR = 1
 ERROR_NO_GUI = 2
 BAD_PARAMETER = 3
 FILE_NOT_FOUND = 4
 PATH_NOT_FOUND = 5
 FILE_EXTENSION_UNKNOWN = 6
 ERROR_EXECUTE_FAILED = 7
 SYNCHRONOUS_FAILED = 8
 NOT_SUPPORTED_BY_GUI = 9
 others = 10
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
In Iv_file if we give 'Excel' in R/3 it opens a new Excel Sheet, but in EP it is giving that error.

RFC Connection error message while Debug the running WebDynpro app

Dear friends,
I am trying to debug WebDynpro application.
After configuring the NWDS with the J2EE server instance, I try to run the WebDynpro application, which I want to debug.
I did selecting the application and run after putting breakpoint at a button click.
But the webdynpro application uses 2 JCo destiantions, and so it gives JCOClientConnection for logical System: ... Please assure that you have configured the RFC connections and/or logical system name properly for this model! message.
If I run the same application from the portal, it doesn't give such error message.
Can anybody help me how can I run the WebDynpro application for debug purpose without getting this error message?
Thanks and regards,
Lakshmikanthaiah

Hi,
are you running the application on the same server? Or are you using the Debugmode on your local installation.
If so, you should check the JCO Destinations on you local server.
<a href="http://localhost:50000/webdynpro/dispatcher/sap.com/tcwdtools/WebDynproConsole">http://localhost:50000/webdynpro/dispatcher/sap.com/tcwdtools/WebDynproConsole</a>
Regards,
Dennis

Error when trying to display a Webi report through the Folder iView

Hi all
I am getting the following error when Im trying to display a Webi report through the SAP Portal. We have installed the SAP Integration Kit and are able to see the content of the Infoview. However when we click on a Webi report, we receive the following error:
Could not get page number. (Error: RWI 00223) (Error: INF)
Have anyone else encountered this problem? Please assist! Any help will be rewarded.
(We are running XI Rel 2).
Addition from trace file (tomcat):
com.businessobjects.rebean.wi.CommunicationException: Could not get page number. (Error: RWI 00223)
     at com.businessobjects.rebean.wi.occa.OccaReportComAdapter.setBlobKey(OccaReportComAdapter.java:542)
     at com.businessobjects.rebean.wi.occa.OccaReportComAdapter.getView(OccaReportComAdapter.java:376)
     at com.businessobjects.rebean.wi.occa.OccaReportComAdapter.getView(OccaReportComAdapter.java:297)
     at com.businessobjects.rebean.wi.ReportImpl.getView(ReportImpl.java:384)
     at com.businessobjects.rebean.wi.ReportImpl.getView(ReportImpl.java:407)
     at org.apache.jsp.viewers.cdz_005fadv.viewReport_jsp._jspService(viewReport_jsp.java:1182)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704)
     at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:474)
     at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:409)
     at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312)
     at org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:670)
     at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:637)
     at org.apache.jsp.viewers.cdz_005fadv.report_jsp._jspService(report_jsp.java:325)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
     at java.lang.Thread.run(Thread.java:534)
Furthermore I'd like to see an example of the cms_name entry. The documentation states: In addition, specify the Application Parameter for each iView. For this property, enter cms_name=[cms] for the fully qualified server name., but I have doubts as to what format to use.
Kind regards,
Martin Søgaard

Hi Jim Ji
The report can be displayed from the java infoview, no doubt, so the report itself works.
But the report cannot be seen from the "SAP Infoview" (:/businessobjects/enterprise115/sap) which is the infoview, I reference from the Folder iView (through the system in the SAP portal). And since the SAP Portal Integration Kit seems very old - the Folder iView was created 12-08-2004 by Ingo Hilgefort - there might be an old version of the jar-files somewhere in the installation.
I guess I should check the version of the jar-files in WEB-INF/lib of our web application (Tomcat) folder, and see if they have been overwritten by the SAP Portal Integration Installation or are an older version of the files in Program FilesBusiness Objectscommon3.5javalib? And also check if somewhere in the .../sap installation there are some old jar-files?
Kind regards,
Martin Søgaard

Error in the RFC Connection

Hi Expert,
First, I'm sorry if I post in the wrong thread.
I have a problem when creating RFC Connection. I want to create RFC Connection between BW systems to R/3 System in SM59.
I already insert the right IP Address to the target system, but when I test the connection, I got this error :
host name 'SAP-BO-01' unknown / CPI-C error CM_PRODUCT_SPECIFIC_ERROR
I already test the connection from BW to R/3 and vice versa, using ping in command prompt, and I got no problem. Also, I already create a log on to the target system, and it was successful, but the RFC Connection still error.
Did you have any clue or solution about this?
I really appreciate every helpful comment from you. Thank You...

Hi
Do you have mapping in the host file in the server? ask you basis team to check that.
If you can ping the server, that means connection is fine, only thing is there might be some entry missing in hosts or services file in the server.
During creation of RFC connection you can directly use the IP address also. as you said you are able to ping the server that means you got to know the IP address. Now use the below command to know the exact hostname.
ping -a <IP_ADDRESS>
Regards
Anindya

Error while running the RFC on ECC 6.0 server

Hello Champs,
The problem I am facing while sending the data for validation and invalidation from RFC on ECC server to Pi server to be send to a webservice. This scenario was working perfectly fine when the RFC was run on R/3 4.7 server. On upgradation of R/3 server to ECC 6.0 server we found the folowing error while we run the RFC on ECC server.
alternativeServiceIdentifier:party/service from channel configuration are not equal to party/service from lookup of alt ..
I have also re-imported the RFC's from ECC server to PI server and activated it again to overcome this problem, but still I am getting this error. Also I have done the CPA cache refresh too. But the problem still persist.
Some times when we keep on clicking on this error continously then we are able to get the desired results ie either valid or invalid. Is there something which needs to be done when we migrate the RFC from R/3 server to ECC server? Pls let me know how to solve this problem... Any help on this on priority basis is highly appreciated.
Thanking You in Advance.
Regards
S Joshi

Dear Rajesh,
I did the activity as suggested by you but still I am getting the same error while sending the order ID number from ECC 6.0 server. But when check the error in the Moni transaction I am getting the error as follow:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Not enough message parts were received for the operation.
This indicates that there is a problem on the receiver side.. Pls guide me......
Thanks
With Best Regards
S Joshi

E-Recruiting BSP iView errors in the Enterprise Portal.

I am trying to get my e-Recruiting BSP applications to work correctly in the Portal. But unfortunatley I consistently get this error message.
The following error text was processed in the system:
BSP Exception: Das Objekt application.do/start in der URL /sap/bc/bsp/sap/hrrcf_start_int/application.do/start?sap-syscmd=nocookie&sap-client=&sap-language=en&sap-accessibility=&sap-ep-version=7.00.200611091758&sap_ep_version=7.00.200611091758&sap_ep_baseurl=http%3A%2F%2Fsnocfpd1.myco.org%3A50100%2Firj ist nicht gültig.
The BSP
https://snocfrd1.myco.org/sap/bc/bsp/sap/hrrcf_start_int/application.do?rcfLogAppl=SEARCH_JOBS
works fine.
anybody have any ideas how to troubleshoot this? I'm assuming it has to do with all the rest of the garbage parameters the Portal is sending to e-Recruit.
-Tim

Hi!
Obviously the BSP iView is configured wrong. Have closer look at the URLs:
BSP in native browser:
https://snocfrd1.myco.org/sap/bc/bsp/sap/hrrcf_start_int/application.do?rcfLogAppl=SEARCH_JOBS
BSP in Portal:
/sap/bc/bsp/sap/hrrcf_start_int/application.do/start?...
Obviously the iView contains a parameter start or you defined the BSP application name as application.do/start
Regards,
Volker

Error"SYSTEM Failure" while testing the RFC in SE37 : RFC to JDBC Scenario

Hi All,
I am doing RFC to JDBC scenario. When I am testing the RFC in SE37 using the RFC destination created in SM59, I get an error "SYSTEM FAILURE".
Please suggest.
Thanks,
Shyam
Edited by: Shyam Sreepada on Dec 18, 2007 5:46 PM

Hi,
You must run RFC with RFC destination in background mode, I suggest to read following post in order to understand it better.
Syntax would be:
CALL FUNCTION func IN BACKGROUND TASK
[DESTINATION <your RFC destination>]
parameter list
http://help.sap.com/saphelp_nw04/helpdata/en/8f/53b67ad30be445b0ccc968d69bc6ff/frameset.htm
If you read it you will find that you can't test it directly from SE37, for this either you need to create dummy ABAP program or another RFC where you will call this RFC with background syntax.
Regards,
Gourav
Reward points if it helps you
Edited by: Gourav Khare on Dec 18, 2007 6:07 PM

LDAP users Faicng Error While Accessing the ESS Iviews in Portal

Hi,
My Portal is SAP EP 7.0 SP20 And ECC 6.0 SP16.
UME users able to access the ESS MSS Iviews.But only one LDAP User only access ESS/MSS Iviews Other getting the Below error.
Critical Error
A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
Please contact your system administrator
Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE
Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE:
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE
                at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
                at com.sap.xss.ser.xssmenu.fc.ModelHandler.onInit(ModelHandler.java:205)
                at com.sap.xss.ser.xssmenu.fc.wdp.InternalModelHandler.onInit(InternalModelHandler.java:428)
                at com.sap.xss.ser.xssmenu.fc.FcXssMenu.setPersonnelNumber(FcXssMenu.java:570)
                at com.sap.xss.ser.xssmenu.fc.FcXssMenu.onInit(FcXssMenu.java:292)
                at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenu.onInit(InternalFcXssMenu.java:455)
                at com.sap.xss.ser.xssmenu.fc.FcXssMenuInterface.onInit(FcXssMenuInterface.java:165)
                at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface.onInit(InternalFcXssMenuInterface.java:389)
                at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface$External.onInit(InternalFcXssMenuInterface.java:546)
                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.pcuigp.xssutils.navi.FcNavigation.onInit(FcNavigation.java:314)
                at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigation.onInit(InternalFcNavigation.java:358)
                at com.sap.pcuigp.xssutils.navi.FcNavigationInterface.onInit(FcNavigationInterface.java:145)
                at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigationInterface.onInit(InternalFcNavigationInterface.java:142)
                at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigationInterface$External.onInit(InternalFcNavigationInterface.java:278)
                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.pcuigp.xssutils.roadmap.VcRoadmap.onInit(VcRoadmap.java:188)
                at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmap.onInit(InternalVcRoadmap.java:162)
                at com.sap.pcuigp.xssutils.roadmap.VcRoadmapInterface.onInit(VcRoadmapInterface.java:153)
                at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmapInterface.onInit(InternalVcRoadmapInterface.java:144)
                at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmapInterface$External.onInit(InternalVcRoadmapInterface.java:220)
                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:782)
                at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:302)
                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:1344)
                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.wdDoInit(PageBuilder.java:193)
                at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
                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:782)
                at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:302)
                at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
                at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
                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: Syntax error in program CL_XSS_CAT_BUFFER=============CP        ., error key: RFC_ERROR_SYSTEM_FAILURE
                at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
                at com.sap.pcuigp.xssutils.xssmenu.model.MenuModel.hrxss_Ser_Getmenudata(MenuModel.java:171)
                at com.sap.pcuigp.xssutils.xssmenu.model.Hrxss_Ser_Getmenudata_Input.doExecute(Hrxss_Ser_Getmenudata_Input.java:137)
                at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
                ... 76 more
Thanks & Regrads,
Subba Rao

Hi,
Now every user facing the same error while accessing ESS Iviews from Portal.
in ST22 Dump is created.
What happened?                                                                                |
Error in the ABAP Application Program
The current ABAP program "CL_XSS_CAT_TIME_SHEET=========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"CL_XSS_CAT_BUFFER=============CP " in include
"CL_XSS_CAT_BUFFER=============CM00C " in
line 50:
""L_CATSDB" and "L_CATSDBCOMM" are not mutually convertible. In Unicode"
" programs, "L_CATSDB" must have the same structure layout as "L_CATSDB"
"COMM", independent of the length of a Unicode character."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error in the ABAP Application Program
The current ABAP program "CL_XSS_CAT_TIME_SHEET=========CP" had to be
terminated because it has
|    come across a statement that unfortunately cannot be executed.
What we need to resolve the above issue.
Thanks & Regards,
Subba Rao

The RFC iview error

Similar Messages

Maybe you are looking for