on 06-19-2007 7:36 PM
Hi All,
I request you to kinldy help me out of the below problem. I have a scenario RFC as a sender and I have gone through the weblog
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
1. Function module is existing in SAP and also successfully imported in XI
2. Create RFC destination with TCP/IP (T) connection
below is the code of my report
REPORT z_xi_tivoliinterface_test.
DATA: i_zxi_test TYPE STANDARD TABLE OF zxi_test,
i_bapiret2 TYPE STANDARD TABLE OF bapiret2,
i_BAPIATTYPE type standard table of BAPIATTYPE.
CALL FUNCTION 'ZRFC_XI_GET_PERSONAL_INFO'
DESTINATION 'SAPSXI'
EXPORTING
pernr = '645056'
TABLES
i_pernr_info = i_zxi_test
i_error_tab = i_bapiret2.
WRITE : 'test'.
commit work.
when I execute the report i got the below error
Error opening an RFC connection.
Component............ "SAP-Gateway"
Place................ "SAP-Gateway on host sxxxxxx / syyyyyy"
Version.............. 2
Error code........... 679
Error text........... "program SHRRFC_SXI not registered"
Description.......... "TP SHRRFC_SXI not registered"
System call.......... " "
Module............... "gwr3cpic.c"
Line................. 1609
Please let me know how to register by program SHRRFC_SXI.
Regards
Dhill
Dhil,
The sender RFC comm channel has to be active and must be registered with the same Program ID. Please check for this.
Best regards,
raj.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Raj,
Yes I check the Sender RFC comm channel is active and also I used the same Program ID. I also refreshed in SXI_CACHE. But still having the same problem.
When I checked in forum they asked to refer the SAP Note 730870 but still not able to get the step how to register. Please let me know how to do it.
Regards,
Dhill
Dhil,
I don't know have u checked the note or not. If u haven't kindly follow the beloe notes and reply back the results.
<b><i>To check which Program IDs are registered at the SAP Gateway the gateway-monitor can be used via transaction SMGW. Select Goto -> Logged on Clients. Registered RFC-Servers have a System-Type of 'REGISTER_TP'. The Program ID of the registered RFC-Servrer can be found in column 'TP name'. Unfortunately the list within SMGW only shows the truncated version of the Program ID (column 'TP name'). To get the full name, the details of an entry have to be selected. As an alternative the report RSGETALL_REG_SERVERS can be executed in transaction SE38. The output of this report will show the full names of the Program ID in column 'Registered PROGID'. This functionality is also available in the function module GWY_READ_CONNECTED_SYSTEMS which can be executed in transaction SE37.</i></b>
Best regards,
raj.
Hi Raj,
I followed the same step which was given in blog /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
<b>To get the full name, the details of an entry have to be selected. As an alternative the report RSGETALL_REG_SERVERS can be executed in transaction SE38. The output of this report will show the full names of the Program ID in column 'Registered PROGID'.</b>
I used the same Program ID in RFC destination (TCP/IP connection) and also in Communication channel but stil getting the same error.
Regards,
Dhill
Hi,
Check out the RFC destination created in the SAP R/3 system. Check the Case Sensitive part of the Program ID. Test the RFC connection
Create the Sender Agreement again.. And activate with correct credentials.. Then check the CommunicatioN Channel monitoring ... to make sure that Adapter is active and the status is green.
Also executing a CPA Cache Refresh and RFC adapter metadata refresh at J2EE engine level will help u.
Hope this helps
Rgds,
Moorthy
Hi,
I tried with all the step as specified but still i am getting the error as
when I tried executing the function module in SAP system i got the error as
<b>Error opening an RFC connection.</b>
and also in <b>RFC communication channel</b> I received the error as below
Sender channel 'CC_RFCSend' for party '', service 'SHRBS210'
Error can not instantiate RfcPool caused by:
com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcServerPool:com.sap.aii.af.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=xisand.dx.deere.com SYSNR=02 GWHOST=xisand.dx.deere.com GWSERV=sapgw02 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner not reached (host 204.54.190.16, service sapgw02)
TIME Wed Jun 20 11:49:26 2007
RELEASE 640
COMPONENT NI (network interface)
VERSION 37
RC -10
MODULE nixxi_r_mt.cpp
LINE 8677
DETAIL NiPConnect
SYSTEM CALL connect
ERRNO 79
ERRNO TEXT A remote host refused an attempted connect operation.
COUNTER 1
Regards,
Dhill
Hi Raj,
We have used the Activation type option button as Registered Server Program only but currently when I execute the test connection for RFC Destination I am getting the below error
<b>Error opening an RFC connection</b>
Initially it was working fine. Please let me know where went wrong. I have given
in rfc destination as
Connectio type TCP/IP
checked the checkbox Registered Server Program
Program ID : ProgramID
Gateway host: saphr server details (not xi)
Gatewayservice : saphr service details (not xi)
Regards,
dhill
Hi,
Thank now I recreated everthing but still i am getting the error when I execute the report in SAP as below
senderAgreement not found: lookup of binding via CPA-cache failed for
Error Analysis
An error occurred when executing a REMOTE FUNCTION CALL.
It was logged under the name "RFC_EXTERNAL_ABORT"
on the called page.
Please let me know where I went wrong
Regards,
Dhill
Hi Raj,
Thank you very much for sending me the thread where I found one valid point that
>1) A common mistake is to create a Message Interface in the IR (Design) for >RFC and IDoc senders and point the sender agreement to this Message Interface >which won't work. The Sender Agreement should be setup as follows:
>Service: SAP Business System
>Interface: RFC name
>Namespace: urn:sap-com:document:sap:rfc:functions
I also given in the same way the one which I created in IR as Asynchronous outbound interface for RFC. I have gone throught the weblog as Krisha told.
Now I am able to see responce in XI system with error message as below
<b>In SAP system i got error like</b>
"call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:
<b>In XI System I got the error as</b>
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Receiver Identification
-->
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>56357870-20B0-11DC-89CB-2E759B0202A0</SAP:MessageId>
<SAP:TimeSent>2007-06-22T11:04:24Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>SHRBS210</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">ZRFC_XI_GET_PERSONAL_INFO</SAP:Interface>
</SAP:Sender>
<SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">ZRFC_XI_GET_PERSONAL_INFO</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2007-06-22T11:04:24Z" wasRead="false">
<SAP:Engine type="AE">af.sxi.xisand</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
<SAP:MessageId>56357870-20B0-11DC-89CB-2E759B0202A0</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
- <SAP:Hop timeStamp="2007-06-22T11:04:25Z" wasRead="false">
<SAP:Engine type="IS">is.01.xisand</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>56357870-20B0-11DC-89CB-2E759B0202A0</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20070622</SAP:Date>
<SAP:Time>060425</SAP:Time>
<SAP:Host>xisand</SAP:Host>
<SAP:SystemId>SXI</SAP:SystemId>
<SAP:SystemNr>01</SAP:SystemNr>
<SAP:OS>AIX</SAP:OS>
<SAP:DB>DB6</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>023</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>XIAFUSER</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>000</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId>5BC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineService>PLSRV_RECEIVER_DETERMINATION</SAP:PipelineService>
<SAP:QIdInternal />
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="210">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID" />
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>229</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>2931</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>229</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>AENGINE</SAP:AdapterInbound>
<SAP:InterfaceAction>INIT</SAP:InterfaceAction>
<SAP:RandomNumber>00</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
<SAP:Sender_Agreement_GUID>5E994FDFA1253F559B55E9DC3433725D</SAP:Sender_Agreement_GUID>
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="xisand">20070622110424.776903</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="xisand">20070622110424.799521</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="xisand">20070622110424.800211</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="xisand">20070622110425.462062</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="xisand">20070622110425.463351</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:DynamicConfiguration xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Record namespace="http://sap.com/xi/XI/System/RFC" name="ppActivated">false</SAP:Record>
</SAP:DynamicConfiguration>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>;
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Party normalization: receiver</Trace>
<Trace level="1" type="T">Receiver scheme external = XIParty</Trace>
<Trace level="1" type="T">Receiver agency external = http://sap.com/xi/XI</Trace>;
<Trace level="1" type="T">Receiver party external =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- <!-- ************************************
-->
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = SXI</Trace>
<Trace level="1" type="T">client = 210</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2007-06-22T11:04:25Z CST</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- <!-- ************************************
-->
<Trace level="1" type="T">Message-GUID = 5635787020B011DC89CB2E759B0202A0</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = BE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="1" type="T">No Relation found - accept given Receivers.</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">Message type BEST EFFORT. -> No determination</Trace>
<Trace level="1" type="T">Set interface action INIT into MAST</Trace>
</Trace>
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <SAP:Payload xlink:href="cid:payload-5637c26020b011dc8e762e759b0202a0@sap.com">
<SAP:Name>MainDocument</SAP:Name>
<SAP:Description />
<SAP:Type>Application</SAP:Type>
</SAP:Payload>
</SAP:Manifest>
</SOAP:Body>
</SOAP:Envelope>
<b>In communiation channel monitoring i got error like but still it is in green status</b>
Receiver channel 'CCRFCRec' for party '', service 'SHRBS210' (internal name 'RfcClient[CCRFCRec]')
Client data: {jco.client.lang=EN, jco.client.snc_mode=0, jco.client.client=210, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=skxxxxx, jco.client.sysnr=02, jco.client.ashost=hrsand.dx.dxxxx.com}
Repository data: {jco.client.lang=EN, jco.client.snc_mode=0, jco.client.client=210, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=skxxxxx, jco.client.sysnr=02, jco.client.ashost=hrsand.dx.dxxxx.com}
Current pool size: 0, maximum pool size : 1
Channel History
- Error: 2007-06-21 03:01:20 CDT: Message processed for interface ZRFC_XI_GET_PERSONAL_INFO: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling ZRFC_XI_GET_PERSONAL_INFO in remote system (RfcClient[CCRFCRec]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: User SKxxxxx has no RFC authorization for function group ERFC .
- Error: 2007-06-21 02:56:20 CDT: Message processed for interface ZRFC_XI_GET_PERSONAL_INFO: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling ZRFC_XI_GET_PERSONAL_INFO in remote system (RfcClient[CCRFCRec]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: User SKxxxxx has no RFC authorization for function group ERFC .
- Error: 2007-06-21 02:51:20 CDT: Message processed for interface ZRFC_XI_GET_PERSONAL_INFO: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling ZRFC_XI_GET_PERSONAL_INFO in remote system (RfcClient[CCRFCRec]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: User SKxxxxx has no RFC authorization for function group ERFC .
<b>In message Monitoring i got the error as</b>
Engine All
Status System Error
Repeatable No
Cancelable No
Start 22.06.2007 06:45:37
End 22.06.2007 06:45:39
Sender Party
Sender Service SHRBS210
Sender Interface urn:sap-com:document:sap:rfc:functions
ZRFC_XI_GET_PERSONAL_INFO
Receiver Party
Receiver Service
Receiver Interface
Quality of Service Best Effort
Error Category
Error Code
Message 184453A120B611DCC18C2E759B0202A0
Reference
By see all the above I notice that the sender and receiver system r same. I don't know how it is coming like that because in receiver agreement I have given correctly. I check and cleared the cache also.
Please help me out is there any other problem with this r let me know if you require more details.
Regards,
Dhill
Hi, I've the same problem. I need to confifgure the SSO Logon Ticket and I created the RFC with the name RFC_TO_PORTAL and some erros appear:
#1.#0018714E4A140061000001A400006AD9000433CDE530F9F7#1182859312810#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.Bundle.initialize()#Administrator#4653####b3f6de7023dc11dcb7ca0018714e4a14#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain###com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=my ECC server SYSNR=01 GWHOST=<my ECC server> GWSERV=sapgw01 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner '<my ECC server>:sapgw01' not reached
TIME Tue Jun 26 09:01:53 2007
RELEASE 700
COMPONENT NI (network interface)
VERSION 38
RC -10
MODULE nixxi.cpp
LINE 2768
DETAIL NiPConnect2
SYSTEM CALL connect
ERRNO 239
ERRNO TEXT Connection refused
COUNTER 1
Any idea what's the problem?
Thanks !!
User | Count |
---|---|
84 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.