joshuatoepferyahoo.com

I see this has been viewed multiple times with no resolution. Are you still having this issue? I may be able to help you with your solution. If you utilize (depending on which version you are using) the server attributes you should be able to accomplish exporting from a lower (test) environemnt to production without messing up your connection. I've done some reseach on this for our team and is what I have come up with as a soltion. https://community.jaspersoft.com/documentation/tibco-jasperreports-server-administration-guide/v611/managing-attributes

We want to use the Jasper Rest API to schedule a Job in JasperServer, that is able to "Run As" another user. We setup a service login that we use as a generic Rest API login to be able to create the Scheduled Jobs. However, when running the report that service account's LoggedInUsername is what is appearing. Is there anyway I can pass LoggedInUsername to the report as a "Run As" situation, and not have it overridden by the service account i'm using in the Rest API? Or do I need to create a new parameter in the report that does a cacluation to handle this? Looking for some direction.

I get the same error in JasperServer 7.5.0 CE. Using the Web UI to delete a user I get the following error. 2020-07-31T10:49:35,829 ERROR BatchingBatch,http-nio-8080-exec-3:120 - HHH000315: Exception executing batch [java.sql.BatchUpdateException: Batch entry 0 delete from JIUser where id=5818 was aborted: ERROR: update or delete on table "jiuser" violates foreign key constraint "fk7caj87u72rymu6805gtek03y8" on table "jiaccessevent" Detail: Key (id)=(5818) is still referenced from table "jiaccessevent". Call getNextException to see other errors in the batch.], SQL: delete from JIUser where id=? 2020-07-31T10:49:35,830 ERROR SqlExceptionHelper,http-nio-8080-exec-3:131 - Batch entry 0 delete from JIUser where id=5818 was aborted: ERROR: update or delete on table "jiuser" violates foreign key constraint "fk7caj87u72rymu6805gtek03y8" on table "jiaccessevent" Detail: Key (id)=(5818) is still referenced from table "jiaccessevent". Call getNextException to see other errors in the batch. 2020-07-31T10:49:35,830 ERROR SqlExceptionHelper,http-nio-8080-exec-3:131 - ERROR: update or delete on table "jiuser" violates foreign key constraint "fk7caj87u72rymu6805gtek03y8" on table "jiaccessevent" Detail: Key (id)=(5818) is still referenced from table "jiaccessevent".

We are having issues with submitting jobs to the rest api using boolean parameters. We have tried the following variations (json): ..."parameters":{"parameterValues":{isDone:"true"}} ..."parameters":{"parameterValues":{isDone:["true"]}} ..."parameters":{"parameterValues":{isDone:true}} None of these work, when placing a non-boolean value in the field I get a request error. When I pass the variations of boolean through they are not returned in the response payload, and I'm only seeing false on the report. I'm not sure where else to go from here.

