ReportServer Forum

lacma

Member

Registered: 2025-01-15

jrxml format is not compatible with the format in ReportServer

Hello
I am completely new to the Report Server environment.
System Environment:
- Windows 11
- ReportServer RS4.7.2-6108 Community Edition
- Zulu 11.76.21 openJDK
- apache Tomcat 9.0.98
- Jaspersoft Studio 7.0.1

So far I have been using JasperReport Server community edition. But now this solution is no longer freely available. Now I am looking for an alternative solution to run reports.
I am using various reports based on Jaspersoft Studio. I would now like to import these into ReportServer.
The import works, but the execution fails because apparently the exported jrxml schema cannot be executed correctly.
There are error messages:
/******/
-...net.datenwerke.rs.core.service.reportmanager.exceptions.ReportExecutorException: The report could not be executed: SAXParseException: cvc-complex-type.3.2.2: Attribute 'uuid' is not....
/******/

if I delete the UUID's element, the next faulty element follows.
apparently my jrxml format is not compatible with the format in ReportServer.

Can someone tell me which Jaspersoft Studio version the jrxml format in ReportServer is based on?

Thank you very much for your support.

Last edited by lacma (2025-01-15 08:07:09)

IF_Alexander

Moderator

Registered: 2020-07-03

Website

Re: jrxml format is not compatible with the format in ReportServer

Hello lacma,

ReportServer currently supports JasperReports version 6.21.3. You can verify this under Administration -> System Console -> Internal Java Libraries.

The following resource may help you: https://github.com/TIBCOSoftware/jasperreports
breaking backward compatibility of source *.jrxml report template files and *.jrtx style template files by replacing the Apache Commons Digester based parsers with Jackson XML object serialization. *.jrxml and *.jrtx files created with version 6 or older can no longer be loaded with version 7 or newer of the library alone. The conversion from the old file formats to the new file formats and back can be made using Jaspersoft Studio 7 and later versions of it;

Please share the complete error message to identify the specific schema elements causing the problem.
ReportServer currently supports JasperReports 6.x, there are plans to analyze compatibility with newer JasperReports versions.

Best regards,

Alex

lacma

Member

Registered: 2025-01-15

Re: jrxml format is not compatible with the format in ReportServer

Thank you Alex

You will find the error message below.
I hope it is complete enough:

/*****/
Report could not be executed. {"error":"SAXParseException: cvc-complex-type.3.2.2: Attribute 'uuid' is not allowed to appear in element 'jasperReport'.","report_id":6736,"report_name":"BN","base_report_id":6736,"base_report_name":"BN","executing_user_id":6,"report_output_format":"PDF","report_key":"4397b1b4cfdc5b76446348f931b47f6b66a9192e"} net.datenwerke.rs.core.service.reportmanager.exceptions.ReportExecutorException: The report could not be executed: SAXParseException: cvc-complex-type.3.2.2: Attribute 'uuid' is not allowed to appear in element 'jasperReport'. at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:280) at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:161) at net.datenwerke.rs.core.server.reportexport.ReportExportServlet.executeReport(ReportExportServlet.java:563) at net.datenwerke.rs.core.server.reportexport.ReportExportServlet.doExportReport(ReportExportServlet.java:444) at net.datenwerke.rs.core.server.reportexport.ReportExportServlet.exportReport(ReportExportServlet.java:367) at net.datenwerke.rs.core.server.reportexport.ReportExportServlet.exportReportViaSession(ReportExportServlet.java:358) at net.datenwerke.rs.core.server.reportexport.ReportExportServlet.doGet(ReportExportServlet.java:162) at net.datenwerke.rs.core.server.reportexport.ReportExportServlet$$EnhancerByGuice$$1845850292.GUICE$TRAMPOLINE() at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:74) at com.google.inject.persist.jpa.JpaLocalTxnInterceptor.invoke(JpaLocalTxnInterceptor.java:64) at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:75) at net.datenwerke.security.service.security.aop.SecurityCheckInterceptor.invoke(SecurityCheckInterceptor.java:112) at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:75) at com.google.inject.internal.InterceptorStackCallback.invoke(InterceptorStackCallback.java:55) at net.datenwerke.rs.core.server.reportexport.ReportExportServlet$$EnhancerByGuice$$1845850292.doGet() at javax.servlet.http.HttpServlet.service(HttpServlet.java:529) at javax.servlet.http.HttpServlet.service(HttpServlet.java:623) at net.datenwerke.rs.core.server.reportexport.ReportExportServlet$$EnhancerByGuice$$1845850292.GUICE$TRAMPOLINE() at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:74) at net.datenwerke.security.service.security.aop.SecurityCheckInterceptor.invoke(SecurityCheckInterceptor.java:112) at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:75) at com.google.inject.internal.InterceptorStackCallback.invoke(InterceptorStackCallback.java:55) at net.datenwerke.rs.core.server.reportexport.ReportExportServlet$$EnhancerByGuice$$1845850292.service() at com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:290) at com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:280) at com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:184) at com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:89) at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85) at com.google.inject.persist.PersistFilter.doFilter(PersistFilter.java:94) at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82) at com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:121) at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:133) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:168) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:168) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:482) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:660) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:346) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:396) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:937) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1791) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1190) at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63) at java.base/java.lang.Thread.run(Thread.java:829) Caused by: java.lang.IllegalArgumentException: Could not execute report: org.xml.sax.SAXParseException; lineNumber: 2; columnNumber: 202; cvc-complex-type.3.2.2: Attribute 'uuid' is not allowed to appear in element 'jasperReport'. at net.datenwerke.rs.base.service.reportengines.jasper.JasperReportEngine.executeReport(JasperReportEngine.java:314) at net.datenwerke.rs.base.service.reportengines.jasper.JasperReportEngine.doExecute(JasperReportEngine.java:108) at net.datenwerke.rs.core.service.reportmanager.engine.ReportEngine.execute(ReportEngine.java:146) at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:246) ... 50 more Caused by: net.sf.jasperreports.engine.JRException: org.xml.sax.SAXParseException; lineNumber: 2; columnNumber: 202; cvc-complex-type.3.2.2: Attribute 'uuid' is not allowed to appear in element 'jasperReport'. at net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:285) at net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:268) at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:257) at net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:235) at net.datenwerke.rs.base.service.reportengines.jasper.JasperReportEngine.executeReport(JasperReportEngine.java:148) ... 53 more Caused by: org.xml.sax.SAXParseException; lineNumber: 2; columnNumber: 202; cvc-complex-type.3.2.2: Attribute 'uuid' is not allowed to appear in element 'jasperReport'. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.processAttributes(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1892) at net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:281) ... 57 more

IF_Eduardo

Administrator

Registered: 2016-11-01

Website

Re: jrxml format is not compatible with the format in ReportServer

Hi lacma,

as alex_aust mentioned, the error "Attribute 'uuid' is not allowed to appear in element 'jasperReport'" occurs because ReportServer does not yet support compatibility with JasperReports 7 syntax. To resolve this, please use the JasperReports 6 syntax instead. You can convert your report to JasperReports 6 syntax using the converter available in Jaspersoft Studio 7, as alex_lust suggested.

Regards,
Eduardo

blearyeye

Member

Registered: 2026-04-16

Re: jrxml format is not compatible with the format in ReportServer

After reading through this, I'm confused. I'm using Jasper Studio 7, which produces the tag uuid. I've set compatibility mode to 6.20.6 and am still getting uuid. This Stack Overflow question says that the tag was introduced in JasperReports 4.6.0.

So apparently I would have to go back to a truly ancient version of Jasper Reports that does not exist any more. For most applications of a Jasper Report, the uuid is not needed. So a hack is to write a script to strip them out.

Last edited by blearyeye (2026-04-20 21:11:05)

IF_Susanne

Moderator

Registered: 2025-11-26

Re: jrxml format is not compatible with the format in ReportServer

Hello blearyeye,

Thank you for your report. We plan to analyze the issue and explore potential solutions in a future version.

Best regards
Susanne