crax Posted October 15, 2008 Share Posted October 15, 2008 I have been using jasperserver 3.0.0 with ireport 3.0 and everything has mostly worked fine.I just installed ireport 3.1.1 and when trying to send a report up to the server through the repository navigator, I get an error when adding a new report:Error:com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequenceIf I open an existing report and modify it, I can update the report on the server by right clicking the Main.jrxml and choosing Replace with current jrxml. Then, when I run the report form the report server, I get the Invalid byte 1 of 1-byte UTF-8 sequence error.Is 3.1.1 not compatible with jasperserver 3.0.0 or is there something else I need to do?I've tried creating a new report from scratch and also using reports originally done in 3.0 Link to comment Share on other sites More sharing options...
crax Posted October 15, 2008 Author Share Posted October 15, 2008 Actually, I can create brand new reports and new report units from 3.1.1 and it does seem to work.However, if I open a report created in 3.0, edit it and then save it and reopen it, I get the Invalid byte 1 of 1-byte UTF-8 sequence or if I upload it to the reportserver, I get that same error as well. Link to comment Share on other sites More sharing options...
Gaby38 Posted October 16, 2008 Share Posted October 16, 2008 It's the same thing for me. If I edit with iReport nb 3.1.1 a jrxml file from a report unit created with iReport 3.0.0 I get the same error. I was thinking that this was due to the fact that my report had a chart.And after if I try to open with iReport 3.0.0 the jrxml damaged by iReport 3.1.1 I get an error saying that the size parameters of the report are not compatible with the band size definition (or something like that)Under 3.1.1 I didn't find all the shortcuts icons of the tools allowing to center, expand, adjust horizontal and vertical size of a cell to the border limits.So, for me, iReport 3.1.1 is less convenient than iReport 3.0.0Gaby Link to comment Share on other sites More sharing options...
crax Posted October 16, 2008 Author Share Posted October 16, 2008 Mine don't actually have a chart. I don't know if 3.1.1 converts the report in someway when it saves it, but I can do the following: I open a 3.0 report in 3.1.1. I Make a few edits and I can preview the report just fine with or without an active datasource. If I save and close the report and then reopen it, I get that Invalid byte 1 of 1-byte error which prevents me from doing anything with the report. I don't know if this is something to do with the saving or what as I can open any 3.0 created reports and preview them just finee. The problems all arise once I save them. Link to comment Share on other sites More sharing options...
Gaby38 Posted October 27, 2008 Share Posted October 27, 2008 I saw on this forum (or IReport forum) that this could be due to the version of Jasperreports. I upgraded the jar of jasperreports to 3.1.0 in the lib directory of WEB-INF in jasperserver and I always get the same error if I update a report created under IReport 3.0.0. Link to comment Share on other sites More sharing options...
mmflynn Posted October 27, 2008 Share Posted October 27, 2008 I was able to reproduce the problem but do not have an explanation for you. I submitted a bug using the Tracker feature: 3218 Invalid byte 1 of 1-byte UTF-8 sequence Mary Link to comment Share on other sites More sharing options...
mwinters Posted November 1, 2008 Share Posted November 1, 2008 I noticed something similar with 3.1.1 when I had text to display that includes a lone single quote '. It would compile but say "No pages in Document". I could save it, but get that same "Invalid byte 1 of 1-byte UTF-8 sequence" error when I tried to load the jrxml file. Link to comment Share on other sites More sharing options...
Gaby38 Posted November 1, 2008 Share Posted November 1, 2008 In fact, there is a thread on the iReport forum about that trouble :jasperforge.org/plugins/espforum/view.phpand it seems there is a workaround : load the plugin "XML and Schemas"I tested that and for me it is working.For your information Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now