We are receiving an error message (listed below) when executing a PUT against a jasperserver v6.4.2 using the rest_v2 endpoint. The same json when put into postman works fine, just not via a spring template execution of the report. Is there something we are missing or can try? If there is logs we can pull or loggging levels we can add to get better results? Either way, we are looking for more information. 2018-12-07 10:27:34,533 ERROR ReportExecutionJob,quartzScheduler_Worker-1:366 - The report was not completed. An error occurred while executing it. (Error UID: 9734c6d7-d50a-4c1a-be1e-9eeabddd6c38) java.lang.ClassCastException: java.util.ArrayList cannot be cast to java.lang.Integer at net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.setStatementParameter(JRJdbcQueryExecuter.java:699) at net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.setStatementParameter(JRJdbcQueryExecuter.java:572) at net.sf.jasperreports.engine.query.JRJdbcQueryExecuter$1.visit(JRJdbcQueryExecuter.java:480) at net.sf.jasperreports.engine.query.JRAbstractQueryExecuter$QueryParameter.accept(JRAbstractQueryExecuter.java:163) at net.sf.jasperreports.engine.query.JRAbstractQueryExecuter.visitQueryParameters(JRAbstractQueryExecuter.java:666) at net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createStatement(JRJdbcQueryExecuter.java:465) at net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(JRJdbcQueryExecuter.java:297) at net.sf.jasperreports.engine.fill.JRFillDataset.createQueryDatasource(JRFillDataset.java:1245) at net.sf.jasperreports.engine.fill.JRFillDataset.initDatasource(JRFillDataset.java:723) at net.sf.jasperreports.engine.fill.BaseReportFiller.setParameters(BaseReportFiller.java:440) at net.sf.jasperreports.engine.fill.JRBaseFiller.fill(JRBaseFiller.java:554) at net.sf.jasperreports.engine.fill.BaseFillHandle$ReportFill.run(BaseFillHandle.java:123) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$SynchronousExecutor.execute(EngineServiceImpl.java:945) at net.sf.jasperreports.engine.fill.BaseFillHandle.startFill(BaseFillHandle.java:169) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.fillReport(EngineServiceImpl.java:1885) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$SynchronousReportFiller.fillReport(EngineServiceImpl.java:843) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.fillReport(EngineServiceImpl.java:1812) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportFill.runWithDataSource(EngineServiceImpl.java:1143) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportFill.runReport(EngineServiceImpl.java:1072) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportRunnable.run(EngineServiceImpl.java:967) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$SynchronousExecutor.execute(EngineServiceImpl.java:945) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.fillReport(EngineServiceImpl.java:651) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.executeReportUnitRequest(EngineServiceImpl.java:2068) at com.jaspersoft.jasperserver.api.engine.jasperreports.domain.impl.ReportUnitRequest.execute(ReportUnitRequest.java:67) at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.execute(EngineServiceImpl.java:529) at com.jaspersoft.jasperserver.api.engine.scheduling.quartz.ReportExecutionJob.runReport(ReportExecutionJob.java:836) at com.jaspersoft.jasperserver.api.engine.scheduling.quartz.ReportExecutionJob.executeReport(ReportExecutionJob.java:803) at com.jaspersoft.jasperserver.api.engine.scheduling.quartz.ReportExecutionJob.executeReport(ReportExecutionJob.java:704) at com.jaspersoft.jasperserver.api.engine.scheduling.quartz.ReportExecutionJob.executeAndSendReport(ReportExecutionJob.java:499) at com.jaspersoft.jasperserver.api.engine.scheduling.quartz.ReportExecutionJob.execute(ReportExecutionJob.java:248) at org.quartz.core.JobRunShell.run(JobRunShell.java:213) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557) 2018-12-07 10:27:34,534 ERROR ReportExecutionJob,quartzScheduler_Worker-1:366 - error.generating.report (Error UID: c0e62959-908e-4a3a-8875-37f5d60ccb32) org.quartz.JobExecutionException: Did not find report result for {paginated: null, maxPageHeight: null, maxPageWidth: null} at com.jaspersoft.jasperserver.api.engine.scheduling.quartz.ReportExecutionJob.getReportResultForOutput(ReportExecutionJob.java:747)

vinothkumar, did you ever get this working? Did you try the information in the wiki below? http://community.jaspersoft.com/wiki/no-query-executer-factory-registered-plsql-language-jasperserver-51

Does anyone else have this issue? with 6.2.0 CE?

While I appreciate the location of where the documentation is located. That's not really the point of my question. Giving vague answers gives me the impression that people lack the knowledge to answer the question. I'm looking for an answer as to what I can start looking at based upon I can login to the system, but all pages are throwing errors on the import of the css pages. All the corresponding javascript is being loaded correctly. I can even call the RESTful services. The entire build process gave my successful messages as every phase. You can see above my comments on the build process steps that I ran.

Just for Reference: Linux Redhat 6.2 Jasper Server CE v6.2.0 Java 1.7_b60 My steps are as follows: 1.) ./js-ant clean-config 2.) ./js-ant gen-config3.) ./js-ant build-ce4.) ./js-ant import-minimal-ce5.) ./js-ant deploy-webapp-ce Everything seems to be fine up to this point, no errors with any processes.

