rayfan

Sherman, The setting should work for the general community. The driver was announced earlier this year http://community.ingres.com/forum/comp-databases-ingres/10909-info-ingres-announcement-ingres-jdbc-driver-available-throughmaven.html, which contains links to the repository and a wiki article.

Hi, Yes I am building under Windows. Thanks for the answer.

I checked out my svn source tree to 16040 which included a change to the pom.xml and that has resolved the compilation errors.

Hi, I've just checked out the jasperserver source from svn trunk onto a windows machine and following the build community edition source build guide. I have edited and am using the settings.xml that is a part of the svn code. I'm hitting a compilation error in the jasperserver-jar-war [iNFO] Compiling 209 source files to G:\Projects\Jaspersoft\jasperserver\trunk\jasperserver-war-jar\target\classes[iNFO] ------------------------------------------------------------------------[ERROR] BUILD FAILURE[iNFO] ------------------------------------------------------------------------[iNFO] Compilation failureG:\Projects\Jaspersoft\jasperserver\trunk\jasperserver-war-jar\src\main\java\com\jaspersoft\jasperserver\war\OlapPrint.java:[260,46] cannot find symbolsymbol : method getDefaultHandler()location: class org.apache.fop.apps.FopG:\Projects\Jaspersoft\jasperserver\trunk\jasperserver-war-jar\src\main\java\com\jaspersoft\jasperserver\war\OlapPrint.java:[260,46] cannot find symbolsymbol : method getDefaultHandler()location: class org.apache.fop.apps.Fop This is after I added a dependency into the pom file. <dependency> <groupid>org.apache.xmlgraphics</groupid> <artifactid>fop</artifactid> <version>0.95</version></dependency> I don't seem to be able to resolve the symbols. Any suggestions appreciated. Thanks.

I think that I've seen this before. If you used a copy command it may have missed the hidden .folder.xml files in each ressource directory. You can try to export to zip file; copy the zip to the target machine and use the import from zip option (--input-zip=) or ensure that all of the contents in the exported folders, including hidden files, are copied.

Hi, Take a look at this post http://jasperforge.org/plugins/espforum/view.php?group_id=112&forumid=102&topicid=30144. It mentions that the sample was written for PHP 4.1 and there are instructions in the post to get the sample working with PHP 5.2. I have used the sample with Apache 2.2.4 and PHP 5.2.6. HTH

I've not tried to install on tomcat 6 but your log is suggesting that the variable java.io.tmp can't be resolved. In tomcat 5 this was set in catalina.sh to $CATALINA_TMPDIR as a defined start-up command line option. Can you check the options that are used to start tomcat? Maybe take a look at the /etc/init.d/tomcat file or the catalina.sh file.

It looks like your original installation created the empty schema but didn't manage to import the sample meta data into the repository. You need to identify why this import failed before attempting to load the data again. The js-import.sh script is located in the apps/jasperserver/scripts directory (at least on my instance it is). There is a config/js.jdbc.properties file in which the database connection details are specified. Execute the js-import.sh script for example, ./js-import.sh --input-dir ./js-catalog It would probably be easier to try and reinstall first. Code:Usage: ./js-import.sh [OPTIONS]Options: --help Print this help. --input-dir Input folder. --input-zip Input zip file. --prepend-path String to prepend to a URI path for all imported resources. --update Specifies that existing repository resources should be updated by catalog resources.

This post would have proved useful to me, if only it was a few days earlier :) I hadn't gotten around to posting my findings. I did find that I need the pear Net_DIME package to be able to export reports in various formats.

I just downloaded the japerserver-3.0-bin.zip and it is included in the archive in the directory jasperserver-3.0-bin/scripts/. You should have a copy of the scripts directory included with your version of Jasperintelligence, although I'm not familiar with it. It is important that the lib and conf directories under scripts are up-to-date with the application as I have had problems when there has been a mismatch. If you are migrating from one version to a similar version on the same hardware and operating system platform you might consider a metadata repository backup and restore. I'm sure it's possible but I've only ever done it with Ingres.

Hi Dmitry, There have been a number of bugs tracked on the MySQL site which feature the mysqld service not starting on Vista. Can you check to see if there are any messages in the event log? The screen shots seem to indicate that.