"No such file or directory error" When using jasper with openerp - jasper-reports

We have developed reports using jasper and all was ok when we developed it.
On my laptop I am able to print the report just fine this is where I ran the server and tested it.
However when I uploaded it to my ubuntu server and users try to access the same report we get an error.
"2
No such file or directory
(<type 'exceptions.OSError'>, OSError(2, 'No such file or directory'), <traceback object
at 0x7f63b8485ab8>) "
Its been two days and we are stuck. Please advice what must be wrong.
I am not sure what is wrong here.
Thank you
Vishal

So the way I solved it was by installing open jdk. As jasper is a java file it needs the compiler and the server did not have this.

Related

"Source file could not be read" error when exporting database

I made a draft of a Wordpress website on localhost using XAMPP. I made a database for it using MySQL. I'm ready to upload to BlueHost. I understand that means I need to save the database as a single .sql or .sql.zip file.
I keep getting the "...\UAywaMh-.sql.part could not be saved, because the source file could not be read" when I try to turn the database into an .sql file that I can upload to BlueHost. BlueHost help says that the problem is not on their end. I've tried it in Firefox and Chrome. Chrome says "couldn't download."
I did leave the "New template" and "Existing template" fields blank. Is that it?
I know the name of the database I created and I was able to find it easily in https://localhost/phpmyadmin/ I don't think I have the wrong one.
How do I fix this so I can get my website live? Thanks!
UPDATE: On GitHub, someone described the same problem and said that patch #17447 fixes it, but I can't find the patch anywhere. https://github.com/phpmyadmin/phpmyadmin/issues/17445
UPDATE: A GitHubber responded! Turns out the answer is to update phpMyAdmin to version 5.20 or later! The first time I did this, I couldn't log in, but the trick is to copy over the config.something file!
Posting this so anyone in the future can find the solution.
The problem ended up being fixed by https://github.com/phpmyadmin/phpmyadmin/issues/17445 which was fixed in phpMyAdmin 5.1.4 and 5.2.0. It seems there was a related problem in PHP https://github.com/php/php-src/issues/8218 that caused download issues with some browsers.
Upgrading to the latest phpMyAdmin release was the solution.

Jasper server error when referencing a custom function

I am using JasperStudio v6.3.1 and I followed the tutorial on how to create a custom Java function that I can use in my report. Everything works fine in Jasper Studio, but when I publish the report to the Jasper Server, then it fails. The report does exist on the Server, but does not run after publishing the latest changes.
"Errors were encountered when compiling report expressions class file: 1. The method CURRENT_MONTH_BEGINNING() is undefined for the type TotalTaskHrsOnly..."
This error is generated because the custom Java functions that I made in Jasper Studio did not get published to the remote Jasper Server. I need help with getting these files onto the Jasper Server, but I'm not sure how to do that within Jasper Studio, Jasper Server, or if I need to log into the remote server, and drop the java files in there somewhere. Can someone please tell me how I can add the custom functionality onto the Jasper Server?
I worked with custom Java functions in Jasperserver reports for quite awhile. Some of the things you will need to ensure:
You import the java class at the top of the Jasper report .jrxml file
The Jar is deployed to the server and is labeled as a resource in the repository. It looks like this is the part you're getting stuck on. If you log into Jasperserver and go to the repository, you can open a folder and upload a new file/resource.
The report references the jar in the repository as a resource
Does this help?

Eclipse save error when trying to open the design view of a synapse config file in WS02 Developer Studio

I'm following the tutorials and samples of the official WSO2 ESB documentation. When I create (or load) a synapse configuration in the WSO2 Developer Studio I'm getting the error as shown below:
Save problems
Save could not be completed.
Reason:
resources\sunErrorHandler.esb_diagram (The system cannot find the path specified)
This error shows up when I want to open anything in the Design view. Even when I'm not trying to save anything.
So far I have tried to add the path specified in the error, but without success. I already found a workaround to be able to save and deploy my ESB configurations. By using "Save as" I'm able to keep the changes I made in the XML files. However the error stills shows up when I open the new version of the file.
Does anyone know a better solution to permanently resolve this error message?
I had this problem as well, running eclipse.exe as administrator fixed it.
Issue remains unresolved for my Eclipse + DevStudio 3.8.0 install on a Windows 10 environment. However since I was experiencing some other issues with the WSO2 ESB I decided to migrate to a Linux (Ubuntu) environment. This seems to work much better, the eclipse does not seem to have this issue on Linux.
Eclipse want to write in C:\Program Files\eclipse\resources. I solve problem by adding full permissions to group users on folder C:\Program Files\eclipse
If this happens in Mac you can provide the required permission to the "/Applications/IntegrationStudio.app/Contents/MacOS/resources" folder.

phpmyadmin blank screen after installing Zend server

I installed LAMP on Ubuntu 12.0.4 LTE. Then I installed phpmyadmin. Everything was good. I used phpadmin to do lots of DB administration....
Then I installed Zend CE server. Now, phpmyadmin throws a blank page. No login screen.
So, I reinstalled my VPS in the same sequence again. No luck. Same behavior.
This time, I installed Apache, Mysql, PHP and Zend server in that order. Then I installed phpmyadmin....Unfortunately, still blank page on phpmyadmin.
Any help?...Thanks in advance.
First, for all those that posted their suggestions to my above issue, thanks!.
Of course, I had to dig deeper into forums and threads to find the specific root cause and solution for this issue.....and after spending few hours...finally, I resolved it!. Thanks to the following bug discussion link on php.net.
https://bugs.php.net/bug.php?id=25876
I tired many suggested fixes there but they didn't help. The suggestion that finally fixed the problem was pasted below ( so that let the credit go to the right owner):
[2011-03-03 12:18 UTC] comments at htmlcompressor dot com
If you are gettin the following error:
"Fatal error: session_start(): Failed to initialize storage module: files (path: ) in...."
Make sure that you have setup the session save path in your php.ini:
session.save_path = "/tmp"
which seems to be disabled by default.
I swear using Open Source software is tough!. I have spent whole day on this issue alone. My goal was to build some software and I have yet to get to it!!.

JasperReports no longer run after move to new server

I have been working with JasperReports for about 4 years now. We have moved our application to a new server, and suddenly none of the reports run any more. All they give is the following cryptic error:
Error compiling report java source files : /usr/code/myapp/applicationguide_xml_1344313005668_686357.java
That's just not enough of an error to do anything about.
All of the JAR files are exactly the same.
I'm using the same version of the Sun JRE.
Google yields nothing helpful.
Has anyone see this before? I see references to the error going all the way back to 2009, but nothing understandable as a solution.
UPDATE:
Here is the code that is failing with the absentee message:
JasperDesign jasperDesign = JRXmlLoader.load(reportFile);
JasperReport jasperReport = JasperCompileManager.compileReport(jasperDesign);
It's the second line.
JasperCompileManager of course requires access to javac. I did not have jdk-devel installed on my new RedHat machine. After I did:
yum install java-1.6.0-openjdk-devel
then I no longer received this error.
In order to figure this out, needed a stacktrace since the Jasper error was so cryptic. I installed the Apache Common Lang jar, and printed out my stack trace in a catch block like so:
System.out.println(ExceptionUtils.getStackTrace(ex));
That gave me the underlying error message plain as day.