CPAcache

Hi..
we have installed PI7.0 and everything works fine .But i have got a doubt according to config doc of XI.With XI 3.0 installation and post installation, we need to create
three Sm59 connection in post installation step
1.AI_DIRECTORY_JCOSERVER
2.AI_RUNTIME_JCOSERVER
3.INTEGRATION_DIRECTORY_HMI
Also LCRSAPRFC and SAPSLDAPI.
My question is that whether the first three is necessary for PI7.0??..becoz it is not mentioned in post installation step for PI 7.0 whereas it is there for XI 3.0
but LCRSAPRFC and SAPSLDAPI has been mentioned.
Moreover when i do a cache refresh in SXI_CACHE..it doesnot thro any error but the same i tired in the URL :http://host:port/CPAcache/refreshmode=full, it doesnot show anything..what is it mean???? how will check the cache refresh....
I do checked in visual administration, SAP XI CPACache in server..but URl is different like http://localhost:5000/.... and so on..
How do i relate this?? please reply to clear this concept
Thanks
Gopal

Moreover when i do a cache refresh in SXI_CACHE..it doesnot thro any error but the same i tired in the URL :http://host:port/CPAcache/refreshmode=full, it doesnot show anything..what is it mean???? how will check the cache refresh....
To refresh the Cache the below URL need to check
<b> http://<hostname>:<J2EE portnumber>/CPACache/refresh?mode=full.</b>
I saw some of the documents in PI7.0 all the post-installation step will configure using Template based-Configuration ...please find the help using below URL
http://help.sap.com/saphelp_nw04s/helpdata/en/14/39084136b5f423e10000000a155106/frameset.htm
Regards,
Venu.

Similar Messages

CPACache will not update

One of our systems fails to update the CPACache when performing a full cache update. The confirmation XML that comes back in the history page begins thus:
<?xml version="1.0" encoding="UTF-8" ?>
- <CacheRefreshError>
<EngineType>AE</EngineType>
<EngineName>af.xd1.rommi</EngineName>
<RefreshMode>C</RefreshMode>
- <GlobalError>
<Message>CPA Cache not updated with directory data.</Message>
<Trace>com.sap.aii.af.service.cpa.impl.exception.CPADirectoryCacheException: Couldn't open Directory URL (http://rommi:50000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.xd1.rommi), due to: HTTP 503: Service Unavailable at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDataFromDirectory(DirectoryAccess.java:382) at
Could anybody please advise how to proceed?

Hi Anthony,
See note: 741214 for CPA cahe update trouble shooting
In Addition check these below links....it might be helpful
/people/sravya.talanki2/blog/2005/12/02/sxicache--ripped-off
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1a69ea11-0d01-0010-fa80-b47a79301290
/people/sravya.talanki2/blog/2005/12/02/sxicache--ripped-off%3Fpage%3Dlast
Thanqs
Biplab

Business system not found in CPACache

Sceinario was working fine before XI system crash. After the system is reestablished the scenario not working. Giving RFC error "Service: SAPESRI not found in CPACache" in R3 system
CPAcache refreshed for dela as well as full
Adapter specific identifiers are fine
SLD cache cleared in IR ID
Business System name is found in CPAcache
error repeated
Business System deleted from SLD. New business system Created. Entire scenario reconstructed. All the above are also fine.
Still error is repeating.
Can anybody give a solution for this problem please?
Regards,
Venkat

Hi Venkat,
The subject of the problem & the problem explanation is varing i.e *Business system not found in CPACache*
However, the problem still lieing with SLD. So, test the SLD and activate the scenario. Also without refreshing CPA cache you will have to perform execution.
Regards
Pothana

Error when executing CPACache mode = full

