Integration Directory - Cache Notifications Error!!

Hi ,
When i try to select "Cache Notifications" in directory i am facing this error below.
Unable to determine the name of the central Adapter Engine from the System Landscape Directory at this time. Notifications to the central Adapter Engine are therefore listed using the technical name of the Adapter Engine. This is usually structured as follows: af.<SAP System ID>.<Name of application server>
I can see in SLD -> technical system -> exchange infrastructure, the entry for Integration Directory is missing. I ve applied note 764176 , but it is not helping. Similarly the entry for RWB is also missing here.
ve checked in SLD -> Admin -> Content Manitenance and the assocations are missing for IR & RWB. I beleive these errors are closely related. ve chked exchange profile XIDIRUSER & XIRWBUSER pwds , chked the roles , they are the same as our DEV / QA envionments.
Can anyone pls point what am i missing here
Thanks
Saravana

Hi Saravana,
About the roles for XIRWBUSER...you can check the same in the ABAP stack...go to transaction SU01 and check the Roles attached...it should have the following entries...
SAP_SLD_CONFIGURATOR
SAP_XI_RWB_SERV_USER
SAP_XI_RWB_SERV_USER_MAIN
These should be sufficient as it is working for us...also...the roles gets passed along from the abap stack to the J2ee stack....
Now to your original issue...we had to change our sld in our system to a new box and had to re-configure....we got the same error that you were getting...
we corrected it by doing the following...
Corrected the entries in the Visual Admin under SLD data supplier service... for the HTTP tab as well as the CIM tab.
Did the SLDCHECK(TCODE on abap stack) and made sure everything was ok....
Did a CPACache refresh full...and of course a restart....
that solved the issue for us...
Thanks,
Renjith

Similar Messages

Integration Directory, Cache Notifications with error

Guys,
In Integration Directory, I create one Comunication Channel, but, when i actived one, it dosnt appears in RWB Comunication Channel Monitoring.
In Integration Directory -> Environment -> Cache Notifications, show the following error:
Integration Server (Central Adapter Engine) | Directory Change List | pisuper | Standard Change List
With "Standard Change List" as: Not Yet Started
Details: Never change Status.
Can anybody help me?

Also check in SLD technical system for Exchange Infraustructure.
Check weather Adapter enginer is registered or not.
Your XI domain should contains 6 entries
1.Adapter engine
2.Domain
3.Integration Directory
4.Integration Repository
5.Integration Server
6.RWB

Integration Directory - Cache Notifications

I just installed QA box. I am trying to move my Integration Directory objects. When I do cache notifications in ID I get an error in the cache notifications Integration Server (ABAP Cache).
Any help is appreciated.

Hi Michael,
What type of error are you getting ?
Anyway if you did not go thru this document, then please have a look into this-
https://websmp101.sap-ag.de/~sapidb/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf
Hope this helps,
Regards,
Moorthy

Cache Notifications Error in Integration Directory

Hello,
I'm having an interesting problem at my client's PI 7.0 system. When I update my changelist, I can see problems in Integration Directory - cache notifications. Integration Builder works fine. When I retry the cache refresh manually, I turns to green.
But, Communication Channels with adapter type XI are not created even when I activate my changelist and manually fix the cache refresh if there are errors. All other adapters can be seen in Component Monitoring - Adapter Engine - CC Monitoring, but XI type adapters are not there.
How can we resolve this problem?
Thank you,
Gökhan

Hi,
Check all steps in this doc (Especially from Page 20 to 24): [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01be34|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01be34]
Thanks,
- Gujjeti.

SXI_CACHE - Integration Directory Cache problem

hi
im getting this on 001 but not xxx client.
I id post installation also. i switch client 001 to another.
while SXI_CACHE - Integration Directory Cache TC i can't see cache also manu option that adpter engine.
Thanks
Sachin

Check if the right client has been identifies as integration server in SLD and check right URL has been mentioned in SXMB_ADM.
VJ

Int Dir Environment Cache Notifications - Error

Every one,
Int Dir > Environment > Cache Notifications, gives the follwoing Dialog,
Unable to determine the name of the central Adapter Engine from the System Landscape Directory at this time. Notifications to the central Adapter Engine are therefore listed using the technical name of the Adapter Engine. This is usually structured as follows: af.<SAP System ID>.<Name of application server>
sxi_cache on the abap stack works fine.
My guess is that,
I did not create any SLD entry for the central AE. That could be the problem.
We have all the components on a single server and only one AE. There are no remote AEs.
-Naveen.

Naveen,
This is because of incosistence of SLD entries- refer SAP Note - 764176 and do accordingly.
Regards,
moorthy

