Hello,

I am upgrading from 8.0.0.7 to 8.2.0.2M and as I am testing reports LOCALLY through App Studio, I am getting an error when changing my reports from running EXL2K to XLSX.

I can run the reports OK on the actual server that the reports will eventually be going through, but locally I am having issues with Java and can't figure it out.

I have an example using the CAR file:

 TABLE FILE CAR
PRINT
CAR MODEL SEATS DEALER_COST RETAIL_COST SALES LENGTH WIDTH HEIGHT WEIGHT WHEELBASE FUEL_CAP BHP RPM MPG ACCEL
BY COUNTRY NOPRINT
ON TABLE PCHOLD FORMAT XLSX
ON TABLE SET HTMLCSS ON
ON TABLE SET STYLE *
TYPE=REPORT,FONT='TIMES NEW ROMAN',SIZE=10,COLOR='BLACK',STYLE=NORMAL,GRID=OFF,$
TYPE=REPORT,COLUMN=P1,WRAP=1.20,$
ENDSTYLE
END
-RUN
-EXIT
 

The error is:
CPJAVA: Error in processing INIT command for Class ibi.jsexcel.JscomExcelZip/ Ensure JSCOM3(JVM) service is running; check -Djava.class.path in edaprint.log

I have tried all kinds of things like changing the order that my PATH is setup to point to Java on my local machine, added JAVA_HOME to the edaenv.cfg file on my local reporting server so it could find it, and a few other things I can't remember off the top of my head.

Any ideas would be appreciated.

Thanks,

Paul

This message has been edited. Last edited by: FP Mod Chuck,

Paul

The edaprint.log in the \ibi\AppStudio82\srv\wfs directory will show why the jscom3 is not starting on your local reporting server. I can't remember if the app studio reporting server uses 32bit or 64bit java but that could be the issue is that even though you have JAVA_HOME set it is not the correct java.

If you open the Reporting Server Console, Workspace, Java Services and double click DEFAULT is the port active?

If it's not, the first thing I'd check is to make sure you're running the latest version of JRE. Compare the version of Java on the server to the one on your local machine and make them the same and restart the server and see what happens.

Thanks Chuck - I absolutely know and understand that jscom3 is not starting on my local server.

Below are the places in the log file that talks about jscom3 (in one place it actually shows it is started). For security purposes I have to mask the first part of my directory structure.

09/12/2018 09:25:07.624 I Configuring PATH for Java JVM for JSCOM3 Listener...
09/12/2018 09:25:07.639 I
09/12/2018 09:25:07.639 E No 64 bit JVM located after search...
09/12/2018 09:25:07.639 E
09/12/2018 09:25:07.639 E JAVA_HOME is "C:\xxxxxxxxx\java\jdk1.8", verify directory contents
09/12/2018 09:25:07.639 E for "C:\xxxxxxxxx\java\jdk1.8\bin\server\jvm.dll"
09/12/2018 09:25:07.639 E or "C:\xxxxxxxxx\java\jdk1.8\bin\client\jvm.dll"

Below it shows that it started:

09/12/2018 09:25:12.530 I FDS started (pid=55064,sid=1)
09/12/2018 09:25:12.702 I JSCOM3 started (pid=55096,jscomid=1)
09/12/2018 09:25:12.702 I Workspace initialization completed

And down a little further:

09/12/2018 09:25:13.280 E Failed to load JVM (module jvm)
09/12/2018 09:25:13.280 I
09/12/2018 09:25:13.280 E JSCOM3 start failed: Java JVM DLL failed to load.
09/12/2018 09:25:13.280 E
09/12/2018 09:25:13.280 E JVM dll is located (and directories added to PATH) by searching ...
09/12/2018 09:25:13.280 E
09/12/2018 09:25:13.280 E Subdirectories indicated by JDK_HOME environment variable value, then...
09/12/2018 09:25:13.280 E Subdirectories indicated by JAVA_HOME environment variable value.
09/12/2018 09:25:13.280 E If variables not set then registry searched for JDK/JRE locations.
09/12/2018 09:25:13.280 E
09/12/2018 09:25:13.280 E Variables can be set at the machine's global property level or
09/12/2018 09:25:13.280 E in the server's EDACONF bin\edaenv.cfg configuration file.
09/12/2018 09:25:13.280 E
09/12/2018 09:25:13.280 E JDK_HOME is not set.
09/12/2018 09:25:13.280 E JAVA_HOME is set to "C:\xxxxxxxxx\java\jdk1.8"
09/12/2018 09:25:13.280 E
09/12/2018 09:25:13.280 E Java JAVA_HOME was set, but no 64 bit JVM found, check variable value.
09/12/2018 09:25:13.280 E
09/12/2018 09:25:13.280 E Also see earlier "Configuring..." section of this log (near top) for further
09/12/2018 09:25:13.280 I processing cmrpaq000002 u=OPSYS\RB\xxxxxxx,r=SRV
09/12/2018 09:25:13.280 E information or errors that may have occurred during the JVM configure phase.
09/12/2018 09:25:13.280 E
09/12/2018 09:25:13.280 E jscom3c: js3crt failed
09/12/2018 09:25:13.311 I FDS listening on tcp :::8122
09/12/2018 09:25:13.327 W request by edapmon to notify JSCOM3 Java service (jscomid=1) failed to start
09/12/2018 09:25:13.327 W JSCOM3 Java service is required to access JDBC based datasources and use WebFOCUS graph reports

I realize it shows me that no 64 bit JVM is found, so I am wondering if my declaration of where the file is needs to be expanded from:
C:\xxxxxxxxx\java\jdk1.8

to
C:\xxxxxxxxx\java\jdk1.8\jre\bin\server

where the jvm.dll file actually is.

Let me try that.

Thanks.

quote:

BabakNYC

Thanks for the reply.

My port is not active on my local machine - probably because it can't find the version of Java. In the section under properties called Version and path it shows Java version not found.

The ports are different by design, but my local port is set to 8123, which I understand it should be.

As I mentioned in my reply to Chuck, I am wondering if I need to add to my PATH exactly where the jvm.dll file is, that being C:\xxxxxxxxx\java\jdk1.8\jre\bin\server

I am going to try that and see if it works.

Thank you.

Paul

Paul

8.0.07 was definately a 32bit java server and based on your log the 8.2 server is 64bit. Insure your java in the path is 64 bit and points to the server directory where the jvm.dll file is located.

That did it - I added the path directly to the jvm.dll and I can run XLSX reports locally now.

Appreciate your help.

I am not sure how to close these discussions so if someone on here knows how, consider it closed - much appreciated.

Have a good day.

Paul

Paul

For future reference if you edit your original post the title of the post can be edited and you can add {SOLVED] or [CLOSED] to that title and re post it.

Ok Chuck thanks.