Hi,
I had error, when executing this CPACache mode = full and delta, I am using this link below:
http://demokl:50100/CPACache/refresh?mode=full.
Full :
Error message =
<?xml version="1.0" encoding="UTF-8" ?>
- <CacheRefreshError>
<EngineType>AE</EngineType>
<EngineName>af.px6.demokl</EngineName>
<RefreshMode>F</RefreshMode>
- <GlobalError>
<Message>Couldn't parse Configuration Data cache update XML string from Directory.</Message>
<Trace>org.xml.sax.SAXException: JavaErrors Tag found in cache update XML. at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataSAXHandler.startElement(DirectoryDataSAXHandler.java:148) at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.startElementEnd(SAXDocHandler.java:146) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1814) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2440) at
Delta :
<?xml version="1.0" encoding="UTF-8" ?>
- <CacheRefreshError>
<EngineType>AE</EngineType>
<EngineName>af.px6.demokl</EngineName>
<RefreshMode>C</RefreshMode>
- <GlobalError>
<Message>CPA Cache not updated with directory data.</Message>
<Trace>com.sap.aii.af.service.cpa.impl.exception.CPADirectoryCacheException: Couldn't open Directory URL (http://demokl:50100/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.px6.demokl), due to: HTTP 503: Service Unavailable at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDataFromDirectory(DirectoryAccess.java:382) at
</Trace>
</GlobalError>
- <GlobalError>
<Message>Confirmation handling failed.</Message>
<Trace>com.sap.aii.af.service.cpa.impl.exception.CPADirectoryCacheException: Couldn't send confirmation, due to: Couldn't access Confirmation URL, due to: HTTP 503: Service Unavailable at
Thank you and Regards
Fernand

Hi,
I already using user PIDIRUSER to execute CPACache full mode, but still unsuccessfull.
Hi Srinivas,
Which parameter that you mention, i couldn't find in the SXMB_ADM Integration Configuration ?
Thank you and Regards
Fernand

Service: not found in CPACache

Hi all,
Service: not found in CPACache
Please suggest a wayout to resolve error.
Regards,
Venkat

visit this forum..its very useful
Cache....schema not available

No authorized after run CPACache refresh

Hi,
I can't do cpacache refresh as follow, it always show "You are not authorized to view the requested resource.", and i have all authorize now.
http://<host:port>/CPACache/refresh?mode=full

Use the XIDIRUSER (PIDIRUSER) to authenticate yourself, it is the only user that is allowed to carry out a CPA Cache Refresh.
The test is successful if you get the message that the cache refresh has been carried out in xyz
milliseconds. Please note that any additional text. e. g. u201CThe XML page cannot be displayedu201D or
u201Cinvalid at the top level of the documentu201D, points at an error.
Troubleshooting:
1) Note 741214 - Troublesh. during cache update of the J2EE CPACache service gives valuable hints
about possible reasons for errors.
2) In case of the error message u201Cinvalid at the top level of the documentu201D the viewing of the source code
of the respective Explorer page gives detailed information about the error.

RfcAFWException: Service: BS_ECC not found in CPACache

Hi everybody,
I have the follow error:
- Error: 2007-07-31 08:53:39 GMT-04:00:
com.sap.aii.rfc.afcommunication.RfcAFWException: Service: BS_ECC not found in CPACache
Does anybody know what is happening?
Thanks,
Renato.

check the below threads
Re: Problem with Http RFC Scenario
RFC adapter as sender
Regards
JJS

CPACache refresh in SXI_CACHE

I do not know what to answer in these two questions:
11. What transaction code is used to refresh the CPA CACHE
a). SXI_CACHE
b). SXMB_CACHE
c). CACHE
d). CACHE can not be refreshed
12. What can be done from SXI_CACHE transaction code
a). CPA cache can be refreshed
b). CPA cache can be restarted
c). None of the above
I am not able to understand If the "Start Delta Cache Refresh"/"Start Full Cache Refresh" in transaction SXI_CACHE refresh also the CPA Cache, or if the only way to refresh the CPACache is the Url:
http://<host>:<port>/CPACache/refresh?mode=delta|full
Please help me. I need an answer.
Thanks,
Antonello

Hi;
Very good question; made me to refresh my memory;
Cache or cash memory to increase / improving overall system speed. Detailed document link
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/1a69ea11-0d01-0010-fa80-b47a79301290?quicklink=index&overridelayout=true
OR
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1a69ea11-0d01-0010-fa80-b47a79301290
Regards,
Prabhu Rajesh

