cancel
Showing results for 
Search instead for 
Did you mean: 

Cache Error in simple file to file scenario

Former Member
0 Kudos

Hi,

I installed a new xi with SP9 yesterday, and created a simple file to file scenario, but I face the error as follows while checking the SXMB_MONI,

Error Category : XICACHE

Error ID : UPDATE

- <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="XICACHE">UPDATE</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>HTTP status code401 Unauthorized</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>An error occurred when refreshing the XI runtime cache</SAP:Stack>

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

</SAP:Error>

What can be the problem?

Regards,

Nick

Accepted Solutions (0)

Answers (5)

Answers (5)

former_member91687
Active Contributor
0 Kudos

Hi Nick,

For configuration purpose you can follow the link below, you can expand it further once you are there and check if you can find your requirement.

http://help.sap.com/saphelp_nw04/helpdata/en/88/0f453cf1fcc85ee10000000a11402f/content.htm

If this does not solve your problem. kindly provide further details.

Cheers,

Chandra

Former Member
0 Kudos

Thanks Chandra,

But this did not solve my problem.

I am getting this error message:

<?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="">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>

<SAP:P1>af.arb.dl380a-wm\arbdb</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>2: Unable to find URL for Adapter Engine af.arb.dl380a-wm</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine af.arb.dl380a-wm\arbdb</SAP:Stack>

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

</SAP:Error>

<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />

- <!-- ************************************

-->

<Trace level="1" type="Timestamp">2005-12-28T04:00:48Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />

- <!-- ************************************

-->

<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>

<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>

<Trace level="3" type="T" />

<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>

<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>

<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>

<Trace level="3" type="T">ADRESSMOD = SD</Trace>

<Trace level="3" type="T">P_CLASS =</Trace>

<Trace level="3" type="T">P_IFNAME =</Trace>

<Trace level="3" type="T">P_METHOD =</Trace>

<Trace level="3" type="T">FL_LOG =</Trace>

<Trace level="3" type="T">FL_DUMMY = 0</Trace>

<Trace level="3" type="T" />

<Trace level="3" type="T">Unknown channel type: File</Trace>

<Trace level="3" type="T" />

<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>

<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>

<Trace level="3" type="T">PLSRVTYPE = AENGINE</Trace>

<Trace level="3" type="T">ADRESSMOD = SD</Trace>

<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_IE_ADAPTER</Trace>

<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>

<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>

<Trace level="3" type="T">FL_LOG =</Trace>

<Trace level="3" type="T">FL_DUMMY = 0</Trace>

<Trace level="3" type="T" />

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />

It seems my adapter engine has some problem, how can I solve it?

Regards,

Nick

Former Member
0 Kudos

Hi Nick,

Take a look at Michal's reply, see if it could help.

Remember to refresh the cache after the changes

Cheers,

Rashmi

Former Member
0 Kudos

Thanks Rashmi,

We have check that, but no effect.

Regards,

Nick

Former Member
0 Kudos

It is solved by changing RFC destination configuration.

Thanks for everyone!

Regards,

Nick

former_member91687
Active Contributor
0 Kudos

Hi Nick,

It could be possible that some configuration is not done in the right way. Check if your adapter engine is registered in the SLD.

Cheers,

Chandra

Former Member
0 Kudos

Thanks Chandra,

I found Adapter Engine af.arb.dl380a-wm is an Adapter Framework, and it is there.

I do not know how to config URL,user and password for Adapter Engine af.arb.dl380a-wm. Any idea?

Regards,

Nick

Former Member
0 Kudos

I found the Basic URLs of Adapter Engine on DL380A-WM(Server Name), and the URL is http://DL380A-WM:50000, is it right?

Regards,

Nick

Former Member
0 Kudos

Thanks,

This is solved by changing the paramter of xi in sicf.

But I am now facing a new issue,

<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="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>

<SAP:P1>af.arb.dl380a-wm\arbdb</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>2: Unable to find URL for Adapter Engine af.arb.dl380a-wm</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine af.arb.dl380a-wm\arbdb</SAP:Stack>

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

</SAP:Error>

former_member91687
Active Contributor
0 Kudos

Hi Nick,

Check whether your destination in sm59 is working properly or not, i.e INTEGRATION_DIRECTORY_HMI.

The path prefic sholud be /dir/CacheRefresh and in the Logon/Securitytab, the user should be XIISUSER.

If any of the entry is in-correct , change and test.

And the check sxi_cache.

If your problem is not solved take a look at these links and they will give you a better understanding of how to go about solving your problem.

Cheers,

Chandra

Former Member
0 Kudos

Hi.

check the thread

Logon to the Abap Engine with XIISUSER.Check if u are able to login sucessfully

go to the XI installation guide and check creating:

RFC Destination - INTEGRATION_DIRECTORY_HMI

you specify the user XIISUSER over there

In the <b>Security/logon</b> Tab, Save ur setting before u move on to next tab.<i>Very Important.</i>

you can also check these properties in the exchangeprofile:

http://<host:port>/exchangeProfile - its username and password.

The user should be XIISUSER and its password.

Cheers,

Rashmi