Error in BEx broadcaster: "Java communication error: Error when opening an

[Former Member]

Hi All,

1) Logon to portal(EP7)

2) Choose Business Explorer from the top level role menu

3) Choose BEx Broadcaster

4) In the dropdown box "Settings for Object Type" choose query and click "Open"

5) In the popup box choose any query, eg ZZKS0002_QUERY

6) The error appears. Error message "Java communication error: Error when opening an RFC connection" is displayed.

FYI only one user is getting this error.

Kindly suggest on the above issue.

Thanks,

Mahesh

[Former Member · Accepted solution]

Hi Mahesh,

RFC communication is always used when the SAP Web Application Server JAVA and the SAP Web Application Server ABAP communicate "in the background", which means that they communicate with each other on the server. For instance, when query results are read to display them in a Java-based BEx Web Application or when precalculated HTML pages are generated in a batch job and the pages are then distributed to a Knowledge Management folder using information broadcasting.

A system parameter is not specified correctly causing the connection setup to fail.

Error message: "hostname '...' unknown", "service '...' unknown" or an error message in the dev_jrfc.trc log file

Solution: Correct the incorrect parameter in the settings of the RFC Bundle in the J2EE Visual Administrator in "<J2EE_SID>" -> "Server" -> "Services" -> "JCo RFC Provider".

SAP NetWeaver 2004s: Setting Up BEx Web

SAP Note Number: [917950|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bw_sys/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d393137393530%7d]

BEx Web Java: Analysis of communication/logon problems

SAP Note Number: [888687|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bw_bex/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d383838363837%7d]

Regards

Andreas

[Former Member · Accepted solution]

Hi Andreas,

Thanks for the suggestion.

We have similar setting of RFC bundles on other portal servers and its working fine without any issue. The only difference is the number of server count is different.

i.e, server count -20 where no issue reported

server count -1 issue reported in Bex broadcaster.

Does it makes any sense?

What would be the impact if we change the server counts on RFC bundles.

I did the initail testing as per the SAP notes 917950.

In the SAP_BW system connector connction has been failed(Make sure that Single Sign-On is configured correctly)

Kindly suggest.

Regards,

Mahesh

[Former Member · Accepted solution]

Hi,

We have another related error as below

"Java system error: Server repository could not create function template for 'RSRD_X_GET_PORTAL_INFO_PROXY' caused by: com.sap.mw.jco.JCO$Exception"

Kindly suggest.

Thanks.

Regards,

Mahesh

[Former Member · Accepted solution]

Hi,

you can check your settings by using the support desk tool.

Check:

Usage of SAP NetWeaver BI Diagnostics & Support Desk Tool

SAP Note Number: [937697|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bw_bex/~form/handler]

Regards

Andreas

[Former Member · Accepted solution]

Additional check regarding error msg:

Server repository could not create function template

SAP Note Number: [1229100 |https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_mid/~form/handler]

Symptom

RFC call to JAVA Application Server (destination type T) from an ABAP AS finishes with SYSTEM FAILURE.

The error message starts with "Server repository could not create function template...", but the error description is cut since the message field on the ABAP side is not sufficiently long.

Other terms

RfcEngine, JCo RFC Provider

Solution

The whole error text contains is most cases enough information about the reason for the failure. The whole error text is logged on the Java Application Server and can be found using the "log viewer".

Start NetWeaver Administrator in the browser, go to Problem Management -> Logs and Traces -> Log Viewer Select "default traces" and search for the error.

[Former Member · Accepted solution]

Hello Mahes, we have a similar error with our broadcasting. Were you able to trouble shoot yours.. Thanks Mayil

"Java system error: Server repository could not create function template for 'RSRD_X_PRODUCE_PROXY' caused by:"

Diagnosis

An error occurred in the BI components on the SAP J2EE Engine.

System Response

Procedure

Contact your system administrator to have the error analyzed in detail.

Procedure for System Administration

Start the Visual Administrator, log on to the SAP J2EE Engine and choose "<J2EE_SID>" ->"Server" -> "Services" -> "Log Viewer".

The file "defaultTrace.trc" includes detailed information about the error that occurred. In Windows, you can find this file in the Log Viewer under "Cluster <computer name>" -> "Server <server number>" -> "<drive>:\usr\sap\<SID>\JC<INSTANCE>\j2ee\cluster\server<NUMBER>\log". ". In Unix, the file is located under "/usr/sap/<SID>/JC<INSTANCE>/j2ee/cluster/server<NUMBER>/log".

