JCO_COMMUNICATION_FAILURE

Can anybody explain the cause of this error and how to fix it?
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error when opening an RFC connection</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>"COMMUNICATION FAILURE" during JCo call. Error when opening an RFC connection</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>

hi Rodel,
Check these similar discussion (Michal and Udo' replies)
Jco System Failure
JCO_COMMUNICATION_FAILURE
regards
Ramesh P

Similar Messages

Error in XI server: JCO_COMMUNICATION_FAILURE in Message Mapping

Hi all,
I am unable to execute even a simple scenario on my server.
The status of the message in moni is random. I get either "Scheduled for outbound processing" in,or the following error(in Request Message Mapping):
SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error opening an RFC connection.</SAP:P1>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>"COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection.</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
I tried deleting the queueus in smq1 and smq2.It did not solve the problem.The test connection for INTEGRATION_DIRECTORY_HMI in sm59 is also working properly. But I don't see any entries for t-RFCs in sm58.
Can anyone tell me what could be the problem?
Regards,
Puloma Chaudhuri.

Hi Puloma,
1. go to TCODE: SWEL and check if you have any errors over there
2. go to TCODE: SWF_XI_CUSTOMIZING
- maintaint runtime environment
- configure RFC destination
and check if the password for user WF-BATCH is correct
Regards,
michal

JCO_COMMUNICATION_FAILURE error in PI7.0

Hello
Till date we have been working with SAP XI 3.0 from last one year, and I have to work with PI 7.0. I creatd a sample scenarion "File to File"in PI 7.0. The sender adapter is picked the file. in SXMB_MONI Error ID showing JCO_COMMUNICATION_FAILURE. Plz suggest me how to resolve this problem.
Thanks
san

Hello San,
Your AI RUNTIME JCOSERVER and AI DIRECTORY JCOSERVER (names - not exact I think) should exist at SM59 of your ABAP stack as well as under JCORFC PRovider in Visual Admin.
Go to the Post isntall steps of XI 3 Install guide (most of the steps are relevant for PI7 also) (page 31 onwards) and you will have all the necessary details. There should be two more RFC destinations SAPSLDAPI adn LCRSAPRFC alongwith the above two.
However the other two are for communicating with SLD mainly.
Hope this helps.
Thanks,
Bhaskar

Mapping Error :JCO_COMMUNICATION_FAILURE

Hi All,
Scenario: File ->XI->File
I am getting following error in Mapping (in Runtime)
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error opening an RFC connection.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>&quot;COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection.</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
This is a simple Message Mapping. Before this error occurs the message is going to Queue with "Running Status" But it never ends.
When I restart the Queues , it goes to SYSFAIL status with the error "XI Error JCO_COMMUNICATION_FAILURE.MAPPING: Queue"
Can anybody come accross this situation ?
Is it because of some Java components are not running ?
Thanks in advance,
Regards,
Moorthy

Hi,
>>>>Can anybody come accross this situation ?
of course:)
>>>Is it because of some Java components are not running ?
no, it's rather because of memory problems + RFC cache
but just have a look at our previous answers
(recreating RFC dest + Udo's answer)
Jco System Failure
Regards,
michal

Reg:JCO_COMMUNICATION_FAILURE

Hi all,
I am getting this error while trying to excecute one IDOC to Proxy interface.Can anyone please let me know the solution?
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error when opening an RFC connection</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>"COMMUNICATION FAILURE" during JCo call. Error when opening an RFC connection</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>

Hi,
can you check whether your SAP Java stack is available ?
if so, check whether if you AI_JCO_RUNTIME config properly, e.g., program id correct, Gateway correct, same program id on java side ?
Cheers,
Aaron

Getting error "JCO_COMMUNICATION_FAILURE"

hi Friends,
I am working with file to idoc & idoc to file scenario
in both the cases i am getting same error in SXMB_MONI
ERROR="JCO_COMMUNICATION_FAILURE".
solutions will be appreciated.
Regards,
RaviKiran.

try a follow up on these threads ... these have various solutions .. hope something might work out for you
JCO_COMMUNICATION_FAILURE
Error in XI server: JCO_COMMUNICATION_FAILURE in Message Mapping

JCO_COMMUNICATION_FAILURE - CPI-C errors

Hi,
I'm getting some errors in XI but not always, I think it's when the server is on heavy load:
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error opening an RFC connection.</SAP:P1>
In sm21, I see:
14:45:55 RD S23 Connection to CPI-C client 351 was closed
14:45:55 RD S74 > Partner LU name:
14:45:55 RD S0R > Host: r1n0v3
14:45:55 RD S0I > Partner TP Name: jlaunch
14:45:55 DIA 003 700 SAPJSF R49 Communication error, CPIC return code 020, SAP return code 223
14:45:55 DIA 003 700 SAPJSF R5A > Conversation ID: 28232929
14:45:55 DIA 003 700 SAPJSF R64 > CPI-C function: CMSEND(SAP)
14:45:55 RD S23 Connection to CPI-C client 080 was closed
14:45:55 RD S74 > Partner LU name:
14:45:55 RD S0R > Host: r1n0v3
14:45:55 RD S0I > Partner TP Name: LCRSAPRF
14:45:55 DIA 000 700 BERNIER_Y R49 Communication error, CPIC return code 020, SAP return code 223
14:45:55 DIA 000 700 BERNIER_Y R5A > Conversation ID: 30118701
14:45:55 DIA 000 700 BERNIER_Y R64 > CPI-C function: CMSEND(SAP)
14:46:27 DIA 000 700 BERNIER_Y R49 Communication error, CPIC return code 002, SAP return code 679
14:46:27 DIA 000 700 BERNIER_Y R64 > CPI-C function: CMINIT(SAP)
14:46:27 DIA 000 700 BERNIER_Y R49 Communication error, CPIC return code 002, SAP return code 679
14:46:27 DIA 000 700 BERNIER_Y R64 > CPI-C function: CMINIT(SAP)
14:46:35 DIA 000 700 BERNIER_Y R49 Communication error, CPIC return code 002, SAP return code 679
14:46:35 DIA 000 700 BERNIER_Y R64 > CPI-C function: CMINIT(SAP)
Any idea? How can I fix those CPI-C errors?
Rgds,
Yves

Hi Yves Bernier ,
ABAP stack and JAVA stack makes communicattion Through JRFC using JCO, for this dedicated connections are defined. When communication takes plcae this calls JCo and if that time resource is engaged with another call and it cann not be assigned to the current call then JCO FAILURE ERROR occurs
For this recomended that you shoyuld increase your maximum no of connections (SAP recomonded 300) but you may increase this according to your requirement.this may solve your problem
For CPIC error codes follow this note.
Note 63347 - List: CPIC error codes
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=63347&nlang=EN&smpsrv=https%3a%2f%2fwebsmp102%2esap-ag%2ede
regards
Sandeep
IF helpful kindly reward points

MAPPING JCO_COMMUNICATION_FAILURE (SOAP to RFC scenario)

Hi,
Our system is PI 7.1 EHP1 and the scenario is to SOAP to RFC (Synchronous). I have imported the RFC into ESR and used it as data type for Outbound interface for SOAP.
Initially i havent created any mapping because all Interface fields are same (name and type) with RFC because i have used RFC as data type. When we have tested the integration via SOAPUI we have seen that the request message wasn't transferred to RFC but the response was transferred from RFC to SOAP response. Could it be a bug? or is it normal behaviour?
Later, i have created a graphical mapping without any data conversion etc.. It is just mapping. This time it transferred the request and response as well.
When we have started stress test on a PI system (6000 SAPS), the PI JAVA stack started to use %100 of CPU. We have processed 100 message per minute. After 20 minutes, Java stack of PI has crashed and restarted.
Our plan is to process message more then this test numbers. Possibly it is approx 400 message per minute.
I have found below errors on RWB (approx 250 message have below errors).
How this high CPU consumption can be resolved?
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=67</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>"COMMUNICATION FAILURE" during JCo call. Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=67</SAP:Stack>
</SAP:Error>
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>
<SAP:P1>connection to partner 'loopback:0' broken / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 th</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>"SYSTEM FAILURE" during JCo call. connection to partner 'loopback:0' broken / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 th</SAP:Stack>
</SAP:Error>
Kind regards,
Altuğ Bayram

Hi,
Connection between ABAP and JAVA has been broken...thats the reason for the JCO_COMMUNICATION Error
you need to either restart the java or have a look at the RFC Connection JCO_AI_CONNECTION...
re you making use of AAE for this scenario..which can improve the performance than using classic scenario.
performance depends on the hardware of the server also...
Check the sizing Guide of the PI 7.1 on SDN.
Check the below link it may help you..
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f0b96675-87cf-2c10-b489-dee0ac03f782
HTH
Rajesh

JCO_COMMUNICATION_FAILURE Error at message procesing

Hi all,
At a productive XI server we are having a lot of errors in message procesing.
Please take a look:
<SAP:Error xmlns:SAP=" http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustU
nderstand="">
<SAP:Category>XIServer
</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE
</SAP:Code>
<SAP:P1>Error opening an RFC connection.
</SAP:P1>
<SAP:P2/>
<SAP:P3/>
<SAP:P4/>
<SAP:AdditionalText/>
<SAP:ApplicationFaultMessage namespace=""/>
<SAP:Stack>&quot;COMMUNICATION FAILURE&quot; during JCo call. Error opening an RFC connection
</SAP:Stack>
<SAP:Retry>A
</SAP:Retry>
</SAP:Error>
I taked a look at: JCO_COMMUNICATION_FAILURE
but i still can't find the problem.
Thanks in advance for your help,
Regards

Hi,
If you want to test your Message Mapping in the IR, then you will not get this JCO error.
You will get this error if you are doing an end to end run of your interface and the communication between the JAVA and ABAP stack is not available. If you are doing an end to end test and still facing this issue ,like mentioned, ask your BASIS team to restart the server. ( out of 10 times this error will vanish when you test your interface after the restart,.
Regards,
Bhavesh

Error in Directory Cache Update

Hi,
because we changed from two SLDs (PROD & DEV) to one (DEV) we did all changes like given in note 720717.
Everything seems to run fine except the Adapter Engine - ok parts of it.
When checking the Cache-Infos in Integration Directory we get following error in Integration Server (Central Adapter Engine). What do we need to do?!
br
com.sap.aii.ib.server.abapcache.CacheRefreshException: Unable to find an associated SLD element (source element: SAP_XIIntegrationDirectory, [CreationClassName, SAP_XIIntegrationDirectory, string, Name, directory.px1.sapru03, string], target element type: SAP_XIIntegrationServer)
 at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:483)
 at com.sap.aii.ibdir.server.abapcache.content.CacheCPA.addContent(CacheCPA.java:154)
 at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:388)
 at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:326)
 at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.processHTTPRequest(CacheRefreshRequest.java:145)
 at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.handleHTTPRequest(CacheRefreshRequest.java:103)
 at com.sap.aii.ibdir.web.abapcache.HmiMethod_CacheRefresh.process(HmiMethod_CacheRefresh.java:67)
 at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
 at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
 at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
 at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:259)
 at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
 at com.sap.aii.utilxi.hmis.web.workers.HmisExternalClient.doWork(HmisExternalClient.java:75)
 at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
 at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
 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:390)
 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(AccessController.java:207)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Hi,
