Hi Avinash, Thank you for the info, it seems to work! Interestingly, Adobe Support said you could not refresh a bundle like this via cURL Do you have any idea why this is necessary in our case? Ideally the code would come back properly between restarts of the AEM instance. This will make things...

AEM 6.5 SP13 We have a code bundle with a search component that is in a failed state when the instance is restarted. Looking around /system/console we see what looks like a conflict with jersey client / jersey core libraries when it's broken (i.e. after instance is restarted). So far, I have d...

Related, I found this post https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/crx-synchronization-of-two-aem-6-5-instances/m-p/441812 by @tadreeves (the blogger referenced earlier). I'm particularly interested in the following:    The other thing that many companies will do, f...

Hi Saravanan,  Thanks for pointing me to that blog. I've seen the blog before for other articles and it's good. This article doesn't really go into the details of cold standby configuration or how reliable it is. It did confirm clustering in previous versions of AEM was not reliable. I think I'll ne...

We never figured out why this was happening. After performing the upgrade again, the error was fixed. It appears something went wrong in the initial upgrade, or in the transfer of that instance to a new server.

I recently opened a ticket with Adobe support re: HA and disaster recovery options for AEM 6.5. Unfortunately, the engineer I spoke with didn't have much experience with it and referred me to some documentation, and said support could not assist with the configuration. I found this odd, especially g...

It seems the indexcopier warnings will go away once the index is rebuilt?The warning logs don't mention it's being rebuilt but I think that may be happening as the warnings are not repeated (for me) on subsequent restarts of AEM.My particular warning was on a relatively newly created index and on an...

FYI -  I noticed my profile did not have the following property:cq.authoring.editor.page.showOnboarding62 = false - adding this property seems to make the pop up go away - however my profile did have the following property: granite.shell.showonboarding620 = false - but this did not prevent the issue...

Hi Arun, There was nothing in the error log. Is there a particular logger that could capture this type of thing? If so, please give class name. Thanks!

Hi Arun, Thanks for the suggestion, unfortunately users do seem to have full permissions on their /home/user/I/xxx node - including preferences ...