Error installing PCK: Changing the CPACACHE service failed

I am getting an error while installing PCK at the step "Changing the CPACACHE service failed". The log file says "Error while connecting to DB".
My J2EE server is up and running; I can connect to the DB using the MySQLMaxDB -> Database manager using either of the IDs : "control" or "superdba". I am not able to understand what ID is the installation using to connect to the DB. Under sessions I see 7 connections under id "SAPJ2EDB". I even set the default authorizations to connect to the Db.
Would appreciate any help...

Hello Syed!
Did you find a way to solve the problem?
I run into the same problem, the install fails with the same failure message.
Greetz
Sebastian

RFC status in R3 system "Service: SAP_ECC5 not found in CPACache"

Hi experts,
When the above error is noted in R3 . Itested INTEGRATION_DIRECTORY_HMI in Xi server there the following errors came.
Response from Webserver contains Cookies
accept?
I gave response no
For that Response:
Response_line : HTTP/1.1 500 internal server error
connection : Close
server : SAP J2EE engine /7.0
pragma : no-cache
Regards,
Venkat

Hi,
How to resolve this error.
Can any of the settings given below are cause for the error?
HTTP version is set to HTTP/1.0
Compression is set to inactive
Compressed response is set to yes
Accep cookies is set to Yes.
I also would like to know whether response to accept cookies be geves as 'yes' during connection test?
Your response is highly helpful
Regards
Venkat

No entry for adapter engine in CPACache

Hi all,
This is a new installation of PI 7.0. Some of the issues we are facing are:
1) ID -> cache notifications -> unable to determine the name of central AE from SLD
2) Integration Builder -> Admin -> cache overview -> refresh objects fails
3) RWB -> Cache connectivity test for AE fails
4) SXI_CACHE -> goto Adapter Engine Cache -> No Entry under Adapter Engine Connection data cache
5) RWB -> Adapter Monitoring : Only JPR is shown. All the adapters need to be shown as well.
6) SLD -> Technical Systems -> XI -> Integration server does not show the domain name. But all other components have a consistent domain name.
It seems to me that somehow the adapter framework hasnt been registered in the SLD. Do we need to do this manually?
Any help on any of the above issues is greatly appreciated..
thanks!

Hi Lasya,
Please have a look at this thread..
Inconsistence Adapter Framework
cheers,
Prashanth

Error in Full and Delta CPACache refresh.

Hi Experts,
In our production environent we have a SOAP -> XI - > PROXY scenario [Synchronous].
The Consumer of the WebService has reported an error:
500_Internal_Server_Error = SOAP:Server_Server_Error_XIAdapter_ADAPTER.JAVA_EXC
When I checked there are no messages in SXMB_MONI , but when I checked the Cache Refresh History I found that
there was error in both Full and Delta Cache Refresh. But the restart of the XI(Production) server resolved the issue.
The error is as shown below:
<?xml version="1.0" encoding="UTF-8" ?>
- <CacheRefreshError>
<EngineType>AE</EngineType>
<EngineName>af.pxi.su0956</EngineName>
<RefreshMode>F</RefreshMode>
- <GlobalError>
<Message>Couldn't parse Configuration Data cache update XML string from Directory.</Message>
org.xml.sax.SAXException: JavaErrors Tag found in cache update XML. at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataSAXHandler.startElement(DirectoryDataSAXHandler.java:157) at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.startElementEnd(SAXDocHandler.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java(Inlined Compiled Code)) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java(Inlined Compiled Code)) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java(Compiled Code)) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java(Compiled Code)) at javax.xml.parsers.SAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataParser.updateCentralCache(DirectoryDataParser.java:56) at com.sap.aii.af.service.cpa.impl.cache.CacheManager.updateCacheWithDirectoryData(CacheManager.java:871) at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:640) at com.sap.aii.af.service.cpa.impl.servlet.CacheRefresh.process(CacheRefresh.java:104) at com.sap.aii.af.service.cpa.impl.servlet.CacheRefresh.doGet(CacheRefresh.java:53) at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code)) at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code)) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java(Compiled Code)) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Inlined Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java(Compiled Code)) at com.sap.engine.services.httpserver.server.Client.handle(Client.java(Inlined Compiled Code)) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java(Compiled Code)) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java(Compiled Code)) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code)) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code)) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
Can anyone tell me what is the cause of this error and how restart of the XI server resolved the issue?
Thannks,