Hereu2019s a list of common errors/problems in SAP XI and their possible resolutions. This Guide will help you troubleshoot your integration scenarios in SAP XI/PI. This is in no way an exhaustive list. You can add your points/ideas to this list. Please feel free to post your inputs using the comments form at the end of this article.
Cache Update Problems
Use transaction SXI_CACHE to update the Integration Directory cache. Alternatively, you can use the following URLs to update the CPA cache. Use XIDIRUSER to refresh the cache.
For complete cache refresh - http://<hostname>:<port>/CPACache/refresh?mode=full
For delta cache refresh - http://<hostname>:<port>/CPACache/refresh?mode=delta
If this does not solve the issue, check transaction SLDCHECK to ensure that connection to SLD is available. If the connection fails, check the configuration in the transaction SLDAPICUST. Make sure that the password maintained is correct and the maintained service user is not locked.
Now in the Integration Repository go to Environment u2192 Clear SLD Data Cache. Also go to Integration Directoy and clear the cache using menu Environment u2192 Clear SLD Data Cache.
Open the XI Start Page and click on Administration. On the Repository tab, choose Cache Overview. Refresh the cache using the buttons/icons on the right. Use XIDIRUSER to refresh the cache. Carry out cache refresh in the same way on the Directory and Runtime tabs.
If you are facing cache update problems in your BPM (say you have modified the BPM, but when executed old version of the BPM is picked up instead of the new one), run the transaction SWF_XI_CUSTOMIZING and press F9 carry out automatic BPM/Workflow Customizing.
Routing Errors
NO_RECEIVER_CASE_BE or NO_RECEIVER_CASE_ASYNC
This means no receiver could be found. Check your Receiver Determination. Activate and update cache. Asysnchronous messages can be manually restarted.
TOO_MANY_RECEIVERS_CASE_BE
More than one receiver found. Check your ID configuration to ensure that there is exactly one receiver for the synchronous message. Multiple receivers for synchronous interfaces are not permitted.
Mapping Errors
JCO_COMMUNICATION_FAILURE
Check whether RFC destination AI_RUNTIME_JCOSERVER is correctly configured
NO_MAPPINGPROGRAM_FOUND
Ensure that mapping program exists and is activated. If it exists then update the cache.
EXCEPTION_DURING_EXECUTE
This error occurs due to erroneous XML formatting. Check your mapping program and ensure that you supply valid input data.
Messages stuck in queues
Check the queues using transactions SMQ1 (outbound)/SMQ2 (inbound). Resolve the displayed errors. You can cancel the messages from SXMB_MONI. Execute LUW if necessary and avoid deleting entries manually.
Conversion Errors
Unable to convert the sender service XXXX to an ALE logical system
This error occurs in case of scenarios with IDoc adapters. Whenever you use business systems, make sure that the corresponding logical system name is maintained in the SLD.
Open your business system in the Integration Directory. Switch to Change mode. Access the menu path Service u2192 Adapter Specific Identifiers. Click the button that says u2018Compare with System Landscape Directoryu2019 and chose Apply. Save and activate your change list.
In case of business services, you can manually type a logical system name in the Adapter Specific Identifiers if required. This name should match the corresponding logical system name defined in the partner SAP systemu2019s partner profiles.
Errors on the outbound side
Sometimes the link between SAP XI and the target system (say ERP) goes down and messages fail on the outbound side. It may not be possible to restart them from using RWB or the transactions like SXI_MONITOR/SXMB_MONI. In such cases, you can follow the procedure outlined in the following article - Dealing with errors on the outbound side.
Refer this article:
http://help.sap.com/saphelp_nwpi71/helpdata/en/0d/28e1c20a9d374cbb71875c5f89093b/content.htm
Refer this portal
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/ep/pointers%2bfor%2btroubleshooting%2bportal%2bruntime%2berrors
Regards,
Suryanarayana

