Port A000000016 is not an RFC port

Hi,
While configuring ALE/IDOC configuration I am getting below error while distributing Model View.
"Distribution of model view ERECRUIT
Target system QERCLNT300                  RFC destination for synchronous communication (message type
                                                             SYNCH) Port A000000016 is not an RFC port, or RFC destination
                                                             is missing."
I have generated the partner profiles and that is showing port A000000022 is assigned with the rfc. but this Model View is picking A000000016 port again & again and throwing error. This all happened after we did the refresh from prod system.
Will appreciate early help.
Thanks,
Kamal

Target system QERCLNT300 RFC destination for synchronous communication (message type
SYNCH) Port A000000016 is not an RFC port, or RFC destination
is missing."
I have generated the partner profiles and that is showing port A000000022 is assigned with the rfc.
but this Model View is picking A000000016 port again & again and throwing error. This all
happened after we did the refresh from prod system.
Go to WE20 and select the partner system to which you are communicating. now select the
message type. You will see the Port that particular Message type is using. *You can add
you A000000022 here for all the message types in the distribution model.* Even if one message
type id using A000000016 it will give the same error.
In addition also check if the port A000000022 has correct RFC Specified thru WE21.
Regards
Shital

Similar Messages

I cannot copy and paste details from my bank statement into a word document, without the formatting changing.I have a message in my Error console which reads: server does not support RFC 5746, see CVE-2009-3555

Since transferring data from my desktop to my laptop, i am now having problems copying and pasting details from my bank website in to a word document, the formatting is all over the place. This didnt happen before, when i pasted the details in to the word document the formatting was exactly the same as on the webpage. If I use internet explorer, I dont have this problem, so, I can only assume it has something to do with Firefox. I have checked the "Error console" and I am receiving this message: server does not support RFC 5746, see CVE-2009-3555.

Maybe: 
Dafizilla Table2Clipboard: https://addons.mozilla.org/firefox/addon/1852

Server does not support: RFC 567456 see CVE-2009-3555

I am running Win 7, with a Netgear wireless dongle (Wn111v2) via a BT HomeHub. Both with latest drivers. Apart from Auto updates from MS & Firefox, no other software newly loaded.
Recently, Netgear starts with 113 Mbps, then rapidly drops to 1 Mbps. Firefox Error console states: "Server does not support: RFC 567456 see CVE-2009-3555"
All assistance appreciated. Dan

That message is meant for webmasters to make them aware that they need to fix their servers.
Firefox 3.6 versions can detect such a misconfiguration and displays a warning in the "Tools > Error Console".
See also https://wiki.mozilla.org/Security:Renegotiation
'''Update Adobe Reader (Adobe PDF Plug-In)'''
*Check your version: http://www.mozilla.com/en-US/plugincheck/
**'''Note: plugin check does ont have information to check all versions of all plugins'''
*'''Another new version of Adobe Reader is schedule for release during the week beginning 2010-08-16 to correct security issues.'''
Updating Adobe Reader:
#From within your existing Adobe Reader:
#*Open the Adobe Reader program from your Programs list
#*Click Help > Check for Updates
#Download complete installer:
#*Use Firefox to download and SAVE the installer to your hard drive from the link in the article below
#*On the Adobe page, un-check any extra items (i.e. Free McAfee® Security Scan Plus) then click Download button
#*If you see message just under tabs, DO NOT click the Allow button, instead click below that where it says "click here to download".
#*Click "Save to File"; save to your desktop
#*After download completes, close Firefox
#*Click the installer you just downloaded and allow the install to continue
#**Note: Vista and Win7 users may need to right-click the installer and choose "Run as Administrator"
#*See: https://support.mozilla.com/en-US/kb/Using+the+Adobe+Reader+plugin+with+Firefox#Installing_and_updating_Adobe_Reader
#After the installation, start Firefox and check your version again.

Server does not support RFC 5746, see CVE-2009-3555

When accessing option: "Personal Banking" at "www.onlinesbi.com" Firefox 3.6.8 crashes. ERROR CONSOLE displays "www.onlinesbi.com : server does not support RFC 5746, see CVE-2009-3555". OS: Windows Vista Home Premium SP-2.