I changed the logging for the themes for log4j and I'm getting the following errors upon login: 2016-01-25 11:10:26,397 DEBUG ThemeCache,catalina-exec-13:115 - Cannot resolve theme element for : _themes/94A181B0/importExport.css2016-01-25 11:10:26,401 DEBUG ThemeCache,catalina-exec-14:115 - Cannot resolve theme element for : _themes/94A181B0/manageTenants.css2016-01-25 11:10:26,398 DEBUG ThemeCache,catalina-exec-12:115 - Cannot resolve theme element for : _themes/94A181B0/attributes.css2016-01-25 11:10:26,460 DEBUG ThemeCache,catalina-exec-22:115 - Cannot resolve theme element for : _themes/94A181B0/common/js_reset.css2016-01-25 11:10:26,460 DEBUG ThemeCache,catalina-exec-23:115 - Cannot resolve theme element for : _themes/94A181B0/common/base.css2016-01-25 11:10:26,581 DEBUG ThemeCache,catalina-exec-24:115 - Cannot resolve theme element for : _themes/94A181B0/common/layout.css2016-01-25 11:10:26,610 DEBUG ThemeCache,catalina-exec-1:115 - Cannot resolve theme element for : _themes/94A181B0/common/state.css2016-01-25 11:10:26,619 DEBUG ThemeCache,catalina-exec-25:115 - Cannot resolve theme element for : _themes/94A181B0/common/modules.css2016-01-25 11:10:26,642 DEBUG ThemeCache,catalina-exec-8:115 - Cannot resolve theme element for : _themes/94A181B0/common/controls.css2016-01-25 11:10:26,661 DEBUG ThemeCache,catalina-exec-7:115 - Cannot resolve theme element for : _themes/94A181B0/common/utility.css2016-01-25 11:10:26,738 DEBUG ThemeCache,catalina-exec-6:115 - Cannot resolve theme element for : _themes/94A181B0/common/dialog.css2016-01-25 11:10:26,757 DEBUG ThemeCache,catalina-exec-10:115 - Cannot resolve theme element for : _themes/94A181B0/dialog.css2016-01-25 11:10:33,193 DEBUG ThemeCache,catalina-exec-21:115 - Cannot resolve theme element for : _themes/94A181B0/attributes.css2016-01-25 11:10:33,194 DEBUG ThemeCache,catalina-exec-9:115 - Cannot resolve theme element for : _themes/94A181B0/importExport.css2016-01-25 11:10:33,204 DEBUG ThemeCache,catalina-exec-7:115 - Cannot resolve theme element for : _themes/94A181B0/dialog.css2016-01-25 11:10:33,207 DEBUG ThemeCache,catalina-exec-22:115 - Cannot resolve theme element for : _themes/94A181B0/manageTenants.css2016-01-25 11:10:33,216 DEBUG ThemeCache,catalina-exec-5:115 - Cannot resolve theme element for : _themes/94A181B0/common/js_reset.css2016-01-25 11:10:33,221 DEBUG ThemeCache,catalina-exec-24:115 - Cannot resolve theme element for : _themes/94A181B0/common/base.css2016-01-25 11:10:33,253 DEBUG ThemeCache,catalina-exec-13:115 - Cannot resolve theme element for : _themes/94A181B0/common/layout.css2016-01-25 11:10:33,281 DEBUG ThemeCache,catalina-exec-3:115 - Cannot resolve theme element for : _themes/94A181B0/common/state.css2016-01-25 11:10:33,288 DEBUG ThemeCache,catalina-exec-23:115 - Cannot resolve theme element for : _themes/94A181B0/common/modules.css2016-01-25 11:10:33,297 DEBUG ThemeCache,catalina-exec-17:115 - Cannot resolve theme element for : _themes/94A181B0/common/utility.css2016-01-25 11:10:33,327 DEBUG ThemeCache,catalina-exec-18:115 - Cannot resolve theme element for : _themes/94A181B0/common/controls.css2016-01-25 11:10:33,327 DEBUG ThemeCache,catalina-exec-4:115 - Cannot resolve theme element for : _themes/94A181B0/common/dialog.css

I fixed the Quartz issue, it seems that it could not find quartz tables under the new schema that was created. That has since been fixed. But I'm still getting the 404 issues with all pages. This does not just seem to be isolated to the login page. Thanks again in advance for any suggestions.

When I start up jasperserver I'm getting 404 on a lot of the included resources for the login page. Info: * Building Jasperserver-ce from source. *Build and deployment with no errors. Started up jasperserver with single error (but I don't think it's related): 2016-01-25 00:20:46,394 ERROR LocalDataSourceJobStore,QuartzScheduler_quartzScheduler- "SCHED_NAME": invalid identifier Resources that are missing: GET http://michigan.assisted.com:8080/jasperserver/_themes/8816E44B/attributes.css login.html:42 GET http://michigan.assisted.com:8080/jasperserver/_themes/8816E44B/importExport.css login.html:43 GET http://michigan.assisted.com:8080/jasperserver/_themes/8816E44B/manageTenants.css login.html:144 GET http://michigan.assisted.com:8080/jasperserver/_themes/8816E44B/dialog.css login.html:144 GET http://michigan.assisted.com:8080/jasperserver/_themes/8816E44B/common/js_reset.css login.html:144 GET http://michigan.assisted.com:8080/jasperserver/_themes/8816E44B/common/base.css login.html:144 GET http://michigan.assisted.com:8080/jasperserver/_themes/8816E44B/common/layout.css login.html:144 GET http://michigan.assisted.com:8080/jasperserver/_themes/8816E44B/common/modules.css login.html:144 GET http://michigan.assisted.com:8080/jasperserver/_themes/8816E44B/common/utility.css login.html:144 GET http://michigan.assisted.com:8080/jasperserver/_themes/8816E44B/common/state.css login.html:144 GET http://michigan.assisted.com:8080/jasperserver/_themes/8816E44B/common/controls.css login.html:144 GET http://michigan.assisted.com:8080/jasperserver/_themes/8816E44B/common/dialog.css 404 (Not Found) All the /rest_v2/* resources are being loaded by the browser. Any advise on where in the build process this would have been setup. Maybe there was a missed step or an warning message that I missed? Thanks in advance.

