When loading a page in the classic UI with SOLR configured, the DAM sidebar appears empty at the following error is thrown in the error log:org.apache.solr.common.SolrException: can not sort on multivalued field: jcr\:content\/jcr\:lastModified_string_sortDoes anyone know a fix for this?

I just setup an AEM 6.1 instance with SOLR, everything is working great but i'm getting tons of this error message in my error log:04.01.2016 12:55:33.683 *WARN* [pool-6-thread-3-SendThread(localhost:9983)] org.apache.felix.jaas No JAAS module configured for realm ClientI can add a new JAAS configur...

Is this a production environment or a test environment?Did you upgrade from 5.4 to 6.1 directly, or were there other upgrades in between?

Sounds like you may want to customize the workflow process for adding/updating DAM assets.  You could have a custom workflow step added to the OOTB workflow process that extracts the extension and stores the data on the node, you'd then be able to add this to your metadata schema.

On the Publish instance, if you go to /crx/de and login (using the login button top right), then go to siteadmin - is it still blank?

Not out of the box.  You'd need to write some code to do that for you.

You know, it actually looks like it's not supported.See here: http://www.slideshare.net/justinedelson/demystifying-oak-search slide 40 and 41, specifically states that synonyms are not supported.

I believe you can utilize the tilde (~) to do this.

Try this:/jcr:root/home/users//element(*, rep:User)Also, the query debug tool is a great way of playing with queries: http://localhost:4502/libs/cq/search/content/querydebug.html

We ran into the same issue.  If you check the error log you're probably getting a generic error from T&T.  After some back and forth with Adobe, it turned out it was because the length of the path from AEM was too long for T&T to handle, which is likely why one of yours is working and the other isn'...