Error "init is not defined"

I'm running BIRT Report viewer on Tomcat 5.5 on linux server. Only Report frame is displayed without data. 
 
Error: init is not defined 
Source file: <a class='bbc_url' href='http://www.e-novice.eu/birt/frameset?__report=dnevnatecajnica.rptdesign&sample=my+parameter'>http://www.e-novice.eu/birt/frameset?__report=dnevnatecajnica.rptdesign&sample=my+parameter</a> 
Vrstica: 1 
 
Boris

Find more posts tagged with

Comments

Virgil Dodson

Hi Boris,

It seems by clicking on the link that maybe the problem is gone. In case someone else has the same problem, did you change anything to make it work correctly?

fsiddiqi

I'm running into this problem as well. 
 
Receive a javascript error init() not defined in firefox. 
 
Here's a link: 
<a class='bbc_url' href='http://pentaho.docsq.com:8080/birt-viewer/frameset?__report=SalesInvoice.rptdesign'>http://pentaho.docsq.com:8080/birt-viewer/frameset?__report=SalesInvoice.rptdesign</a> 
 
Any help would be appreciated. 
 
Thanks 
 
Faisal

fsiddiqi

Interestingly, this error occurs only when using the /frameset operation URL. Works correctly with /run operation..

Thanks

srswart

I am having this same issue. The odd thing is my reports were running fine for the past year and suddenly they started having this problem yesterday. On most of the reports nothing has changed. If anyone has recovered from this problem your solution would be appreciated.

dader

Hi,

I have a problem with a report designed with BIRT. This report worked perfectly but since today when I launch it I just have the birt-viewer page without any results, with no Java error.

The webdevelopper plugin for Firefox give me this error : "init is not defined".

Can anyone help me to fix this bug ?

Thanks

Virgil Dodson

Hi dader,

I merged your post with another thread where others are having the same issue. Maybe this way we can get more eyes on the problem.

What version of BIRT are you using? ... and is the problem with just one report? Have you tried modifying/saving the rptdesign to see if it was corrupted... or redeploying the BIRT Viewer, restarting server, etc?

dader

Thanks for your answer.

I tried to modify and save the rptdesign, but no changes about the "init" error.
We are using BIRT 2.5.0 on a Debian Server with Tomcat 5.5.

We've tried to redeploy a new report and we had the same error.

Those two reports are using an Oracle Database connection, the others (who are working) are connected to a MySQL and a SQL Server database.

dader

The bug is fixed by restarting the Tomcat server.

Thanks for your help

moh

Hi all, 
 
I've got the same problem while loading /frameset : 
 
Erreur*: init is not defined 
Fichier Source*: <a class='bbc_url' href='http://localhost:8080/birt-viewer/frameset?__report=test.rptdesign&sample=my+parameter'>http://localhost:8080/birt-viewer/frameset?__report=test.rptdesign&sample=my+parameter</a> 
Ligne*: 1 
 
I've moved webapps/birt to webapps/birt-viewer and restarted tomcat 
and the problem is still happening 
 
I've just deployed birt.war into tomcat5 webapps folder, and added mysql jdbc connector. 
 
my configuration is : 
 
Tomcat Version : Apache Tomcat/5.5.23 
JVM Version : 1.5.0_18-b02 
JVM Vendor : Sun Microsystems Inc. 
OS Name : Linux Centos 5.3 
OS Version : 2.6.18-128.1.10.el5.centos.plusPAE 
OS Architecture : i386 
 
Birt version : 2.5 
 
mysql jdbc driver is in : ./birt-viewer/WEB-INF/platform/plugins/org.eclipse.birt.report.data.oda.jdbc_2.5.0.v20090605/drivers 
 
any help will be apreciated.

dregan

I figured this out, it turns out that birt crashed trying to initialize CUPS on my server (probably because I have set it up) and it never finished rendering the FramesetFragment.jsp file which contains the init() declaration. I fixed this by disabling server side printing (in the WEB-INF/web.xml file set BIRT_VIEWER_PRINT_SERVERSIDE to OFF).

Parido Par

I had the same problem on BIRT viewer 3.7.
I was using a file for storing the connection parameters, so I didn't have to create new each time.
This procedure was creating the below 2 lines in the xml
<property name="OdaConnProfileName">CONNECTION_NAME</property>
<property name="OdaConnProfileStorePath">PATH_OF_THE_FILE_WITH_THE_CONNECTIONS</property>
When I deleted these everything worked fine.