Cache Notifications Error

[santosh_k3]

Hi Experts,

I am using XI 3.0 version,

And my scenario is File >XI->File.

While processing i am getting an error in ID-->Chache Notifications as shown below, can any one suggest me how to resolve it

and why did this error occured.

Error :

Unable to notify integration runtime (ABAP) of data changes

http connection to "http://xxx/sap/xi/cache?sap-client=xxx" returns the status code "403" in response

Thanks

Sai

[baskar_gopalakrishnan2 · Accepted solution]

>can any one suggest me how to resolve it and why did this error occured.

Talk to Basis team.. HTTP 403 error means access denied. So user role setup for the caching is not allowed to perform

[santosh_k3 · Accepted solution]

Hi all,

I want to know why some of the notifications are in red ,

Integration server (ABAP cache) are in red.

How these errors effect the processing of the scenario

Thanks

Sai

[former_member194786 · Accepted solution]

Hi Sai,

this will affect your scenario in runtime as the changes done will not get reflected in runtime.

there could be various reasons for this such as user locked, authorisation issue or HTTP destination INTEGRATION_DIRECTORY_HMI not working.

Regards,

Sanjeev.

[santosh_k3 · Accepted solution]

Hi All,

Thanks for u r reply,

The issue is resolved ,

Basis guy resolved it.

[former_member4985]

Hi Sai,

Ensure you have maintained the correct password, which MUST be the same, for all the service users on XI. You may check all the places it should be maintained, such as Exchange Profile, SU01, SLDAPICUST, etc..

Check the notes below, according to your system version:

PI 7.1:

#999962 - PI 7.10: Change passwords of PI service users

XI 7.0

#936093 - XI 7.0: Changing the passwords of XI service users

XI 3.0

#721548 - XI 3.0: Changing the passwords of the XI service users

And also ensure that the user has the correct role as per link below:

http://help.sap.com/saphelp_nwpi71/helpdata/en/9f/d12940cbf2195de10000000a1550b0/frameset.htm

Another shot would be by looking the description of the error as per:

/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi

Regards,

Caio Cagnani