SCAN não retorna status do serviço

Bom dia,
Desde 14/08/2011 às 08:05:56 o nosso tipo de emissão SCAN não está retornando STATUS de ativo, e também não é realizada a consulta do status do mesmo.
Dei uma olhada no GRC/PI/Java/ECC... e aparentemente está tudo ok
Quando o SCAN parou pela primeira vez, deu o seguinte erro:
PARSE_APPLICATION_DATA Error during XML => ABAP conversion: Response Message; CX_ST_MATCH_ELEMENT in /1SAI/TXS2731B33DE5F5A8813C20 Line 268 Elem.'nfeStatusServicoNFResponse2' esperado
Pesquisando sobre o erro, achamos 2 trheads:
http://forums.sdn.sap.com/click.jspa?searchID=73768752&messageID=10193658
http://forums.sdn.sap.com/click.jspa?searchID=73768752&messageID=10151927
Elas sugerem a aplicação das notas abaixo:
1501345 - Xi runtime: Manifest
1522630 - Xi runtime: Payload ignored due to parsing error
1162160 - CX_ST_MATCH_ELEMENT in XML Inbound processeing
Inclusive um dos usuários comenta que após aplicada a 1522630 o problema foi resolvido... (Mas não sei se isso irá funcionar)
Outro check que realizei foi do erro retornado no status do serviço do SCAN agora, e o GRC retorna o seguinte erro:
MAPPING.JCO_COMMUNICATION_FAILURE "COMMUNICATION FAILURE" during JCo call. Error when opening an RFC connection
Pesquisando sobre o erro, encontrei algumas sugestões:
1) Alguns sugerem a exclusão da conexão RFC AI_RUNTIME_JCOSERVER para TCP/IP (SM59) no GRC e criar novamente... mas não sei se isso iria funcionar...
2) Em outras pesquisas, alguns falam que a Conexão entre ABAP e JAVA foi quebrada... isso é a razão para o erro JCO_COMMUNICATION... e a sugestão é reiniciar o Java...
3) Em outra pesquisa: Quando há muitas mensagens a serem processadas simultaneamente. O número padrão de processos paralelos em VisualAdmin -> JCO Provider RFC -> AI_RUNTIME_) e ver se isso ajuda.
Obs.: À alguns dias, tivemos um problema que ocorreu com a SEFAZ-GO, a mesma colocou nossa faixa de IP's em uma Blacklist (ainda não sabemos porque) e daí ela nos retornava que estava "fora do ar". Será que poderia ser isso? Como posso checar isso?
O nosso S.P. é o:
SLL-NFE 100 0018 SAPK-10018INSLLNFE xNFE 1.0
Alguém poderia nos auxiliar? Pois isso não gera impacto em nossos processos desde que a SEFAZ (GO/PR/SP/MT) não fique inativa, pois caso isso ocorra o nosso processo de emissão de NF-e em SCAN não irá funcionar e a emissão de NF-e irá parar.
Qualquer dúvida estou à disposição.
Edited by: MATEUS PARREIRA GUIMARÃES on Sep 1, 2011 7:12 PM
Edited by: Fernando Ros on Sep 2, 2011 10:24 PM - trocado code por quote para melhor visualizaçã

