The code packages not installed properly in AMS

Hi @keehwan1 
Could you please also check the package version? It could be because of the same version is being installed twice.

Hi @keehwan1 ,

To troubleshoot and resolve the issue with code packages not being installed properly in Adobe Managed Services (AMS) for AEM 6.5.16, follow these steps:

1. Check Log Files for Errors

Examine the log files for both the Author and Publish instances. Look for any errors related to package installation. The relevant logs are:

• Error.log: /crx-quickstart/logs/error.log
• Installation.log: This can usually be found in the logs directory or directly from the package manager interface after an installation attempt.

2. Verify Package Integrity

Ensure that the packages (ui.apps and ui.content) are not corrupted. You can:

• Rebuild the packages: Run your Maven build again to generate fresh packages.
• Manually upload: Try manually uploading the packages via the AEM Package Manager to ensure they are not corrupted during the AMS pipeline deployment.

3. Manual Installation Steps

If the automated deployment via the AMS pipeline isn't working, try manually installing the packages:

1. Upload Packages Manually: Use the AEM Package Manager to upload the ui.apps and ui.content packages.
2. Install Packages: Click on "Install" in the Package Manager. Note any errors that occur during this process.

4. Check Dependencies and Order of Installation

Ensure that all dependencies are satisfied and that packages are installed in the correct order. Typically, ui.apps should be installed before ui.content.

5. Review Permissions

Ensure that the user account used by the AMS pipeline and for manual installation has the necessary permissions to install packages. Missing permissions can cause installation failures.

6. CRXDE Lite Check

Use CRXDE Lite to verify the current state of the repository. Look for:

• Node inconsistencies: Check if there are any partial nodes from previous installations.
• Repository health: Ensure the repository is not in a corrupt state.

7. Package Manager Logs

Check the installation logs in the AEM Package Manager:

• Go to http://<aem-host>:<port>/crx/packmgr/index.jsp.
• Click on the package that failed to install.
• Check the "Last Unpacked Log" for details on why the installation failed.

8. Heap and Memory Settings

Ensure that your AEM instances have sufficient heap and memory allocated. Insufficient resources can lead to package installation failures.

9. Bundle State

Ensure all necessary OSGi bundles are in the active state. Go to the OSGi console:

• http://<aem-host>:<port>/system/console/bundles
• Ensure there are no bundles in the INSTALLED or RESOLVED state that should be ACTIVE.

10. Check AEM Version Compatibility

Ensure that the packages are compatible with your AEM version. Sometimes, a minor mismatch in versioning can cause issues.

Example Workflow

Here’s a sample workflow to follow:

1. Rebuild Packages:

1. Upload via Package Manager:

   • Navigate to /crx/packmgr/index.jsp.
   • Click "Upload Package" and select your ui.apps and ui.content packages.

2. Install Packages:

   • Click on the uploaded package and select "Install".
   • Monitor the log output for any errors.

3. Check Bundle Status:

   • Navigate to /system/console/bundles.
   • Ensure all bundles are active.

4. Verify Permissions:

   • Ensure the user has the required permissions:
     • Go to /useradmin and check the permissions for the user or group handling deployments.

Common Issues and Solutions

• Permission Issues: Ensure the deployment user has crx:replicate permissions on the /apps and /content nodes.

• Out of Memory Errors: Increase the heap size of your AEM instance if you encounter out-of-memory errors during package installation.

• Corrupt Repository: Use oak-run check to ensure the repository is healthy:

By systematically going through these steps, you should be able to identify and resolve the issue preventing your packages from being properly installed. If problems persist, consider reaching out to Adobe support with detailed logs and steps taken for further assistance.

@keehwan1 Did you find the suggestions from users helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.