lucianc wrote: The bug is fixed now. You can test (and use) the fix by including the attached jar in your web application. There are also a couple of workarounds to the issue. If you can't/don't want to use the fix, I'll post them. Regards, Lucian [file name=jasperserver_api_engine_impl_0_fix.jar size=2085]http://www.jasperforge.org/components/com_joomlaboard/uploaded/files/jasperserver_api_engine_impl_0_fix.jar[/file] Hello. Can you describe how exactly should I use this fix with JasperIntelligence and/or how to solve this problem without this fix?