내 커뮤니티 업적 표시줄을 확대합니다.

Introducing Top KCS Articles, Curated For Your AEM Troubleshooting Pleasure!

Avatar

KB_Author
Employee

24. 5. 14.

Introducing Top KCS Articles, Curated For Your AEM Troubleshooting Pleasure!

  by @KB_Author 

 

 

Dear AEM Community,

 

Your time is precious, and we understand the importance of efficiency when it comes to troubleshooting issues with AEM. That's why we're excited to introduce our carefully curated collection of Top KCS (Knowledge-Base) Articles, designed to help you resolve common challenges swiftly and effectively.

 

Our Top KCS Articles are your shortcut to:

 

  • Quickly identifying and resolving recurring issues.
  • Accessing expert insights and best practices for AEM.
  • Streamlining your troubleshooting process for maximum productivity.
  • Empowering yourself with the knowledge to tackle any AEM-related problem head-on.

Why spend hours searching for solutions when our Top KCS Articles have already done the heavy lifting for you?

Let us help you save time so you can focus on what truly matters – empowering you to provide a truly personalized experience to your customers with AEM.

 

Start supercharging your problem-solving skills today by exploring our Top KCS Articles!

 

Take a look:

 

  1. Cloud Manager Assets performance testing failing – Learn why the Assets Performance testing fails with an unknown error.
  2. Pipeline Build fails due to Python not available error - Fix the Pipeline Build failure due to a Python error by creating a Maven project that uses the exec plugin to install Python3.
  3. Steps to get Oak-run tool for the AEM version - The article explains how to get the Oak-run tool depending on the AEM version.
  4. Frontend pipeline deployment breaks the website - This article describes a solution to the issue where frontend pipelines are not successfully applied to websites, even when deployment finishes successfully. Add ServerAlias to an enabled vhost to fix it.
  5. Tasks can't be created in Assets Essentials - If you can't create tasks when using the Assets Essentials UI for a specific asset repository, add the missing values to the “Allow Regexp Host” property of the Apache Sling Referrer Filter OSGi configuration.
  6. Not able to move experience fragments – Learn the solution to the issue when someone attempts to move a content fragment in Adobe Experience Manager 6.5, the UI will spin, and the move operation is not processed completely.
  7. Replication Queue blocked in AEMaaCS - The Replication Queue in Adobe Experience Manager as a Cloud Service (AEMaaCS) may sometimes get blocked. Follow the steps in this article to fix this issue with Admin permissions.
  8. How to restore a deleted content path in AEM as a Cloud Service – Learn the solutions if you need to find different ways to restore a specific content path in Adobe Experience Manager as a Cloud Service.
  9. Workflows are set to “not editable” after code deployment - This article resolves the AEM issue where after creating a Workflow in AEM followed by a code deployment, the Workflow appears as “Not Editable”.
  10. Common asset ingestion issues and solutions - This article describes the most common AEM assets ingestion issue scenarios and how to analyze them, including high processing, high volume, large DAM repositories, and many concurrent authors.

 

But wait! There’s even more important AEM Featured Content this month!

 

Adobe is deprecating the Service Account (JWT) credentials in favor of the OAuth Server-to-Server credentials.

Here’s the facts with resource links:

What is happening?

Adobe is deprecating the Service Account (JWT) credentials in favor of the OAuth Server-to-Server credentials.

 

Who is impacted?

Your projects on the Developer Console that use the Service Account (JWT) credential need to be migrated to use the OAuth Server-to-Server credential.

 

What action needs to be taken?

To ensure that those integrations and custom applications continue to work, an IT/Development team in your organization must update them to use the OAuth Server-to-Server credential.

 

When is the deadline?

Existing Service Account (JWT) credentials will continue to work until January 27, 2025.

 

In addition, the Developer Console will continue to support the creation of new Service Account (JWT) credentials until June 3, 2024. A new Service Account (JWT) credential can't be created or added to a project after this date.

If you have stale/unused projects containing Service Account (JWT) credentials, you should delete those projects.

 

Resources

For more information (including details on specific products), please see the resources below:

 

Happy Troubleshooting!

응답