SQL Anywhere SQL central not working after edition upgrade to advanced

[rizwan_javed2]

We recently upgraded edition for our SQL Anywhere database from workgroup to advanced. after this upgrade the SQL central have stopped working. When we try to open it. it fails and generates error file. Error file is attached. Please help. 

hs_err_pid2476_0.log.txt

error_file_07302025.txt

[jack_schueler]

It would really help to know which version you were using and what version you upgraded to.

The trace file seems to have a wonky command line. Are you running scjview.exe or a batch file that may have been created with an earlier version.

Try this command:

java -cp "C:\Program Files\SQL Anywhere 17\java\sqlcentral1700.jar;C:\Program Files\SQL Anywhere 17\java\jsyblib1700.jar;C:\Program Files\SQL Anywhere 17\java\SCEditor1700.jar" -Dsun.java2d.noddraw=true -Dsun.java2d.d3d=false -Dsybase.native.executable="C:\Program Files\SQL Anywhere 17\Bin64\scjview.exe" -ea com.sybase.central.viewer.SybaseCentral -installdir="C:\Program Files\SQL Anywhere 17\bin64" -Xmx4096m

Does that launch SQL Central correctly? The SQL Anywhere Java-based tools are meant to be run with the JRE included with SQL Anywhere. From your dump file, it looks like an Oracle JVM is getting in the way.

[rizwan_javed2]

I tried this command and still got the same issue. Attaching the error. There is no path for any other Java in the environment. output of the path is below.  Version of the SQL anywhere is 17.0.11.7908

Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\SQL Anywhere 17\bin64;C:\Program Files\SQL Anywhere 17\bin32;E:\QcSoftware\Lib;E:\QcSoftware\Bin;C:\gnu\bin;C:\Program Files\SQL Anywhere 17\java\;C:\Program Files\SQL Anywhere 17\Bin64\jre180\bin;C:\Users\a-rjaved\AppData\Local\Microsoft\WindowsApps;

[rizwan_javed2]

source version was : 17.0.11.7059 and the update that was installed is : 17.0.11.7908

[rizwan_javed2]

ran the command got the same error. attached the error log. Also if it helps sharing you the environment path to show no other Java set in the environment.

[rizwan_javed2]

Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\SQL Anywhere 17\bin64;C:\Program Files\SQL Anywhere 17\bin32;E:\QcSoftware\Lib;E:\QcSoftware\Bin;C:\gnu\bin;C:\Program Files\SQL Anywhere 17\java\;C:\Program Files\SQL Anywhere 17\Bin64\jre180\bin;C:\Users\a-rjaved\AppData\Local\Microsoft\WindowsApps;

[rizwan_javed2]

One very interesting discovery. If i use the java from different JRE. SQL central loads just fine. Does that mean the Java delivered with the SQLanywhere is corrupt ?

C:\Program Files\Java\jre1.8.0_212>cd bin

C:\Program Files\Java\jre1.8.0_212\bin>java -cp "C:\Program Files\SQL Anywhere 17\java\sqlcentral1700.jar;C:\Program Files\SQL Anywhere 17\java\jsyblib1700.jar;C:\Program Files\SQL Anywhere 17\java\SCEditor1700.jar" -Dsun.java2d.noddraw=true -Dsun.java2d.d3d=false -Dsybase.native.executable="C:\Program Files\SQL Anywhere 17\Bin64\scjview.exe" -ea com.sybase.central.viewer.SybaseCentral -installdir="C:\Program Files\SQL Anywhere 17\bin64" -Xmx4096m

BTW, When I do java -version on the SQL anywhere native java. that also throws the same error message. 

[jack_schueler]

Re: java -version

That this fails is very odd.

>which java
java is an external : C:\sa17011.7059\bin64\jre180\bin\java.exe

>java -version
java version "1.8.0_301"
Java(TM) SE Runtime Environment (build 8.1.078)
SAP Java Server VM (build 8.1.078 10.0.2+000, Jul 19 2021 17:45:12 - 81_REL - optU - windows amd64 - 6 - bas2:328676 (mixed mode))

Is it possible that the wrong DLLs are being picked up from other folders?

Try something like (using your installation path)...

cd C:\sa17011.7059\bin64\jre180\bin
java -version

[rizwan_javed2 · Accepted solution]

We were able to resolve the issue. The java packaged with the SQL anywhere software was corrupt. Just running the Java-version was throwing these exceptions. We downloaded the same version of the JVM and replaced it in the relevant location under SQL anywhere files. that resolved the issue. Thank you for all the help.