Preview Issue with 4.2.2

Hello out there -- i have recently installed the All-in-one 4.2.2 package on a client's Windows7 machine and i am getting the error below when previewing a report. The same package works fine on other machines. Any ideas?
 
HTTP ERROR: 500
Problem accessing /viewer/frameset. Reason: 
 PWC6033: Error in Javac compilation for JSP
 
PWC6199: Generated servlet error:
The type java.io.ObjectInputStream cannot be resolved. It is indirectly referenced from required .class files

Find more posts tagged with

Comments

lenburt

I have been able to narrow this problem down to any report which has a report parameter. Even a simple 'Hello World' template which works fine, throws this error once a report parm is added to it. Does anyone have an idea of what might be going on?

shamo

If running on internet explorer, change to either chrome or firefox. I encountered same sometime with reports with parameters.

lenburt

I am using Chrome, but thanks for the suggestion.

SailRCG

Looks to me like it could be a Java version issue on your client's machine. I'd start there.

lenburt

Yes, i agree...we are trying different JREs now. One question about that. Can some one explain how the BIRT developer uses these:
 
1) the JRE in JAVA_HOME at the time Eclipse starts
2) The first JRE bin in the Windows path when Eclipse starts
3) The JRE specified in the Eclipse/Windows/Preferences/Java/Installed JREs
 
It does get confusing.

SailRCG

Len,
 
Lets start with #3; I believe the Eclipse preferences can be selected at compile time. If memory serves me, you might even have some
 kind of drop down to select from within the IDE?
 
regarding #2; If you're referring to the System or Environment variables classpath; I believe the default is to "walk the classpath"
 until your java program hits the first class variable it is expecting. Order matters in your System or environment
 variables.
 
finally #1; I think this is the "default" Java location for your Eclipse installation. You are able to control this in the eclipse.ini
 file. For example use: -vm C:/Java/jdk1.7.0_09_x64/jre/bin/server/jvm.dll to use java version 7
 
Hope this helps, if not... I know IBM and ORACLE both have much better and more comprehensive info than I can manage off the top of my head.

lenburt

Ok - good info. We actually resolved the problem by pointing to the 1.7 79 JRE. Hopefully this thread will help others in the future.