The message about CVE-2009-3555 is meant for webmasters to make them aware that they need to fix their servers. 
Firefox 3.6 versions can detect such a misconfiguration and displays a warning in the "Tools > Error Console".
* http://wiki.mozilla.org/Security:Renegotiation

Who can tell me if it right I can not write rfc with bdc?

Dear experts,
I want to write a rfc with BDC so that vs.net can use this rfc, but I find it can not be used. who can tell me if it right I can not write rfc with bdc?
Best Regards,
Shinny

Hi Shinny,
Can you explain what error are you getting a little briefly. Coz you can write BDC in Function Modules.
Thanks,
Prashanth

Hi I keep getting this "Server Does Not Support RFC 5746/ CVE-2009-3555" when I try to see my bank account.

I try to login to my web account and I get this message "Server Does Not Support RFC 5746/ CVE-2009-3555"

The message about CVE-2009-3555 is meant for webmasters to make them aware that they need to fix their servers. 
Firefox 3.6 versions can detect such a misconfiguration and displays a warning in the "Tools > Error Console".
See http://wiki.mozilla.org/Security:Renegotiation

I cant access my bank account since having firfox always get error message and it now says retail.santander.co.uk : server does not support RFC 5746, see CVE-2009-3555 does anyone know what i need to change thanks

i keep getting an error message and i know its to do with firefox but have also gone into one of the settings and it says the following retail.santander.co.uk : server does not support RFC 5746, see CVE-2009-3555 but not what to do now??

Clear the cache and the cookies from sites that cause problems.
* "Clear the Cache": Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
* "Remove the Cookies" from sites causing problems: Tools > Options > Privacy > Cookies: "Show Cookies"
See also:
* http://kb.mozillazine.org/Error_loading_websites
The message about CVE-2009-3555 is meant for webmasters to make them aware that they need to fix their servers and visitors like you can ignore that warning. 
Firefox 3.6 versions can detect such a misconfiguration and displays a warning in the "Tools > Error Console".
* http://wiki.mozilla.org/Security:Renegotiation

What does this mean in lay terms: server does not support RFC 5746, see CVE-2009-3555

This error turns up sometimes most of the time associated with another message that says that the 'server timeout.'

'''''"server does not support RFC 5746, see CVE-2009-3555"''''' 
That message is meant for webmasters to make them aware that they need to fix their servers. Firefox 3.6 versions can detect such a misconfiguration and displays a warning in the "Tools > Error Console".
See: https://wiki.mozilla.org/Security:Renegotiation
 
You have an item installed that is considered malware/spyware/adware, "My Web Search Plugin Stub". This type of pest is usually installed along with software you download from the internet; generally free programs, but not always. Carefully watch for "extra" items that will be installed and un-check or opt-out of them.
#You can check to see if you have any of these from [http://www.google.com/search?q=%22Fun+Web+Products%22&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:es-ES:official&client=firefox-a|"Fun Web Products"] installed:
#*Control Panel > Add or Remove Programs, click on any that you find and click "Remove": Ask.com Bar, My Search Bar, MyWay Speed Bar, My Web Search Bar, Fun Web Products Easy Installer
#*See:
#**http://www.safer-networking.com/removemywebsearch.php
#**[http://www.pchell.com/support/mywebsearch.shtml|PC Hell: My Web Search Removal Instructions]
#**http://helpint.mywebsearch.com/intlinfo/help/toolhelp.jhtml#q3
#You '''MAY''' need to change a preference to reset your default URL/location bar search provider:
#*Enter '''about:config''' in the address/URL bar and press the Enter key
#*If you see a warning, accept it (Promise that you will be careful)
#*Filter = keyword.URL
#*Below the Filter, if keyword.URL is '''bold''', right-click on keyword.URL and choose "Reset"
#*Restart Firefox (File > Restart Firefox)
#*See: http://kb.mozillazine.org/Keyword.url
#You '''MAY''' need to reset your homepage. Firefox can open multiple home pages. Home pages are separated by the "|" symbol.
#*See: http://support.mozilla.com/en-US/kb/How+to+set+the+home+page
 
