tkavanagh

There is an existing forum thread with the same error. Hopefully, this can help fix this issue: http://jasperforge.org/plugins/espforum/view.php?group_id=112&forumid=102&topicid=18324 Looks like a comment out part of the Spring Bean in WEB-INF/applicationContext-logging.xml is the fix in this case.

Additional info/question from Jason: Do you have any recommendations on handling this? I was thinking of optionally disabling just the cross site scripting issue in the port. Any thoughts? I'm also wondering what is triggering that. We are just passing from Apache to localhost (tomcat) via proxy. Info from Tony: It sounds to me like you are hitting a bug. It would be good if you can capture a stack trace (or full set of error info) from the jasperserver/WEB-INF/logs/jasperserver.log. Or the tomcat/logs/*.log/.out files - Which ever has the most information. (Assuming that there is something to see on the servers side.) It would be nice to fix this so that you don't have to turn off the csrf in the port. The error message says that the Token is not being generated. This token is generated on the client (browser) side using javascript and sent to the server. Is it possible for you to go in (with Firebug or something similar) and see if there is an actual token generated and being sent? If it's not then we would expect the error. Also, which browser are you using, maybe try a couple of additional very up to date browsers? Interesting too about the proxy. Can you try Browser to -> localhost server (ie with no proxy anywhere)

