cancel
Showing results for 
Search instead for 
Did you mean: 

com.sap.aii.af.service.cpa.impl.exception.CPALookupException

Former Member
0 Kudos

Hi,

iam getting following error in SXMB_MONI for outbound IDOC to FILE.

Verified all the compoennts in ID and no issues. Could find a note# 994614 on similer issue, but its for release 640.

-


<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- <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.ConfigException:

ConfigException in XI protocol handler. Failed to determine a receiver

agreement for the given message. Root cause:

com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't

retrieve outbound binding for the given P/S/A values:

FP=;TP=;FS=sapdev;TS=xiddev;AN=MI_WPPLU02_Articlemaster;ANS=http://sub-

sapretail-pos.com/Articlemaster;</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Accepted Solutions (0)

Answers (5)

Answers (5)

aashish_sinha
Active Contributor
0 Kudos

Hi,

Reason of this error is :

During J2EE Engine restart the CPA Cache application tries to read the configuration data from the Integration Directory. The Integration Directory is an application, whereas the the CPA Cache is an J2EE service and starts earlier. Therefore the automatic delta cache refresh fails on the central AE in case of a server restart and the CPADirectoryCacheException is thrown.

This exception can be ignored. The CPA service stores its cofiguration data in the database. During J2EE Engine downtime the Integration Directory is not available either. Therefore no new configuration can be added in the Integration Directory and there and the system has a consistent state after restart.

The automatic delta cache refresh mechanism is necessary for decentral Adapter Engines, after system restart. During a downtime of a decentral Adapter Engine the configuration data in the Directory can change, since it runs on different physical machine.

An inconsistency can only arise under special circumstances on a central Adapter Engine: The Directory data is changed while the CPA Cache service is down (an error is reported in the Directory's Cache notification). Engine restart will not update the CPA Cache data, due to the above explained reason.

and solution of this problem is

Restart the CPA Cache application "com.sap.aii.af.cpa.app" manually. This can be done with the Visual Administrators "deploy" service. Make sure that the Integration Directory is available. The Directory's Cache notification should report success after that.Alternatively you can trigger a partial (delte) cache refresh.

Also try this solution.

In Release 6.40 you can use adapter metadata from SAP BASIS 6.40 only. If, regardless of this, you import the content of SAP BASIS 7.00, the 6.40 adapter metadata in the cache is overwritten. As a consequence, objects cannot be loaded at runtime and messages trigger an error.

The adapter metadata from the software component SAP BASIS 7.00 is not distributed to the runtime cache.

The communication channels with adapter types from SAP BASIS 7.00 can no longer be activated.

1) Import the archive as described in the Support Package Stack Guide.

The correction concerns the archive:

For XI 30 SP18:

- SAPXITOOL18P_2.sca

For XI 70 SP09:

- SAPXITOOL09_3.sca

The archive and the Support Package Stack Guide are located on the SAP Service Marketplace. See Note 952402 for the relevant link.

2) Execute a complete cache refresh for the adapter engine.

Note: Bear in mind that if you created communication channels with the adapter types from SAP BASIS 7.00, these will not work in Release 6.40. Therefore, you must change the channels that they use the relevant adapter type from SAP BASIS 6.40 and activate the changed channels.

Hope this will help you.

Regards

Aashish Sinha

PS : reward points if helpful

Former Member
0 Kudos

Hi Assshish,

Thanks a lot for the detailed information.

We have Release 7.00 and we have adapters from SAP BASIS 7.00. So as per the details u have provided, the second solution may not be relevant to us. Please confirm.

I will try to restart the service "com.sap.aii.af.cpa.app" and update you.

At present, there are no errors in directory cache notifications.

Former Member
0 Kudos

Hi Karthik,

It seems you have problem with you Cache refresh.

Check whether you have any error in "Cache notifications" in ID.

-Pinkle

Former Member
0 Kudos

HI , Cache notifications in ID shows all the entries in GREEN. No messages in PROBLEMS.

nisarkhan_n
Active Contributor
0 Kudos

Make sure you are using the PIDIRUSER and PWD to do the complete cache....

Former Member
0 Kudos

Hi All,thx for the quick response. I did full refresh and got following output:

The XML page cannot be displayed

Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.

-


Invalid at the top level of the document. Error processing resource 'http://subdev:50000/CPACache/refresh?mode=full'. Line...

CPA cache refresh (mode=full) successfully executed in 323 milliseconds.

^

-


I assume, refresh is successfull. But still I am getting same error. Other components are properly created ,no erros and all the compoenets are activated.

Please let me know if I have to verify any other details.

Former Member
0 Kudos

Hi karthik

whether you did just SXI_CACHE or CPA cahce refresh?

http://<hostname>:<port>/CPACache/refresh?mode=full ..use this to do CPA cache refresh.

If error is still there, check the RFC connection INTEGRATION_DIRECTORY_HMI ...it should be workng fine..

i Think Cache refresh could solve this problem. See this

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1a69ea11-0d01-0010-fa80-b47...

Regards

Abhishek

prateek
Active Contributor
0 Kudos

1. Make a full CPACache refresh

http://<hostname...>:<port>/CPACache/refresh?mode=full

2. Make sure u have created the proper receiver agreement and assigned it proper communication channel

3. Make sure alll ID developments are activated.

Regards,

Prateek