You need to update your plugins. It is important to keep them updated due to continuing security fixes and improvements in those plug-ins:
*Adobe Shockwave for Director Netscape plug-in, version 11.5 (you '''may''' need to update)
#Check your plugin versions: http://www.mozilla.com/en-US/plugincheck/
#*'''Note: plugin check page does not have information on all plugin versions'''
#'''Update Shockwave for Director'''
#*NOTE: this is not the same as Shockwave Flash; this installs the Shockwave Player.
#*Use Firefox to download and SAVE the installer to your hard drive from the link in the article below (Desktop is a good place so you can find it).
#*When the download is complete, exit Firefox (File > Exit)
#*locate and double-click in the installer you just downloaded, let the install complete.
#*Restart Firefox and check your plugins again.
#*'''Download link and more information''': http://support.mozilla.com/en-US/kb/Using+the+Shockwave+plugin+with+Firefox

I have prolblem like this, server does not support RFC 5746, see CVE-2009-3555 - can i get solution

server does not support RFC 5746, see CVE-2009-3555

The message about CVE-2009-3555 is meant for webmasters to make them aware that they need to fix their servers. You can ignore that error as a normal user (visitor). Firefox 3.6 versions can detect such a misconfiguration and displays a warning in the "Tools > Error Console".
* http://wiki.mozilla.org/Security:Renegotiation

Program not registered - RFC to J2EE (local machine)

I have a local install of WAS on my laptop using MSSQL 2000. I am trying to integrate local portal into a BI system.
1. I completed SLD configuration of local J2EE
2. As part of local SLD config I specified a BW7 system as data supplier
- entered BW7 host & gateway
- kept default settings for "configure data supplier targets" (i.e: sld/active=TRUE)
3. In Visual composer I successfully triggered SLD data transfer
4. In Visual Composer I specified a JCo RFC Provider to the BW7 system I want to access.
5. If I go to BW7 and goto tcode SMGW -> GOTO -> Logged on client, I see 2 pair of entries for JCo RFC provider
with the following settings
- system type: Registered Server (REGISTER_TP)
- state: connected
- LU name & Host Name = J2EE Host name w/ last 4 characters truncated. Only first 8 characters appear.
- TP Name: 2 entries = SLD_UC & 2 entries = SLD_NUC. So a total of 4 connections. My understanding is that TP Name is supposed to = Registered Server Program
6. In BW7, I have an RFC w/ Registered Server Program setting and program ID = JCo RFC Provider program ID
7. In BW7 RFC & JCo RFC the host & gateway settings are the same, they both refer to the BW7. THIS IS THE PART WHERE I AM UNSURE. I would have thought that the host & gateway settings of BW7 RFC would refer to Local J2EE engine. AND I DON'T KNOW WHAT THE GATEWAY IS FOR LOCAL J2EE.
8. In BW7 when I try to test the RFC, I get errors:
- Logon Connection Error
- program <...> not registered / CPIC-CALL: 'ThSAPOCMINIT' Tran
- ERROR: program <...> not registered
- DETAIL: TP <...> not registered
- COMPONENT: SAP-Gateway
- MODULE: gwr3cpic.c
- RETURN CODE: 679
- SUBRC: 0
- RELEASE: 700
- VERSION: 2
9. I completed step 1 & 2 of RSPOR_SETUP
- Step 1 <Create RFC Destination in J2EE engine> messages:
No Authorization to SMGW
Profile parameter login/create_sso2_ticket is not set to 2
Check of RFC destination <...> with RFC_READ_TCPIP_DESTINATION successful
- Step 2 <Create RFC destination to Portal> messages:
No Connection
Option Send SSO tickets not active (see documentation)
RFC CALL RFC_PING, destination <...> failed with sy-subrc =2
There a little something missing. Hope u gurus can help, lost a weekend over this.

Hello,
we get the same message (program ... not registered, COMPONENT: SAP-Gateway) in sm59, when checking the TCP/IP connection. We got it, after we changed the user name in the Visual Administrator.
Does anyone know with which tool and where the program can be registered. (The connection has no user name (connection by SAP ticket)).
Best regards,
Thomas

Can not call RFC inside VC

Hi everybody,
i use a RFC in my VC. The local test of the R/3 RFC within NWDS (Test Data Service) runs with success. But if i start the Application and call this RFC i get the following error:
Error in getting the connection Could not find destination XXX
Error occurred while executing the service: Could not get connection to the backend XXX
Error Occurred while executing the service: Error occurred while executing the service:
Could not get connection to the backend XXX
Please help...
Thanks,
Sid