Ah, there is a new permission added as of 4.0 or perhaps 4.1. This is the execute permission. So, I believe that in order to be able to view a report/pdf/etc the user will need this execute permission. But the execute permission will not allow a use to delete the same report. Also, the docs/JasperReports-Server-User-Guide.pdf should have information on this too (I'll have to take a look to refresh my memory!).

That does look famililar... but the errors initially reported by the Spring Framework, which we use, can be confusing because the "real" error is usually lower down in the error stack. So, the best thing will be to attach the full log (or fully java stack trace) to this forum thread. Probably, the most common problem is some kind of database connection issue. So, you might try and look lower down for a error with the database "connection"

Yes, the thing to do will be to look in your tomcat log. (and of course I am assuming that you are using tomcat as the Application Server). So, go to <tomcat-home>/logs and look at the catalina.log. If you are getting a 404, then most likely the JasperReports Server Web App did not startup successfully. If you can find this log (there are a few logs in the folder, which ever one is largest probably contains the errors). You can attach the log to this thread and we can take a look... Also, make sure your tomcat is running too!

The validation rules are here: jasperserver/WEB-INF/classes/esapi/validation.properties And there is a security prop file with some on/off switches. So you could try a couple of those: jasperserver/WEB-INF/classes/esapi/security-config.properties ######################################################### # Jaspersoft Security Configuration ######################################################### security.validation.input.on=true security.validation.csrf.on=true security.validation.sql.on=true encryption.on=false

For 4.5.0, there have been security enhancements based on the owasp framework in order to prevent cross-site scripting and other similar attacks. There are a number of characters which are now dis-allowed. Could it be that there is a user with a "<" or ">" in the name? (just looking at the error output). But in general, if there is an error blocking you based on the security settings, you can temporarily turn off the security - just to verify that you can get farther. And to help track down the problem. I'm looking for where the doc is for turning off the CSRF security ... hmm, but I don't see it. The release notes say this: * Security - The JasperReports Server now has enterprise-grade security through the integration of a comprehensive security framework. This new security framework protects the server against common security threats. Customers can configure the security settings (switch on/off or change the security rules) based on their perceived threat level. But don't say how to switch off (! :-( I'll see what I can find out...

Hi Anand, Adding a link the the more complete discussion at this thread: http://jasperforge.org/plugins/espforum/view.php?group_id=112&forumid=102&topicid=94750 There is an internally logged bug on this installation error. Also, wondering if installing to an existing postgresql instance will succeed. Thanks.

Hi Chadd, I think I have good news that this bug is fixed in our most current version (should be coming out today) which will be 4.5.0. If you get a chance to look at this in 4.5.0, let us know either way. Thanks!

Hmm, that sounds like a bug. Can you double-check it and make a bug/tracker item?

Nice work getting this going. This is actually a known issue (reported in the bug tracker and in the 4.2.1 release notes - although easy to miss this). However! The good news is that MySQL 5.5 is now supported as of the JasperServer 4.5.0 release. And that release is going out *today* (2012-01-16). So, please take a look at 4.5.0 when you get a chance.

Oops, I just noticed that you are talking about MS SQL Server (not MySQL!). There are some users who are running with SQL Server from the Community (ie non-commercial). They have modified the postgresql or mysql db scripts so that they are SQL Server syntax. So, you can do a Forum search to find those entries. The SQL Server is "certified" under the commercial version of the product (which means that QA runs through a full cycle of testing from end-to-end). But to get it running under Community you just need to get the DB setup and then add the sql server specific entries to the database config files. (See chapter 6.1 of the Install Guide for some info on manual DB setup). And you will need the SQL Server JDBC driver (which can be downloaded from microsoft). (Also see section 6.3.4 "JDBC Drivers"). The jasperserver/WEB-INF/hibernate.properties will need to correct hibernate dialect for SQL Server too. SQL Server metadata.hibernate.dialect=com.jaspersoft.ji.hibernate.dialect.SQLServerJICustomDialect I believer that class is actually part of the Community code base. So should be available.

Yes, the JRE/JDK can be configured for JasperServer. Basically, the *real* configuration is in the startup scripts for your Application Server (for instance Tomcat or JBoss, etc). So, let's say that you use Tomcat. Tomcat will look for the JAVA_HOME environment variable in order to find the Java that Tomcat will start up with. So, you can set (or change) the instance of Java pointed to using your environment variable setting. I would suggest taking a look at the Install Guide because it also points out the names of the script files that are used to start tomcat and JBoss. It would be Chapter 6 of the Install Guide. See section 6.2 "Setting JVM Options for Application Servers"

Yes, we definitely support MySQL. However, the used to be a problem with MySQL 5.5 (ie the most current MySQL version) because of reserved word changes in the newest MySQL. But the good news is that JasperReports Server 4.5.0 now supports MySQL 5.5 *and* 4.5.0 is being released today! The best way to install to MySQL 5.x is to use the "war file distribution zip" (which is file jasperreports-server-cp-4.5.0-bin.zip) There is an "auto-install" procedure where you add you DB settings info to a property file - and then install from the command line. Please download the Install-Guide PDF. And take a look at Chapter 5. Also, the release notes give a brief description of how to install with the auto-install. (The binary installers only install to the postgresql database).

I think that this is a reported bug - ie the install not working when the locale in not set as a default en_US. Let me ask you about how the install was done. I assume that you were installing a "bundled" tomcat and a "bundled" postgresql? (ie the installer puts those packages on your system for you). Would it be possible to try and do an install to an already existing version of postgresql? I will need to do some testing myself around this and see if the default lang setting causes a problem on an already existing postgresql (I would expect that it would not).

Good that you found the hostname issue and fixed it. There is an item in the Install Guide Troubleshooting section that has some info on this. Now that you have a 404 error, there is probably a tomcat startup error. So you can look in the tomcat logs (and post them) and see what is going on. By the way, postgresql and tomcat can be started separately by: (first clear the tomcat logs) cd <js-install> ./ctlscript.sh postgresql start (see that postgres looks good). ./ctrscript.sh tomcat start (then look at the tomcat logs and see what can be seen)

Hmm, I'll take a look at what is posted. I think that there haven't been changes since 4.0 so the 4.0 version should be good for connecting to 4.2.1 or any of the 4.x releases.

Hi the samples/php-sample files were out of date and were indeed based on an old php version. These old versions are now deprecated (ie no long supported by Zend). The php-sample has been updated for the next release 4.5.0. It comes out in a couple of weeks. However, if you pull down the trunk code of the samples/php-sample it is updated and supported php 5.3 and above. Maybe I should post the new files directly to this thread? Would this help?

It seems like everything is working except the "import" operation fails. And the import operation puts all of the required "core" resources into the jaspersever database. So, for whatever reason, there is an issue with the import in the EC2 environment. I am thinking that I can create a postgresql dump of the resources that are required and then you can just load them into your postgresql database on EC2. Do you have enough access to your environment to be able to load the postgresql data?

yes this would be the location for tomcat 6 and 7 too.

Hi, our 4.5.0 release will be coming out soon. It has some enhancements for the php sample (jasperserver/samples/php-sample). The new code has been upgraded to support newer php language. The release will not be out for a couple of weeks. However, you can get it straight from the trunk source code. I will do some checking and see if anyone is familiar with the error you are getting

Hi, I would like to ask you about the specific error that you are getting (which can be seen in the <js-install>/installation.log). I can see from your error message posted to your message that it is the "import" operation that is failing. For me, the import operation is also failing. However, the thing that is a little odd is that for me it is failing with CentOS 5.7 but it is *not* failing with CentOS 5.3. And yours is failing with CentOS 6. So, there definitely seems to be something going on with newer versions of centos. The error I'm getting on the import is that the loggingService is not initialized and so the loggingService bean reference is null. So, the import runtime spring initialization fails. buildomatic/conf_source/iePro/applicationContext-report-scheduling.xml]: Cannot resolve reference to bean 'loggingService' while setting bean property 'schedulerContextAsMap' with key [TypedStringValue: value [loggingService], target type [null]]; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'loggingService': org.springframework.beans.factory.FactoryBeanNotInitializedException I am attaching the whole stack trace (which ends up a few pages long actually - but mostly just says the same thing over again). I might be able to create a postgresql db-dump file for you so that you can simply load the data into you database (and skip having to do the import).

I am going to look at this bug. I think that I have reproduced the same issue on a centos install that I have. We have seen issues in the past where the "import" operation (ie adding jasperserver data/resources to the database) has failed when the /etc/hosts is not set up in a standard way on linux instances. The issue can be that "localhost" does not get resolved and then there is a failure - so you might take a look at your hosts file to see if anything looks unusual.

Can you see any specific error in the jasperserver.log file related to this? The location would be (in the case of Tomcat): <tomcat>/webapps/jasperserver/WEB-INF/logs/jasperserver.log

Oh, and I should mention that the instructions for running the js-upgrade-samedb.bat are found in Chapter 10 of the JasperReports Server Install Guide PDF (found in the <js-install>/docs folder)