Before open source version discontinued their support of Oracle db, I had the system working. My problem was upgrading to the 6.2.0 version. I narrowed it down to the upgrade script did not set permissions on a table there by giving me problems.

Installing Jasperserver 6.2 on Linux Redhat 6.2 The original install of 6.0 worked fine, but I wanted to get the latest one installed. Installing via source code, by running the following: 1.) create database 2.) build ce 3.) import minimial - FAILS (I did this with verbose and debugging turned on.) Caused by: java.sql.SQLSyntaxErrorException: ORA-01950: no privileges on tablespace 'USERS' ... org.springframework.dao.InvalidDataAccessResourceUsageException: could not insert: [com.jaspersoft.jasperserver.api.metadata.user.domain.impl.hibernate.RepoTenant]; SQL [insert into JASPER.JITenant (tenantId, tenantAlias, parentId, tenantName, tenantDesc, tenantNote, tenantUri, tenantFolderUri, theme, id) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]; nested exception is org.hibernate.exception.SQLGrammarException: could not insert: [com.jaspersoft.jasperserver.api.metadata.user.domain.impl.hibernate.RepoTenant] Any Ideas?

iceey, When I built jasperserver from source, i noticed that several of the dependencies did not exist in my local maven repo. Make sure you are using the maven repo that comes with the jasperserver source download. in the default_master.properties files there is a property called... # Repo path (extra dependencies repository path) repo-path - make sure this points to the repository that comes with the source - Josh

jgilmore, A couple of questions. Did you install using the installer? Which version CE/Pro? Are you using a local database? Which one?

@djohnson53 I think I can use what's there, however, we are working on Linux so Waffle is not possible, but I get the idea. Thanks for your time.

Kalpesh, Can you add a little more information, like are you using the ce or pro. Are you building your own jmxml using the JasperReports Studio? or are you creating a query resource? Thanks, - Josh

@hozawa, I think you might have missed my questions, let me try to rephrase. I want external authenication via our own security. However, I still want to keep Jasperserver's original authentication, so if I click the logout link, i can then log in via the jasperadmin account. When I use my custom proxyAuthenticationProcessFilter, I cannot ever login to the Jasperserver using the jasperadmin account. When the basic auth request comes in my proxyAuthProcessFilter picks up the authentication but fails to authenticate jasperadmin. Do I force my process filter to fall throught on authentication, and if I do will the filter chain pick up the authorization for jasperadmin? Or do I need to have my custom process extend a class to pick up basic auth?

Daniel, Jasper Reports has its own JRXML report definition. I am not aware of anything that will do a MS Access translation to JRXML. Saying that, it shouldn't be that hard to replicate the report in JasperReports Studio. Hopefully that helps. - Josh

Daniel, If you could clarify a couple of things, it might help resolve your issue. What sort of tools do your uses currently use to generate the report with MS Access? or do they use SQL? When you say you are now using Jasper Studio are you using it as a standalone IDE to run reports?

Details: 6.0.1 CE We are in the process of upgrading our old 3.5.3 JasperServer. I am using the applicationContext-externalAuth-template.xml to integrated our own NTLM signal sign on, however, when I want to login as the jasperadmin it ignores my login and logs me as myself. When I create my own filter, and not use the proxyAuthenticationProcessFilter, the system works better, but I get other weird errors. I can post more information as needed to help with this problem. Thanks in advance for any help.

I don't know if you resolved this problem yet, but here is my 2cents. I could not access the jaspersoft maven repo either, so I updated my default_master.properties file to point to the repo that came with the jasperserver-xx-src.zip.

I tried to upload an image, but that functionality doesn't seem to be working.

I have successfully, built the JasperServer CE on Redhat 6.2 from source. However, now that it is running, I am having problems with themes, as in ... there is none. I'm reading through the docs on customizing themes, but I don't see anything on installation. Can someone point me in the right direction? Thanks in advance for any help.