Hi Sid,
If you are working with NWDS, except for defining the destination in the NWDS you also have to define the same destination in the WAS you deploy to. That is because the runtime environment for your model (the WAS) also has to connect to the destination.
A system administrator can define the destination from NetWeaver Administrator (/nwa).
Best regards,
Tal.

Can not call RFC contains "call transaction" in webdynpro

We use Webdynpro to develope a UI that can create service orders in CRM
system. We create an RFC funciton "ZKLEE_CRM_ORDER_MODIFY" in CRM,which
contain a statement of "CALL TRANSACTION 'CRMD_BUS2000120' USING T_BDC
MODE 'N' MESSAGES INTO MESSTAB.".
But as we exacute the RFC from WEB,we got 3 error messages in the
output "MESSTAB":
1.MESSAGE ID = "DC",MESSAGE NUMBER = "006", MESSAGE = "Control
Framework: Fatal error - GUI cannot be reached".
2.MESSAGE ID = "SY",MESSAGE NUMBER = "002", MESSAGE = "Exception
condition CNTL_ERROR raised."
3.MESSAGE ID = "00",MESSAGE NUMBER = "359",and it is a terminate
message.
The problem is that we can use webdynpro to call RFCs that do not
contain "call transaction" freely. At first we suspect that it is our
RFC function's fault, but we tried it in ABAP enviroment,and it works
OK. We also tried to call this RFC in JSP through JCO,the same error
occurs.
Our system enviroment is CRM 4.0, J2EE 640, kernel 640 patch 109.

HI,
Thank you for your information.
Maybe you are right that BAPI/RFC can not contain "call transaction" statement. But two weeks ago, one of my colleagues tried to use "call transaction" in RFC through JCO in our R/3 enviroment(not in CRM),and he successed.
So I suspect the kernel release. The kernel of R/3 is 640,while CRM is 620(I said our CRM kernel release is 640 before,and it is a mistake.).I will confirm whether what my colleague said is right by myself, and will also told you the result.
Message was edited by: Vincent zklee

Can not perform RFC lookup

