SAP Basis Tech Supports

Symptom

The runtime cache for the integration server (ABAP) is not automatically updated after you activate a change list. The traffic light in the “Cache Updated” column remains red (= it has not started yet). In transaction SXI_CACHE, the system issues the following error message: “Error when reading HTTP destination: INTEGRATION_DIRECTORY_HMI”. However, if you start the partial cache refresh in transaction SXI_CACHE, the cache is updated correctly.
Other terms

XI 30, XI 70, PI 70, XPI, SAP NetWeaver 04, SAP NetWeaver 2004s,
Exchange Infrastructure, Integration Directory, runtime cache, XI cache, SXI_CACHE, INTEGRATION_DIRECTORY_HMI
Reason and Prerequisites

In particular, this problem may occur after you upgrade from NW2004 to NW2004s. The insufficient user authorizations are caused by an obsolete role profile.
You have already checked the following and you did not detect any errors:
- The HTTP destination INTEGRATION_DIRECTORY_HMI exists, is configured correctly, and the target destination can be reached.
- Users entered in the INTEGRATION_DIRECTORY_HMI destination (usually Integration Server service users) and Integration Directory service users (see ExchangeProfile, Eigenschaft com.sap.aii.directory.serviceuser.name) are set up correctly and are not locked.
For more information about these checks, refer to the documentation “How To handle Caches in SAP XI 3.0″ or “How To Handle XPI Caches in SAP NetWeaver 04s” Guide (see SAP Service Marketplace, http://service.sap.com/nw-howtoguides).

Solution

For the users mentioned under “Reason and Prerequisites”, proceed as follows:
1. Delete the user profile for the SAP_XI_IS_SERV_USER or SAP_XI_ID_SERV_USER role. To do this, call transaction su01, enter the name of the service user and choose “Display”. Then choose the “Roles” tab and double-click to select the SAP_XI_IS_SERV_USER or SAP_XI_ID_SERV_USER role. A new window is displayed. In the new window, choose the “Authorizations” tab and switch to change mode. Here, delete the profile names.
2. Now choose the new profile names that have been proposed.
3. Then choose “Change Authorization Data” and generate the role.
4. Finally, perform a user comparison.