After consulting via ticket this issue is really already taken care of and will be fixed in SP 18. 

The Excel files are created ok, it is really just the startup log error. I was wondering if anyone else is having this issue and has a solution, or if we should simply wait for next SP.

Hello everyone,after the upgrade to the current Service Pack, we are getting the following error on startup. It references the org.apache.poi.ooxml.POIXMLRelation class, so I think it regards the OSGi bundle wrapper for the Apache POI library (com.adobe.granite.poi). This we actually use in our appl...

In the end there were probably two faults, not relating directly to AEM:There was something wrong with the CentOS Winbind daemon which wasn´t connected properly to our Active Directory server. That was restarted.We were accessing the JMX via URL servername.xx.yyy/..., where xx.yyy is our company dom...

Hello Jitendra, everything seems to be configured and working normally, as on our production and other servers. All bundles are up and running, configuration should be also ok. It is really puzzling.  

Hello community,recently, we are getting a strange 404 error when accessing "External Identity Synchronization Management". It´s the same for every country configuration we have:       The configurations were working well in the past, importing user accounts from LDAP and users were testing our appl...

Apache Sling Request Parameter Handling configuration for the Default parameter encoding is set correctly to UTF-8, that is not the problem.With lack of any other answers the workaround mentioned here is still the best approach https://github.com/Adobe-Consulting-Services/acs-aem-commons/pull/1030

Hello Kiran,thank you for the answer. Yes, we are using the default one and the encoding is set to UTF-8. I think that shouldn´t be a problem, because the body of the emails is always displayed correctly and if we set the subject in code viaorg.apache.commons.mail.HtmlEmail.setSubject() then the sub...

Hello,we have a long-term problem with encoding in email subjects, where characters like "šáěíéščřý" are not shown correctly. Until now, we have been changing the subjects to use basic ascii letters. But now we are expanding to russian customers, and with azbuka (cyrilic) letters we can no longer do...

Thank you for the info, I tested it now and it seems to work! Now I see only the logs about the service/servlet registrations again.Since I didn´t find an existing config in system/console/configMgr I´ve added the configuration manually through CRX:/apps/system/config/com.adobe.granite.maintenance.i...