Boa tarde a todos!
Pessoal incluindo mais informações as já enviadas pelo Mateus; quando fazemos um check pela SXI_monitor esta
retornando sempre o mesmo retorno:
Qualquer dica ou nota agradecemos,
Pamplona
CENTRAL
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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>SystemError</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>8AB8CC05-D44B-11E0-8D74-000000729692</SAP:MessageId>
<SAP:RefToMessageId>E0D44B74-1BE5-7BF1-975B-0024E8437829</SAP:RefToMessageId>
<SAP:TimeSent>2011-09-01T03:36:13Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">SEFAZ_2_SCAN</SAP:Party>
<SAP:Service>Producao</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/NFE/006">SRVSC_nfeStatusServicoNFSoapIn_SYNC_IB</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty" />
<SAP:Service>GRPCLNT200</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/NFE/006">SRVSC_nfeStatusServicoNF_SYNC_OB</SAP:Interface>
</SAP:Receiver>
<SAP:Interface namespace="http://sap.com/xi/NFE/006">SRVSC_nfeStatusServicoNFSoapIn_SYNC_IB</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SystemErrorAckRequested="true" SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTPEXCEPTION - HTTP 403 Forbidden----

Error message "com.sap.aii.af.ra.ms.api.DeliveryException: "

Hi Team,
Created a simple file2file scenarion successfully. Unable to pick the file from Sender directory to Receiver Directory.
Checked from monitoring the Communication Channel.
Error message shown for sender communication channel as below:
Communication Channel Status   Short Log                                Control Data   Party Service           Adapter Type Direction
sen_cc                 Red ball Processing Errors In the Last 30 Seconds Manually             kanchuf2f_sen_bs   File         Sender
Line 1 / 1
By selecting the sender communication channel "sen_cc", below is the node details given.
Processing Details for Cluster Node Server 0 1_54295
Type
Time Stamp         Message ID                           Explanation
12/3/08 8:20:01 AM 45f841be-a421-43bd-235a-c7ad19b0aec8 Retry interval started. Length: 60.0 seconds
12/3/08 8:20:01 AM 45f841be-a421-43bd-235a-c7ad19b0aec8 Error: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:JCO_COMMUNICATION_FAILURE:
By clicking on the first Message ID, The message says successful upto some point and give error says JCO COMMUNICATION FAILURE and RFC issue.
Below is the information provided in detail.
Audit Log for Message: 45f841be-a421-43bd-235a-c7ad19b0aec8
Time Stamp          Status Description
03.12.2008 08:20:00 Success Channel sen_cc: Send binary file "f:\xi_file\sender\f2fmap.xml". Size 210 with QoS BE
03.12.2008 08:20:00 Success Application attempting to send an XI message synchronously using connection AFW.
03.12.2008 08:20:00 Success Trying to put the message into the call queue.
03.12.2008 08:20:00 Success Message successfully put into the queue.
03.12.2008 08:20:00 Success The message was successfully retrieved from the call queue.
03.12.2008 08:20:00 Success The message status set to DLNG.
03.12.2008 08:20:01 Error Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:JCO_COMMUNICATION_FAILURE:.
03.12.2008 08:20:01 Error Transmitting the message using connection http://sitaserv33:8001/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:JCO_COMMUNICATION_FAILURE:.
03.12.2008 08:20:01 Error The message status set to FAIL.
03.12.2008 08:20:01 Error Returning to application. Exception: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:JCO_COMMUNICATION_FAILURE:
Page 1 / 2
I think this could be the problem with some basis related settings, I am not sure what exactly the issue with.
Any idea what exactly the error is talking about please do help me in finding the solution to thresolve this error message.
Regards,
Venkat Ramana K

