cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Error in Directory Cache Update

Former Member

on ‎07-22-2008 9:41 AM

0 Kudos

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)

Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (3)

Answers (3)

prateek
Active Contributor
‎07-22-2008 12:06 PM
0 Kudos

Refer SAP Note 764176

Regards,

Prateek

Show replies
Show replies
Former Member
‎07-22-2008 12:48 PM
0 Kudos

Hi Prateek,

thx for the note. I followed all steps and all finished fine.

But i have no Adapters in RWB of PROD System.

As mentioned, we changed from two SLD to one. We chose the DEV SLD and connected the PROD System on DEV SLD. This went fine, also with your helping note.

But when we go to Int. Directory we get red Status in Cache-Information for Intergration Server (central adapter engine). Java Cache and Abap-Cache are showing green here.

Also we don't get Cache data in SXI_CACHE for Adapter-Engine-Cache - which seems to be a "connection" to the error on Int- Directory.

Do you have a clue on how to solve this?!

br

Former Member
‎07-22-2008 10:37 AM
0 Kudos

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%2bru...

Regards,

Suryanarayana

Show replies
Show replies
Former Member
‎07-22-2008 11:40 AM
0 Kudos

Hi Suryan,

thanks for ur hints.

I did all the mentioned but i am not authorized to update cache of Runtime in Exch. Profile / Runtime.

The Refresh of INTEGRATIONSERVER_ and af.pi.... fails because of error 403 which is sth. with user. So what user is used here and where do i have to change it?!

I already checked all User for locks, no one is locked.

Could you help?!

Because of not able to refresh the cache the SXI_CACHE is also not up to date and in error!

br

Former Member
‎07-22-2008 11:54 AM
0 Kudos

hi,

Pls make sure XIISUSER has the correct role (SAP_XI_IS_SERV_USER_MAIN).

When you test the HMI destination in SM59, do you have a popup logon window even though you have already entered the logon data in its definition? If so, you should use another user id, test the remote logon once, and then change it back to XIISUSER. Do the logon again, you should not get the logon prompt again. The refresh will work automatically afterwards

<removed by moderator>

regards

kummari

Edited by: Mike Pokraka on Jul 24, 2008 12:56 PM

Former Member
‎07-22-2008 1:16 PM
0 Kudos

Hi,

In continuation with ur reply,We have no authorization for the Exchangeprofile so U can reach Basis(admin) people.

Regards,

Surya.

Former Member
‎07-22-2008 1:56 PM
0 Kudos

Hi, anyone who could provide me with informations on how to get Cache-Data from adapter engine in SXI_CACHE?!

Also we are not able to check Service "enigine" in SICF.

We get this:

<detail>
u2212
	<SAP:Error SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">URL_PIPELINE_NOT_FOUND</SAP:Code>
<SAP:P1>/sap/xi/engine?sap-client=100</SAP:P1>
<SAP:P2/>
<SAP:P3/>
<SAP:P4/>
<SAP:AdditionalText/>
<SAP:ApplicationFaultMessage namespace=""/>
u2212
	<SAP:Stack>
Pipeline ID , which is expected as value of attribute &quot;type&quot; in the URL, does not exist in the Integration Engine (URL = /sap/xi/engine?sap-client=100)
</SAP:Stack>
</SAP:Error>
</detail>

some ideas?!

we already checked SXMB_ADM for right URL and also in Business System related to Technical System of integration server. Here the right URL is given!

br

Former Member
‎07-22-2008 3:31 PM
0 Kudos

someone please help!?

br

Former Member
‎07-22-2008 9:50 AM
0 Kudos

hi fritz,

go thru this help link for reference

http://help.sap.com/saphelp_nw04/helpdata/en/ef/ca41420c77f83ae10000000a1550b0/frameset.htm

regards

kummari

Show replies
Show replies
Ask a Question