How To Fix /UI2/CDMRPL019 - No App Descriptors found

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/CDMRPL -

• Message number: 019

• Message text: No App Descriptors found

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/CDMRPL019 - No App Descriptors found ?

  The SAP error message /UI2/CDMRPL019 No App Descriptors found typically occurs in the context of SAP Fiori applications when the system is unable to find the necessary application descriptors for a specific Fiori app. This can happen for various reasons, and here are some common causes, solutions, and related information:
  Causes:
  
  Missing or Incomplete App Descriptor: The app descriptor (usually a manifest.json file) for the Fiori application may be missing or not properly configured.
  Incorrect Configuration: The application might not be correctly registered in the SAP Fiori Launchpad or the configuration might be incorrect.
  Transport Issues: If the application was recently transported from one system to another, the transport might not have included all necessary files.
  Caching Issues: Sometimes, caching issues can prevent the system from recognizing the app descriptors.
  Authorization Issues: The user may not have the necessary authorizations to access the app descriptors.
  
  Solutions:
  
  Check App Descriptor: Verify that the manifest.json file exists in the application folder and is correctly configured. Ensure that all required properties are defined.
  Register the Application: Ensure that the application is properly registered in the SAP Fiori Launchpad. Check the Launchpad configuration and ensure that the app is included in the relevant catalog and group.
  Transport Check: If the app was transported, check the transport logs to ensure that all necessary files were included and that the transport was successful.
  Clear Cache: Clear the browser cache and the SAP Fiori Launchpad cache. You can do this by using the /UI2/FLP transaction and selecting the "Clear Cache" option.
  Check Authorizations: Ensure that the user has the necessary roles and authorizations to access the application. This can be checked in the user profile and role assignments.
  Check System Logs: Review the system logs (transaction SLG1) for any additional error messages or warnings that might provide more context about the issue.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Fiori Launchpad Configuration: Familiarize yourself with the Fiori Launchpad configuration and how to manage app descriptors.
  SAP Community: The SAP Community forums can be a valuable resource for finding similar issues and solutions shared by other users.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or Fiori development team for further investigation.