I've checked your case and assume this is because of one (ore more) of the submissions has "Issue date" EMTPY or NULL. That's why it's not working only in "Issue date" filter and DESCEND combination. Null values should go right on the first result page - thats why it throws exception. To check this - you choose ASCEND - it works ok for all listing pages - excep LAST one - so that NULL issue date submission is sorted to be last. We know that this field is obligatory - maybe error was during manual restore\backup process or straight DB edit.
One thing I can advise to know it for sure - check the table in database or query DB with SELECT statement to detect that cpecific record and UPDATE it (or them) with some year. Hope this will help you! Good luck! -- View this message in context: http://dspace.2283337.n4.nabble.com/Help-with-DSpace-Internal-Server-Error-tp4677083p4677098.html Sent from the DSpace - Tech mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
