cancel
Showing results for 
Search instead for 
Did you mean: 

Cache Error

Former Member
0 Kudos

Hi,

After upgradation from XI3.0 to PI7.0,i was trying to run one scenario but I face the error as follows while checking the SXMB_MONI,

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

- <!-- Receiver Identification

-->

- <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>Error when reading HTTP destination: INTEGRATION_DIRECTORY_HMI.</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error while refreshing the XI runtime cache</SAP:Stack>

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

</SAP:Error>

please do the needful.

Regards,

Pratibha

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Pratibha

can you try a cache refresh by running the report SAI_CACHE_REFRESH

have a look at this doc:

https://websmp202.sap-ag.de/~sapdownload/011000358700003163902004E/HowTo_handle_XI_30_Caches.pdf

Please refer to the Trouble SHooting section of this guide,

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

Please refer to

also refer to the SAP Help URL:

http://help.sap.com/saphelp_nw2004s/helpdata/en/37/5b0f41e9a0ef23e10000000a155106/frameset.htm

Pls reward if useful

Former Member
0 Kudos

Hi..

try with this blogs...

/people/sravya.talanki2/blog/2005/12/02/sxicache--ripped-off

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

/people/sravya.talanki2/blog/2006/12/19/unable-to-read-integrationdirectoryhmiundocumented-bug-sxicache

vasanth

Former Member
0 Kudos

Check this blog:

/people/sravya.talanki2/blog/2006/12/19/unable-to-read-integrationdirectoryhmiundocumented-bug-sxicache

There are several variants of the cache refresh mechanism depending on the scope of the cache refresh (delta only or entire cache refresh) and on the triggering component (tool or messaging component). The bootstrapping mechanism described above is always used for the communication. There is one exception, however, if a direct HTTP connection is established from the Integration Server to the Integration Directory by using the SM59 type H destination INTEGRATION_DIRECTORY_HMI.

Following the conventions above, the user defining the Integration Server should be used as the logon user that is maintained in the exchange profile parameters com.sap.aii.integrationserver.serviceuser.*.