Hi Carlos,
Thank you for the quick information.
Followed all the steps and also basis person from onsite restarted the XI server.
Now, I am able to log onto XI with the login Id but, when I give Tr Code: SXMB_IFR, unable to open the browser that shows Integration Builder.
Getting the error message.
*500   Internal Server Error*
                                                                                *SAP J2EE Engine/7.00*
**Exception**
*An internal error occurred. Contact you XI administrator*
*Unable to read configuration data (ExchangeProfile/aii.properties)*
Error Details, Error History, Build Info, Generic Application Info
Regards,
Venkat Ramana K

Getting an error while transfer the data SAP XI to SAP R/3

Hello Everyone,
I am getting an error
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error opening an RFC connection.</SAP:P1>
when i was transfing the data to SAP R/3.
But i found the error In SM59 , TCP IP connections ,
AI_DIRECTORY_JCOSERVER , AI_RUNTIME_JCOSERVER and SAPSLDAPI are failed to connect.
ERROR program AI_DIRECTORY_SXI not registered
LOCATION SAP-Gateway on host starxi / sapgw00
DETAIL TP AI_DIRECTORY_SXI not registered
COMPONENT SAP-Gateway
COUNTER 15736
MODULE gwr3cpic.c
LINE 1621
RETURN CODE 679
SUBRC 0
RELEASE 640
TIME Sun Oct 12 16:23:18 2008
VERSION 2
How to register these program?
Can any one please help me.
Thanks
Subash.

