Unable to see any assets after login to AEM Desktop App | Community
Skip to main content
A
abhisheklakhpatre
February 9, 2023
Solved

Unable to see any assets after login to AEM Desktop App

  • February 9, 2023
  • 2 replies
  • 698 views

 

I can't see any assets when I logged in to aem as cs based environment. The lower environments are working fine. I have sufficient permission to view asset. 

 

Can anyone help how to resolve this issue?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by abhisheklakhpatre

As a workaround, adobe team disabled ntFileFolderElastic which was causing the issue in the desktop app and the errors in the logs.

 

And informed it as a bug and will be fixed in upcoming releases.

Adobe comment for reference:
The problem seems to be related to the use of the index ntFileFolderElastic with sort options that are not mapped in the index definition.
In this case, the index should not apply the sort clause that instead should be performed in OAK.
As a workaround, we have to disable ntFileFolderElastic on the affected environments.


2 replies

krati_garg
Adobe Employee
krati_gargAdobe Employee
Adobe Employee
February 12, 2023

@abhisheklakhpatre The screen shot you have shared is of your AEM Desktop App.

 

Do you mean to say, that assets are in your Cloud environment, but not visible in the AEM Desktop App. It could be a Sync issue between Cloud and Desktop App.

 

Please follow below link - on how to set up the AEM Desktop App and sync with AEMaaCS

https://experienceleague.adobe.com/docs/experience-manager-desktop-app/using/using.html

 

    A
    abhisheklakhpatreAuthorAccepted solution
    April 20, 2023

    As a workaround, adobe team disabled ntFileFolderElastic which was causing the issue in the desktop app and the errors in the logs.

     

    And informed it as a bug and will be fixed in upcoming releases.

    Adobe comment for reference:
    The problem seems to be related to the use of the index ntFileFolderElastic with sort options that are not mapped in the index definition.
    In this case, the index should not apply the sort clause that instead should be performed in OAK.
    As a workaround, we have to disable ntFileFolderElastic on the affected environments.


      Terms & ConditionsAccessibility statement

      Loading footer...