When deploying Jasper Reports getting error message

Question

Hi I created a simple report using iReport 4.5.1 and when I tried to deploy the report in JasperSoft (Ver 4.5) I am getting the following error message even thought I am selecting the correct JRXML file

The selected JRXML could not be parsed. You might have selected the wrong file.

What could be the issue.

I am using iReport designer to design my reports.
Database: Oracle 11g
I have created a Data Source in JaseperSoft - test connection successfull
I am getting the error message only when I click the browse button to upload the JRXML file when i tried to upload a report file...

Please help....

Answer 1

This error can occur when attempting to deploy a report that uses stored procedures.

You can find this issue at http://jasperforge.org.

This article is about how to call stored procedures from JasperReports.

Answer 2

Try to deploy the report using the jdeploy tool on https://sourceforge.net/projects/jaspertools/?source=directory

Answer 3

Solution: By default JasperSoft® Studio tries to save and upload the JRXML's in the latest possile JRXML version which may not be compatible with the parser on the server side. You can configure the version used by the studio. Go to Window > Preferences > Jaspersoft Studio > Compatibility and in the Source .jrxml version set the version to 6.2.1. Then open your reports, do a minor change and re-save it. This should re-generate the JRXML that is compatible with previous JasperReports version. You can also set the same compatibility setting on project level by right clicking on the project folder in the Project Explorer > Properties > Jaspersoft Studio > Compatibility

https://community.jaspersoft.com/wiki/error-message-selected-jrxml-could-not-be-parsed-when-trying-update-jrxml-files-tibco

Answer 4

I have created an automatic build option for maven reports. Anyone that is interested please read: http://the-consultants-blog.blogspot.be/2013/06/deploy-jasperreports-with-maven.html

It might come in handy with deployment problems or with mass deployment of jrxmls.