How To Fix /UI2/GLOBAL_CACHES029 - &2: &1 instances invalidated for all users in all clients (incl. CONF)

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/GLOBAL_CACHES -

• Message number: 029

• Message text: &2: &1 instances invalidated for all users in all clients (incl. CONF)

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /UI2/GLOBAL_CACHES029 - &2: &1 instances invalidated for all users in all clients (incl. CONF) ?

  The SAP error message /UI2/GLOBAL_CACHES029 indicates that certain instances have been invalidated for all users in all clients, including the configuration client (CONF). This typically relates to the caching mechanism used in SAP Fiori/UI5 applications, where certain cache entries are invalidated due to changes in the underlying data or configuration.
  
  Cause:
  
  Changes in Configuration: The most common cause for this error is a change in the configuration of the Fiori/UI5 applications, such as updates to the OData services, changes in the UI5 libraries, or modifications in the application settings.
  Transport Requests: If transport requests are moved between systems, it can lead to cache invalidation if the transported objects affect the cache.
  System Maintenance: Regular system maintenance activities, such as system upgrades or patches, can also trigger cache invalidation.
  Manual Cache Clearing: If a system administrator manually clears the cache, it can lead to this error message being displayed.
  
  
  Solution:
  
  
  Rebuild the Cache: The primary solution is to