lasinir

I had the same problem the first time I attempted to install 3.7CE onto a linux Distro that had MySQL already persent. The fix that I found was that the installer does not look in the system path for the 'mysql' application. Thats why as part of the install process, there is a parameter box to say where is the mysql tools. If you dont enter this correct for your system it will fail the install. The default I has there is where it would put the mysql tools if you used the default mysql install as bundled with JS 3.7 CE. This was completely different to where the distro's repository installed mysql. Hope this helps in some small way. -lasinir

OKay, I had this occuring in my migration from 3.5CE to 3.7CE, but only when I started to update/make changes to the reports via ireport (3.7.3). Previously I copied the JRML file and pasted into 3.7.3 and it ran with out a problem. But when I started to edit it and change the reports I was running, the datafields started corrupting the same as the ones you mentioned, "[@dks434" and so on. But strangely enough I stumbled accross the fix (or atleast it fixed it for me). I went into the dataset of the report that was causing the problem, and edited the query, I then did a read fields and at this point my items that were in the field type column changed. Click ok to commit this update, and hey presto, no more corrupted entries. Of course I was trying other things to fix it ,but none of them had this level of visible change to something that might actaully be about data mis-formating. Hope this helps and let me and others know if it does. -lasinir

You really should read other posts, even ones who's subjects are in no way related to what you want. See how to get anon access to reports working with JS 3.7 CE in my post: http://jasperforge.org/plugins/espforum/view.php?group_id=112&forumid=102&topicid=609&page=2#77631 Let me know how it goes for you. LasiniR

Okay. I know we had this working under 3.5. but I recently upgraded to JS 3.7 CE (and my working version of 3.5 is formated ;). I have tried all the solutions presented in this posting, (and still have the flowVoter bean change to add ROLE_ANONYMOUS and /fileview/**=ROLE_ANONYMOUS,ROLE_USER setting) but none of these worked. But then after gonig back almost 20 pages in forum post's I came across this obscure thread. http://jasperforge.org/plugins/espforum/view.php?group_id=112&forumid=102&topicid=71124 And then after I made the change mentioned (adding the line in bold): Change the entry in applicationContext-evetns-lgging.xml - Exactly what sherman told me to. <bean id="accessContext" class="com.jaspersoft.jasperserver.api.logging.access.context.impl.AccessContextImpl"> <property name="clientClassFactory" ref="mappingResourceFactory"/> <property name="loggingContextProvider" ref="${bean.loggingContextProvider}"/> <property name="userAuthorityService" ref="${bean.userAuthorityService}"/> </bean> Then a restart of the services and bingo!. anonymous access started working again. Hope this helps some one. or more than one.

Check this post http://jasperforge.org/plugins/espforum/view.php?group_id=112&forumid=102&topicid=46863 Specifically the entry from mmflynn. This worked for me. -Randy

Thanks! This helped a lot. I was trying to get direct anonymous access to a Dashboard web page (scheduled refreshing 15 minutes). I am using JasperServer Communtity Edition version 3.5.0 (with 3.5.3 jasperreports.jar).