cancel
Showing results for 
Search instead for 
Did you mean: 

a problem about cache refresh in PI7.3

0 Kudos

hi experts:

  i have a problem about cache refresh in PI7.3.  when i finished the senario configuration in IR and ID,and run it ,the monitor give us a error message:"

NO_RECEIVER_CASE_ASYNC",but i checked the receiver determination ,it is correct. And ,the senario run correctly before have the same problem now.

I think it some thing to do with cpa cache.So i check the sxi_cache,and refresh it manually, there is a error:

<html><head><title>Application Server Error</title></head><body>
<H2>500 Connection timed out</H2><br>
<hr>Mon Jun 25 15:17:23 2012

</body></html>

How can i solve this porblem?

Thank you!

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

>>>>>>>I think it some thing to do with cpa cache

Use PIDIRUSER for CPACache delta/full refresh

Use this link :-    http://<host>:<port>/CPACache/refresh?mode=full

>>>>>>>i check the sxi_cache,and refresh it manually, there is a error:

Was is it a full or delta cache refresh ?

Thanks,

      Suji

0 Kudos

Hi

        When i using the PIDIRUSER for CPAcahe,it shows:403   Forbidden,Error: You are not authorized to view the requested resource.And i use the delta cache refresh in sxi_cache

Former Member
0 Kudos

>>>>>>>>>>>>it shows:403   Forbidden,Error: You are not authorized to view the requested resource

You should use PIDIRUSER which has proper authorization. Check with ur Access provisioning team to provide you SAP_ALL user access.

Also go through this link regarding PI service users and roles [http://help.sap.com/saphelp_nwpi711/helpdata/en/9f/d12940cbf2195de10000000a1550b0/content.htm]

>>>>>>>>>>For Cache refresh in PI , refer to part 1.5, check if you are on the same track

https://websmp109.sap-ag.de/~sapidb/012003146900000492702008E/ReadinessCheckFor71.pdf

Thanks,

    Suji    

Former Member
0 Kudos

Hi Yu,

I just hit this exact issue a couple of weeks ago...Although I'm on PI version 7.11 I think a couple of these suggestions would prove useful in your case too...

It could be caused by an SLD inconsistency with the CIM model and relevant associations. To check that all associations are fine in the SLD (and for any manual corrections that may be required), refer to SAP Note 764176.

Then SAP Note 1670123. This details additional parameter changes that could be made. While it refers to a 'full' cache refresh, it could still be related to your issue.

Regards, Trevor

Answers (0)