How To Fix /UI2/PAGEBUILDER106 - Page Cache reset started

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/PAGEBUILDER -

• Message number: 106

• Message text: Page Cache reset started

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/PAGEBUILDER106 - Page Cache reset started ?

  The SAP error message /UI2/PAGEBUILDER106 Page Cache reset started is typically related to the SAP Fiori/UI5 framework, specifically concerning the page cache mechanism used by the SAP Fiori Launchpad. This message indicates that the system is initiating a reset of the page cache, which can occur for various reasons, such as changes in the application, updates to the UI5 libraries, or configuration changes.
  Cause:
  
  Application Changes: If there are changes made to the UI5 application or its components, the cache may need to be reset to reflect those changes.
  Library Updates: Updates to the UI5 libraries or the Fiori Launchpad can trigger a cache reset to ensure that the latest versions are being used.
  Configuration Changes: Changes in the configuration settings of the Fiori Launchpad or related components can also lead to a cache reset.
  Performance Optimization: The system may periodically reset the cache as part of performance optimization routines.
  
  Solution:
  
  Wait for Cache Reset: Often, this message is informational, and the cache reset will complete automatically. You may just need to wait for the process to finish.
  Clear Cache Manually: If the cache reset does not complete or if you encounter issues, you can manually clear the cache:
  
  Use transaction code /UI2/FLP to access the Fiori Launchpad.
  Navigate to the "Settings" and look for options to clear the cache.
  
  
  Check System Logs: Review the system logs (transaction code SLG1) for any related errors or warnings that might provide more context on the cache reset.
  Monitor Performance: After the cache reset, monitor the performance of the Fiori applications to ensure they are functioning as expected.
  Consult Documentation: Refer to SAP Notes or the official SAP Help Portal for any specific guidance related to your version of SAP Fiori/UI5.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address specific issues related to cache management in your version of SAP Fiori.
  Fiori Launchpad Configuration: Familiarize yourself with the configuration settings of the Fiori Launchpad, as improper settings can lead to frequent cache resets.
  UI5 Versioning: Keep track of the UI5 version being used and any updates that may affect the cache behavior.
  
  If the issue persists or if you encounter additional errors, it may be beneficial to reach out to SAP support for further assistance.