Hi All,
We are getting below error in doing testing in PI mapping.We are calling a RFC function module in PI.
Cannot perform RFC lookup com.sap.aii.mapping.api.StreamTransformationException: Cannot perform RFC lookup at com.sap.aii.mappingtool.flib7.RfcLookup.cacheMore(RfcLookup.java:105) at com.sap.aii.mappingtool.tf7.rt.AMultiResIterator$MultiOutIterator.gotoNextContext(AMultiResIterator.java:95) at com.sap.aii.mappingtool.tf7.AMappingProgram.processNode(AMappingProgram.java:299) at com.sap.aii.mappingtool.tf7.AMappingProgram.processNode(AMappingProgram.java:395) at com.sap.aii.mappingtool.tf7.AMappingProgram.processNode(AMappingProgram.java:395) at com.sap.aii.mappingtool.tf7.AMappingProgram.start(AMappingProgram.java:482) at com.sap.aii.mappingtool.tf7.Transformer.start(Transformer.java:133) at com.sap.aii.mappingtool.tf7.AMappingProgram.transform(AMappingProgram.java:612) at com.sap.aii.ibrep.server.mapping.exec.ExecuteXiMappingCommand.transformInternal(ExecuteXiMappingCommand.java:197) at com.sap.aii.ibrep.server.mapping.exec.ExecuteXiMappingCommand.execute(ExecuteXiMappingCommand.java:94) at com.sap.aii.ib.server.mapping.exec.CommandManager.execute(CommandManager.java:43) at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:40) at com.sap.aii.ibrep.server.mapping.MapServiceBean.execute(MapServiceBean.java:40) at sun.reflect.GeneratedMethodAccessor743.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy1621.execute(Unknown Source) at sun.reflect.GeneratedMethodAccessor742.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) Caused by: com.sap.aii.mapping.lookup.LookupException: Exception during processing the payload. Error when calling an adapter by using the communication channel BigWRFCReceiver (Party: , Service: KD3_300, Object ID: 4dcd47e22ff0367ea3779fe0e9dc7fd2) XI AF API call failed. Module exception: 'error while processing the request to rfc-client: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.adapter.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.adapter.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=KD3.AP.CSPLC.ORG SYSNR=22 GWHOST=KD3.AP.CSPLC.ORG GWSERV=sapgw22 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.227.148.123:sapgw22' not reached TIME Fri Aug 6 02:11:46 201 RELEASE 710 COMPONENT NI (network interface) VERSION 39 RC -10 MODULE nixxi.cpp LINE 2778 DETAIL NiPConnect: 10.227.148.123:3322 SYSTEM CALL connect ERRNO 239 ERRNO TEXT Connection refused COUNTER 27 '. Cause Exception: 'com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.adapter.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.adapter.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=KD3.AP.CSPLC.ORG SYSNR=22 GWHOST=KD3.AP.CSPLC.ORG GWSERV=sapgw22 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.227.148.123:sapgw22' not reached TIME Fri Aug 6 02:11:46 201 RELEASE 710 COMPONENT NI (network interface) VERSION 39 RC -10 MODULE nixxi.cpp LINE 2778 DETAIL NiPConnect: 10.227.148.123:3322 SYSTEM CALL connect ERRNO 239 ERRNO TEXT Connection refused COUNTER 27 '. com.sap.aii.mapping.lookup.LookupException: Error when calling an adapter by using the communication channel BigWRFCReceiver (Party: , Service: KD3_300, Object ID: 4dcd47e22ff0367ea3779fe0e9dc7fd2) XI AF API call failed. Module exception: 'error while processing the request to rfc-client: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.adapter.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.adapter.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=KD3.AP.CSPLC.ORG SYSNR=22 GWHOST=KD3.AP.CSPLC.ORG GWSERV=sapgw22 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.227.148.123:sapgw22' not reached TIME Fri Aug 6 02:11:46 201 RELEASE 710 COMPONENT NI (network interface) VERSION 39 RC -10 MODULE nixxi.cpp LINE 2778 DETAIL NiPConnect: 10.227.148.123:3322 SYSTEM CALL connect ERRNO 239 ERRNO TEXT Connection refused COUNTER 27 '. Cause Exception: 'com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.adapter.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.adapter.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=KD3.AP.CSPLC.ORG SYSNR=22 GWHOST=KD3.AP.CSPLC.ORG GWSERV=sapgw22 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.227.148.123:sapgw22' not reached TIME Fri Aug 6 02:11:46 201 RELEASE 710 COMPONENT NI (network interface) VERSION 39 RC -10 MODULE nixxi.cpp LINE 2778 DETAIL NiPConnect: 10.227.148.123:3322 SYSTEM CALL connect ERRNO 239 ERRNO TEXT Connection refused COUNTER 27 '. at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.process(AdapterProxyLocal.java:92) at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.call(SystemAccessorInternal.java:55) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:140) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:73) at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:167) at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:212) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:337) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:238) at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:532) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:670) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376) at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:295) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222) 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:152) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247) Caused by: com.sap.aii.af.service.api.AFException: XI AF API call failed. Module exception: 'error while processing the request to rfc-client: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.adapter.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.adapter.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=KD3.AP.CSPLC.ORG SYSNR=22 GWHOST=KD3.AP.CSPLC.ORG GWSERV=sapgw22 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.227.148.123:sapgw22' not reached TIME Fri Aug 6 02:11:46 201 RELEASE 710 COMPONENT NI (network interface) VERSION 39 RC -10 MODULE nixxi.cpp LINE 2778 DETAIL NiPConnect: 10.227.148.123:3322 SYSTEM CALL connect ERRNO 239 ERRNO TEXT Connection refused COUNTER 27 '. Cause Exception: 'com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.adapter.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.adapter.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=KD3.AP.CSPLC.ORG SYSNR=22 GWHOST=KD3.AP.CSPLC.ORG GWSERV=sapgw22 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.227.148.123:sapgw22' not reached TIME Fri Aug 6 02:11:46 201 RELEASE 710 COMPONENT NI (network interface) VERSION 39 RC -10 MODULE nixxi.cpp LINE 2778 DETAIL NiPConnect: 10.227.148.123:3322 SYSTEM CALL connect ERRNO 239 ERRNO TEXT Connection refused COUNTER 27 '. at com.sap.aii.af.service.api.AdapterAccess.sendMsg(AdapterAccess.java:214) at com.sap.aii.af.service.api.AdapterAccess.call
Please sugets how to resolve this issue.
Thanks
Mohit