Guys,
I have deployed the below components and after this repository could not be started which gives the below error.
1000.7.11.10.18.20130529165100
SAP AG
sap.com
SAP_XIAF
1000.7.11.10.11.20130529165100
SAP AG
sap.com
SAP_XIESR
1000.7.11.10.15.20130529165100
SAP AG
sap.com
SAP_XITOOL
We have the same issue. Still the Restart did not solve ths issue.
Can anybody help? We are not able to start the XI Repository.
Our PI components are as below
com.sap.engine.services.ejb3.runtime.impl.refmatcher.EJBResolvingException: Cannot start applicationsap.com/com.sap.xi.repository; nested exception is: java.rmi.RemoteException: [ERROR
CODE DPL.DS.6125] Error occurred while starting application locally and wait.; nested exception is:
        com.sap.engine.services.deploy.container.DeploymentException: Cannot activate endpoint for message-driven bean sap.com/com.sap.xi.repository*xml|com.sap.xpi.ibrep.server.jar*xm
l|CacheRefreshMDB^M
        at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.startApp(DefaultContainerRepository.java:315)^M
        at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.getEnterpriseBeanContainer(DefaultContainerRepository.java:106)^M
        at com.sap.engine.services.ejb3.runtime.impl.DefaultRemoteObjectFactory.resolveReference(DefaultRemoteObjectFactory.java:55)^M
1000.7.11.10.6.20121015232500
SAP AG
sap.com
MESSAGING
Regards
Omkar

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

GRC NF-e 2.0 - Status de Serviço com Erro

Boa noite Srs,
Estamos recebendo um erro no cenário SRVSC_WebAS_Outbound_ServiceStatusCheck.
No NF-e Monitor o Status de Erro é 70 (Error from the authorities). Verifiquei a MONI e encontrei a seguinte mensagem:
/CPACache/refres...
CPA cache refresh (mode=full) successfully executed in 1607 milliseconds.*
Estamos no SLLNFE 16 do XI Content e SAP_APPL 604/07 do ERP; Nossa versão do PI é a 7.0.
Alguém teria alguma dica que pudesse nos ajudar a resolver este erro.
Grato,
Ricardo

Marlo, obrigado por sua resposta!
Refiz novamente todo o cenário de StatusServico, e todos os conditions estão perfeitamente setados, conforme exemplo de São Paulo abaixo:
Condition Homologation: (/p1:nfeStatusServicoNF2/p1:cUF = 35 AND /p1:nfeStatusServicoNF2/p1:tpAmb = 2)
Condition Production: (/p1:nfeStatusServicoNF2/p1:cUF = 35 AND /p1:nfeStatusServicoNF2/p1:tpAmb = 1)
Para todos os outros estados utilizei a mesma regra citada, com exceção ao cenário BATCH, que segui conforme o PDF da nota 1465726 que utiliza o tpEmis (diferente de 3).
Estou fazendo um refresh no sld e reiniciando o server para ver o que acontece...rs
Mais alguma outra dica?
Grato,
Ricardo

Error: Couldn't find delivery channel for message

Hi All,
In our production environment, we sometime get the following error (Channel Audit Log):
2009-01-12 15:08:47 Error Unable to find channel ID
2009-01-12 15:08:47 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Couldn't find delivery channel for message: 496b9e98-9466-0109-e100-8000ac10a218.
2009-01-12 15:08:47 Error The message status set to NDLV.
This particular interface runs around 100 times a day without any issues, however around once or twice a month we get this error.
This is a synchronous interface.
Could be because of number of threads alloted for Synchronous messages in Visual Admin.
Thanks.

Hi XIer
try doing a CPACache Refresh:
Http://<host>:50000/CPACache/refresh?mode=full)
Best regards,
Chris

CPAcache

Similar Messages

Maybe you are looking for