Changing the Symlink for an AEM Instance Creates Critical Issues


AEM 6.x


This issue relates to a scenario where automatic uninstallation of a CFP(Cumulative Fix Pack) or a SP(Service Pack) is observed. Removing the symlink can cause severe damage to the instances, for example missing nodes or data which could lead the AEM instance to an unusable state.


The cause for this issue is the manual change or update in the symlink used for AEM.

These changes are generally made out for storage changes but can cause severe problems as the AEM can no longer find the SP/CFP zip files in the old path.


The symlink should not be changed for the running AEM instances.


Get help faster and easier

New user?