Hi Mohit,
Do full CACHE refresh.
http://<host>:5<sys#>00/CPACache/refresh?mode=full
This may solve the issue.
Thanks,
Vijay.

Any SAP Note for RFC Error between BI and ECC 5.0

Hi..
the RFC Destination between BI and ECC 5.0 is giving errors.
Plz let me know if there is any Support pack or any solution to fix this error.
thanks..

Hi,
pls find the RFC connection details
1 Prerequisites
1.1 User Roles
Use
With the Building Block Connectivity a configuration role for each component is provided to access all transactions relevant for the installation. The following roles are available:
Technical name Description File name for upload
B02_01C B02 - Connectivity Configuration Role (SAP R/3) B02_01C.SAP
B02_03C B02 - Connectivity Configuration Role (SAP BW) B02_03C.SAP
C71_04C B02 - Connectivity Configuration Role (SAP CRM) C71_04C.SAP
B02_04C_SRM B02 - Connectivity Configuration Role (SAP SRM) B02_04C_SRM.SAP
Procedure
Please upload the necessary roles and add them to your user, using transactions PFCG (Role Maintenance).
2 Local Settings
This chapter describes all local settings that are necessary for each component like SAP R/3, SAP SCM, SAP BW, SAP CRM or SAP SRM.
2.1 SAP R/3
2.1.1 Define Client Administration (SAP R/3)
Use
This activity allows you to change Customizing settings.
Prerequisites
You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
Procedure
Run the following activity:
SAP R/3 Role Menu Define Client Administration (SAP R/3)
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
Then carry out the following steps:
1. Choose Display  Change.
2. Confirm the warning message Caution: The table is cross client.
3. Select your SAP R/3 client and choose Details.
4. In the Change View Clients: Details screen, activate the following settings:
u2022 Automatic recording of changes
u2022 Changes to Repository and cross-client Customizing allowed
u2022 eCATT and CATT allowed.
5. Save.
6. Go back to the SAP Easy Access menu.
2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)
Use
The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
1. Define the systems as logical systems.
2. Assign the logical system for the SAP R/3 System to a client.
This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
Logical systems are defined cross-client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Defining a Logical System for SAP R/3 (SAP R/3)
Transaction Code SPRO
SAP R/3
IMG Menu Basis Components (for R/3 Enterprisse: SAP Web Application Server)  Application Link Enabling (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System
2. Choose New entries.
3. In the column Log System, enter a name for the logical system that you want to create.
4. In the column Name, enter a description of the logical system.
Log. System Name
where XXX is the system name
and NNN is the client.
5. Save your entries.
A transport request for Workbench appears.
6. Select an existing request or create a new request, if necessary.
A transport request for Customizing appears.
7. Select an existing request or create a new request, if necessary.
2.1.3 Assigning Logical System to Client
Use
The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Assign Logical System to Client
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Choose Display ® Change.
3. Confirm the warning message The table is cross client.
4. Select your R/3 client and choose Details.
5. Enter the name of the logical system of your SAP R/3 client.
6. Save and confirm the warning message Be careful when changing the logical system.
7. Choose Back twice.
2.1.4 Creating an RFC User (SAP R/3)
Use
To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Creating an RFC User (SAP R/3)
Transaction Code SU01
SAP R/3 Menu Tools  Administration  User Maintenance  Users
2. In the User field, enter RFCUSER.
3. Choose Create.
4. On the Maintain User screen, enter the following data on the Tab entry screens:
Address
Last Name
Function
Logon data
User type System
Password LOGIN
Profile
Profiles SAP_ALL
SAP_NEW
S_BI-WX_RFC
Defaults
Logon Language EN
5. Save your entries.
2.3 SAP BW
2.3.1 Define Client Administration
Use
This activity defines changes and transports of the client-dependent and client-independent objects.
Procedure
1. To perform this activity, choose one of the following navigation options:
SAP BW Role Menu Local Settings ® Define Client Administration
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Switch to change mode.
3. Select your client.
4. Choose details.
5. In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
6. In field Client Role enter Customizing
7. Check the settings for changes and transport of client-specific objects and client-independent object changes
If you want to use the settings made by BC-Sets or manually in other systems (other than BW), u201CAutomatic recording of changesu201D and u201CChanges to Repository object and cross-client Customizing allowedu201D is required.
Result
Client administration has been defined to support the installation using Best Practices.
2.3.2 Defining a Logical System for SAP BW (SAP BW)
Use
In this step, you define the logical systems in your distributed system.
Prerequisites
Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Defining a Logical System for SAP BW (SAP BW)
Transaction Code SPRO
IMG Menu SAP Reference IMG  SAP Customizing Implementation Guide  SAP NetWeaver  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System
1. A dialog box informs you that the table is cross-client. Choose Continue.
2. On the Change View u201CLogical Systemsu201D: Overview screen, choose New entries.
3. On the New Entries: Overview of Added Entries screen enter the following data:
Field name Description R/O/C User action and values Note
Log. System Technical Name of the Logical System Enter a name for the logical BW system that you want to create
Name Textual Description of the Logical System Enter a clear description for the logical BW system
4. Choose Save.
If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
If you want to continue with the next activity, do not leave the transaction.
Result
You have created a Logical System Name for your SAP BW client.
2.3.3 Assigning Logical System to Client (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW
Role Menu Assigning Logical System to Client (SAP BW)
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
1. In the view Display View "Clients": Overview, choose Display.  Change
2. Confirm the message.
3. Select your BW client.
4. Choose Details.
5. In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
6. Save the entries and go back.
2.3.4 Opening Administrator Workbench
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Modeling  Administrator Workbench: Modeling
Transaction Code RSA1
1. In the Replicate Metadata dialog box, choose Only Activate.
2. If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
2.3.5 Creating an RFC-User (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Creating RFC User
Transaction Code SU01
SAP BW Menu Tools  Administration  User Maintenance  Users
Then carry out the following steps:
1. On the User Maintenance: Initial Screen screen:
a. Enter the following data:
Field Entry
User RFCUSER
b. Choose Create.
2. On the Maintain User screen:
a. Choose the Address tab.
b. Enter the following data:
Field Entry
Last Name RFCUSER
Function Default-User for RFC connection
c. Choose the Logon data tab.
d. Enter the following data:
Field Entry
Password LOGIN
User type System
e. Choose the Profiles tab.
f. Enter the following data:
Field Entry
Profiles SAP_ALL , SAP_NEW and S_BI-WHM_RFC
g. Choose Save.
Do not change the password of this user as it is used in RFC connections.
2.3.6 Define RFC-USER as default (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Role Menu Define RFC-USER as default (SAP BW)
Transaction Code RSA1
SAP BW Menu Modeling  Administrator Workbench: Modeling
1. On the Administrator Workbench: Modeling screen choose Settings  Global Settings.
2. In the Global Settings/Customizing dialog box choose Glob. Settings.
3. On the Display View u201CRSADMINA Maintenance Viewu201D: Details screen:
a. Choose Display  Change.
b. Enter RFCUSER in the BW User ALE field.
c. Choose Save.
Hope this helps in solving u r problem
Regards
Ramakrishna Kamurthy

JCO getDefaultConnection() not using RFC user from XCM

Hello,
I am writing a custom backend class to call a custom function module in R3 to get some data. As this has to run before the application start page is loaded, I have used a exit before the /b2b/startapp.do is called.
The problem here is that when I am using the getDefaultJCoConnection() method in the backend class which extends the IsaBackendBusinessObjectBaseSAP class, the JCO user is determined as the application user rather than the RFC user which I have configured in XCM. Because of this there is an authorization error as the application user does not have auth to the custom function group.
I have written many other exits in the application and they are all working fine and picking up the RFC user which has relevant authorizations.
Am I missing something here?
Pradeep

Thanks Easwar
stateless was giving me other issues.
I managed to solve the problem with the below code.
ManagedConnectionFactoryConfig mConfig = (ManagedConnectionFactoryConfig) (getConnectionFactory().getManagedConnectionFactoryConfigs().get("JCO"));
Properties props = mConfig.getConnectionDefinition("ISA_COMPLETE").getProperties();
connection = getDefaultJCoConnection(props);
Pradeep

Port A000000016 is not an RFC port

Similar Messages

Maybe you are looking for