If the file does not include enough detail about the error, you can increase the log level to obtain more information. To do this, choose "<J2EE_SID>" -> "Server" -> "Services" -> "Log Configurator". On the "Locations" tab page, choose "com" -> "sap" -> "ip" -> "bi" -> "webapplications". Using the selection list on the right side of the screen, you can increase the log level, whereby "DEBUG" represents the log level with the most information. You can save your settings by choosing the "Save" icon. The change to the log level is active immediately. Once you have successfully analyzed the error, you should set the log level back to its default value using the appropriate pushbutton; continuous writing to the log file negatively affects the overall performance of the system.

Notification Number RSBOLAP 018

[Former Member · Accepted solution]

Hi Mahesh

Has this been resolved ? In our landscape user reported the similar error.I could not see any errors reported in dev_jrfc.trc.Can you help with the action you have taken to resolve this

[Former Member]

NA

[Former Member]

Hi Mahesh,

Check with authorization for RFC.

check below SAP Notes : 888687

it may help you

Thanks,

Vijay.

[Former Member]

Hi Vijay,

I do checked the SAP note 88867 and not bale to find the rootcause. Below is the error message in the

dev_jrfc.trc file.

Kindly suggest.

Exception thrown [Thu Apr 16 06:08:01,059]:Exception thrown by application running in JCo Server

com.sap.engine.services.ejb.exceptions.BaseRemoteException: Exception in method processFunction.

at com.sapportals.portal.prt.service.rfc.PRTRFCRemoteObjectImpl0_0.processFunction(PRTRFCRemoteObjectImpl0_0.java:127)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)

at $Proxy135.processFunction(Unknown Source)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)

at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)

at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254)

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.ip.bi.base.service.connection.ConnectionException: No connection possible to BI master system SAP_BW

at com.sap.ip.bi.base.service.connection.impl.GenericConnectionPool.getMasterSystemConnection(GenericConnectionPool.java:71)

at com.sap.ip.bi.base.application.impl.Application.createService(Application.java:466)

at com.sap.ip.bi.base.application.impl.Application.getProperty(Application.java:718)

at com.sap.ip.bi.base.application.impl.Application.startApplicationStep(Application.java:286)

at com.sap.ip.bi.base.application.impl.Application.initialization(Application.java:266)

at com.sap.ip.bi.base.application.ApplicationFactory.createApplication(ApplicationFactory.java:172)

at com.sap.ip.bi.base.application.ApplicationFactory.createApplication(ApplicationFactory.java:65)

at com.sap.ip.bi.portalrfc.dispatcher.services.BIServicesRfcDispatcherService.doHandleRequest(BIServicesRfcDispatcherService.java:213)

at com.sap.ip.bi.portalrfc.services.BIRfcService.handleRequest(BIRfcService.java:247)

at com.sapportals.portal.prt.service.rfc.RFCEngineService.handleEvent(RFCEngineService.java:345)

at com.sapportals.portal.prt.service.rfc.PRTRFCBean.processFunction(PRTRFCBean.java:37)

at com.sapportals.portal.prt.service.rfc.PRTRFCRemoteObjectImpl0_0.processFunction(PRTRFCRemoteObjectImpl0_0.java:118)

... 17 more

Caused by: com.sap.ip.bi.base.service.connection.ConnectionException: No connection exists for system "SAP_BW"

at com.sap.ip.bi.base.portal.connection.PortalConnectionPool.getConnection(PortalConnectionPool.java:206)

at com.sap.ip.bi.base.service.connection.impl.GenericConnectionPool.getMasterSystemConnection(GenericConnectionPool.java:67)

... 28 more

Caused by: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: This system rejects all logons using SSO tickets

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)

at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1025)

at com.sap.mw.jco.JCO$Client.connect(JCO.java:3255)

at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.connectWithJCO(SAPCFConnectorManagedConnection.java:429)

at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.establishInitialConnection(SAPCFConnectorManagedConnection.java:204)

at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.init(SAPCFConnectorManagedConnection.java:183)

at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnectionFactory.createManagedConnection(SAPCFConnectorManagedConnectionFactory.java:129)

at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:338)

at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:188)

at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorConnectionFactory.getConnectionEx(SAPCFConnectorConnectionFactory.java:156)

at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:295)

at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:256)

at com.sapportals.portal.ivs.cg.ConnectorService.getConnection(ConnectorService.java:446)

at com.sapportals.portal.ivs.cg.ConnectorService.getConnection(ConnectorService.java:84)

at com.sap.ip.bi.base.portal.connection.PortalConnectionPool.getConnection(PortalConnectionPool.java:170)