We are using the workflow to 'Dam Update Asset' to create renditions for all the new assets that are added in AEM.And since yesterday we see the following error appearing in the log files:18.07.2017 07:24:15.270 *ERROR* [JobHandler: /etc/workflow/instances/server1/2017-07-18/model_6797382541536:/con...

I found the issue, I skipped a step in the upgrade documentation.I did not run the unpack of the new version of the AEM jar. After changing that, the upgrade worked perfectly.

Hi,No after the upgrade I don't see the system user(s).However we did follow the migration steps and it does not mention adding additional users.Are there still steps to need to be executed after the upgrade?

After following the documentation on : Upgrading to AEM 6.3​ , we have successfully migrated the repository from 6.1 to 6.3, however when we restart AEM we see a few errors in the log file.Example:09.07.2017 14:14:09.219 *WARN* [Shell Script Executor Thread for diskusage.sh] org.apache.sling.jcr.res...

Hi,I followed the documentation on https://docs.adobe.com/docs/en/dispatcher/permissions-cache.html to configure the auth_checker to check the permissions. When I check the dispatcher log I see that the authentication checker is used, but the url is always called on the publish instance. Is it possi...

Another update: I debugged the sling engine code to determine when the alias was resolved and the sling code tries several strategies to resolve the content node, one of them is starting at the root node ('/') and adding everything until the path is resolved or an alias is found in the aliasMap. Gra...

Update: I am able to reproduce the issue on a "new" publish instance, I also installed all the hotfixes for AEM 6.1 just to make sure that isn't an old problem.I changed the Sling Authentication to allow anonymous access. I even gave the anonymous user access to read/write/.... for all the paths usi...

        After trying to reproduce the issue on a new publish instance I noticed that a request filter is also not working. Is it possible that some filters are disabled?

Yes it is AEM 6.1

I checked the security settings, the "Allow Anonymous Access" was already selected. And I provided read-only access to everyone on the /content/www-company-com/ node (and all the subnodes).Still no success, the page is "not found"RegardsSteven