Hi,
Check this XI Configuration guide:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ac6de690-0201-0010-54ac-8923089dcc97
Also check this thread on XI installation and post-installation:
Re: XI INSTALLATION and POSTINSTALLATION
Regards,
Subhasha

Getting an error in while transfer the data to SAP

Hello Everyone,
I am getting an error
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error opening an RFC connection.</SAP:P1>
when i was transfing the data to SAP R/3.
But i found the error In SM59 , TCP IP connections ,
AI_DIRECTORY_JCOSERVER , AI_RUNTIME_JCOSERVER and SAPSLDAPI are failed to connect.
ERROR program AI_DIRECTORY_SXI not registered
LOCATION SAP-Gateway on host starxi / sapgw00
DETAIL TP AI_DIRECTORY_SXI not registered
COMPONENT SAP-Gateway
COUNTER 15736
MODULE gwr3cpic.c
LINE 1621
RETURN CODE 679
SUBRC 0
RELEASE 640
TIME Sun Oct 12 16:23:18 2008
VERSION 2
How to register these program?
Can any one please help me.
Thanks
Subash.

Did you create the entry for this in the J2EE visual admin -> Cluster -> Server -> Services -> JCo RFC Provider ?

Error in SOAP to file scenario

Hey guys
i m doing a SOAP to File scenario and getting the following error.
<SAP:Stack>"COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection.</SAP:Stack>
any idea where should i look ?
thanx
ahmad

Hey
i m still getting a red flag in MONI,the error is
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error opening an RFC connection.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>"COMMUNICATION FAILURE" during JCo call. Error opening an RFC connection.</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
i checked my mapping by copyin payload from MONI,its working fine.
thanx
ahmad

JCO_COMMUNICATION_FAILURE

Similar Messages

Maybe you are looking for