Using Integration Directory Programming Interface Error Wrong_Version

Hi all
using the IB API to query and read the objects in the pi 7.11 I get the error wrong_version
by reading of some interface determinations.
If I use the webservice InterfaceDeterminationQuery all will worke fine but using
InterfaceDeterminationRead some of the interface determinations response WRONG_VERSION
All Objects are from PI 7.11 and the wsdl File are from SAP BASIS 7.11
any idea?, testingteh same from the WSNavigator in the pi will work fine.
regards
Ralf

Hi Ralf, did you solve the problem? Are there any detailed error messages/payloads/stack traces? Thanks, regards, Martin

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

Error while assigning Business Systems in Integration Directory

Hi,
I'm getting an error when trying to assign the business systems in the integration directory.
The error i'm getting exactly is "access to object list of type BusinessSystem using the internalEOAService BusinesSystemAccessor failed " .
I've cleared the SLD_cache and checked it but the same error.
The business systems are appearing when i tried the transaction code SLD_CHECK and is in green status.
what might be the error.

Hey
just want to make sure,are u using communication channel with party or without party.
also make sure that user has sufficient authorizations
http://help.sap.com/saphelp_nw04/helpdata/en/c4/51104159ecef23e10000000a155106/content.htm
Thanx
Ahmad
Message was edited by:
Ahmad

Adapter Status Grey and Cache Error in acessing Integration Directory

Dear All
While going through the following path
RWB-->Component Monitoring->Adapter Engine->Cache Connectivity Test
i got the following result
" Cache notification from Integration Repository failedError when accessing the Integration Directory "
RWB-->Component Monitoring->Adapter Engine->Adapter Monitoring
I am able to see the list of all adapters but all the adapters have Gery light status instead of having a red or green light status
Kindly tell me what to do...how to change the grey light status to green light and how to set the Cache right
and going by the following path
Thanks in anticipation
Chakra and Somnath

Hi Somnath,
Check out this link for cache Connectivity:
How To handle Caches in SAP XI 3.0
https://websmp206.sap-ag.de/~sapdownload/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf
Cheers,
Vijay Raheja

Integration Builder Directory cache access problem

Hi All,
I am learning SAP XI. I am trying to follow the example explained at https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1312. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] I did al the steps in the Integration Builder Repository. Then I opened the Integration Builder Directory to continue with the next steps.
in the Cache Notifications Panel I get some errors, all of the same kind:
Unable to notify integration runtime (ABAP) of data changes
http connection to "http://p4p800d-6:8000/sap/xi/cache?sap-client=000" returns the status code "403" in response
Am I doing something wrong?
Thanks
Juan Manuel

The Java Web Start cannot accept unsigned jars. If the jars are signed, it will ask in a dialog box if it should allow unrestricted access to this jar.
In my case, I upgraded XI SP0 to SP4, which included updating the Adapter Core, Adapter Framework, and the XI TOOLS to SP4.
On launching the Web start, it seemed that the jars were not getting signed. JWS cannot allow unsigned jars to the client.
These jars are maintained in:
\usr\sap\<SID>\SYS\global\xi\directory_server\javaws\directory
I am having problems with my XI upgrade to SP4, and it is probably not signing the jars.
Do you know why this may be happening ...
thanks,
Manish

Error in Integration Directory

Hi Experts,
In ID When I Go for Environment-->>Cache Notifications
I Got the Following Error

Unable to determine the name of the central Adapter Engine from the System Landscape Directory at this time. Notifications to the central Adapter Engine are therefore listed using the technical name of the Adapter Engine. This is usually structured as follows: af.<SAP System ID>.<Name of application server>
I Checked With All PI* Users, None of them are Locked.
In The Runtime Workbench Component Monitoring-->> All Components AE, SLD,IR , ID, RTW, Are in the Green State Only.
Here If I Clicked on the Cache Connectivity Test Means It's Giving Error.
Attempt to fetch cache data from Integration Directory failed; cache could not be updated
[Fetch Data]: Unable to find an associated SLD element (source element: SAP_XIIntegrationServer, [CreationClassName, SAP_XIIntegrationServer, string, Name, is.01.epnwsrv, string], target element type: SAP_BusinessSystem)
Please Resolve this Issue.
10 Points If Problem is Solved
Regards
Khanna

HI Khanna
Unable to determine the name of the central Adapter Engine from the System Landscape Directory at this time. Notifications to the central Adapter Engine are therefore listed using the technical name of the Adapter Engine. This is usually structured as follows: af.<SAP System ID>.<Name of application server>
did you try to clear the SLD cache in Integration Directory? After that SLD information is newly read and so your biz system will appear.
To clear SLD cache go to menu "Environment" --> "Clear SLD Data Cache".
Have a look at these threads ?
Unable to determine name of central adapter engine
Wrong Adapter engine in RFC Adapter after export/import
Attempt to fetch cache data from Integration Directory failed; cache could not be updated
[Fetch Data]: Unable to find an associated SLD element (source element: SAP_XIIntegrationServer, [CreationClassName, SAP_XIIntegrationServer, string, Name, is.01.epnwsrv, string], target element type: SAP_BusinessSystem)
Same kind of problem discussed here.. have a look at this thread.. might be helps to you....
Attempt to fetch cache data from Integration Directory failed
Cheers...
Vasu
** REward Points if found useful **

Error in the Integration Directory

Hi All,
In ID When I Go for Environment-->>Cache Notifications
I Got the Following Error
Unable to determine the name of the central Adapter Engine from the System Landscape Directory at this time. Notifications to the central Adapter Engine are therefore listed using the technical name of the Adapter Engine. This is usually structured as follows: af.<SAP System ID>.<Name of application server>
Please Resolve this Issue
Regards
Khanna

Hi Navadeep,
I Checked With All PI* Users, None of them are Locked.
In The Runtime Workbench Component Monitoring-->> All Components AE, SLD,IR , ID, RTW, Are in the Green State Only.
Here If I Clicked on the Cache Connectivity Test Means It's Giving Error.
Attempt to fetch cache data from Integration Directory failed; cache could not be updated
[Fetch Data]: Unable to find an associated SLD element (source element: SAP_XIIntegrationServer, [CreationClassName, SAP_XIIntegrationServer, string, Name, is.01.epnwsrv, string], target element type: SAP_BusinessSystem)
Please let me Know
Regards
Khanna

XI Error in Integration Directory adapter list is not display.

Hi All,
We are getting following error message while creating communication channels in Integration directory. More over we have attached error log file with this message.
ERROR :-
u2022 Connection to system REPOSITORY using application REPOSITORY lost. Detailed information: Error accessing "http://xxxxx:50000/rep/query/int?container=any" with user "PIDIRUSER". Response code is 503, response message is "Service Unavailable" (HCX_COMMUNICATION_ERROR)
Apart from this if we try to refresh the xi cache with T-code SXI_CACHE it show the following error. For same I have already checked the Troubleshooting Guide for How To handle Caches in SAP XI and found every thing is ok.
ERROR :-
com.sap.aii.ib.server.abapcache.CacheRefreshException: Connection to system REPOSITORY using application REPOSITORY lost. Detailed information: Error accessing "http://xxxxx:50000/rep/hmi_service_swc_manager/int?container=any" with user "PIDIRUSER". Response code is 503, response message is "Service Unavailable"
 at com.sap.aii.ibdir.server.abapcache.content.CacheSwc.addContent(CacheSwc.java:63)
 at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:360)
 at com.sap.aii.ibdir.server.abapcache.CacheRefreshRequest.addContent(CacheRefreshRequest.java:324)
 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.CacheRefreshSession.setXmlDataAndBufferSize(CacheRefreshSession.java:121)
 at com.sap.aii.ibdir.web.abapcache.CacheRefreshSession.<init>(CacheRefreshSession.java:40)
 at com.sap.aii.ibdir.web.abapcache.CacheRefreshSession.getInstance(CacheRefreshSession.java:54)
 at com.sap.aii.ibdir.web.abapcache.CacheRefreshServlet.doGet(CacheRefreshServlet.java:45)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 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(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
So please guide us to solve the above mention problem.
Thanks,
Harshal

Hi...
Contact your basis team .
Regards,
Leela

Error: - No service for system port, client in Integration Directory

Hi
In Idoc to File scenario, My Idoc 've been successfully send from the sender system.
but its neither getting displayed in the SXMB_PATH nor saved in the specified path.
I checked in SM58 in R3 that RFC user has access to send data to XI. But it showing below Error:_
ERROR:-
No service for system Sender Port (SAPDEV) client sender client (300 ) in Integration Directory
Please do the needful
Thanks,
Anshul

Hi Anshul,
Go to:
TCODE SXMB_ADM -> Integration Engine Configuration
Please change the system rile to be "Application System", then retest if the similar issue happen again after that.
If not helped, follow:
1. Clear SLD Delta Cache Referesh in the Integration Directory
2. Open the Business System in edit mode and select Adapter specific identifiers following the menu path:
Service -> Adapter Specific Identifiers
3. Please click in the button next to "Apply" button to pick up the Logical system from SLD.
Regards,
Caio Cagnani

Integration Directory - Cache Notifications Error!!

Similar Messages

Maybe you are looking for