Error opening Sybase Central

[Teddo]

Hi Mike,

I had a lot of troubles with ASA8 java too. Did they install Internet
Explorer 6.xx? I de-installed it and re-installed it and then it worked
like a charm. If they have IE 6 as well, try reinstalling it.

Best wishes for 2003,

Ted

[Mike Marston]

Hi,
Just installed ASA 8.01 and it works great. But...when I start Sybase
Central on a client machine I get the following error message.

"The Java2 runtime was initialized, but there was a problem loading the main
class. Sybase Central could not be started."

This has happened on 2 seperate customer installations. Can anybody tell me
what causes this and how to get around it? Both systems are Windows 2K.

Mike

[Mike Marston]

They do not have IE 6! ANy other ideas?

Thanks,
Mike

"Teddo" <tg@[REMOVETHIS]quadrant.nl> wrote in message
news:$8BMQaNs...@forums.sybase.com...

[Chris Irie]

Hi Mike,

The message you quoted ( "The Java2 runtime was initialized, but there was a
problem loading the main class. Sybase Central could not be started") usually
indicates a problem related to the "sybasecentral.jar" file. There are 2 likely
scenarios:

a) The "sybasecentral.jar" file could be missing or damaged, or
b) A .JAR file which "sybasecentral.jar" depends on is missing

Here's how to figure out what's going on:

STEP 1. Confirm that the "sybasecentral.jar" file is present.

In a canonical ASA 8.0.1 installation, the .JAR file is in "C:\Program
Files\Sybase\Shared\Sybase Central 4.1". The
"scjview.exe" file which launches Sybase Central should also be in this
directory. The size of the
"sybasecentral.jar" file that shipped with the GA build of ASA 8.0.1 was 607,212
bytes long (the actual size
may differ by up to a couple of hundred bytes if you have applied an EBF).

If "sybasecentral.jar" or "scjview.exe" are missing, then you should reinstall
ASA.

STEP 2. If the "sybasecentral.jar" file is present, check that the other JAR
files it needs are present and in the right location.

Sybase Central 4.1.x requires the following JAR files:

SCEditor13.jar
jsyblib13.jar
jh.jar
helpmanager11.jar
jcchart400k.jar

Sybase Central expects to find the "jcchart400k.jar" file in the same directory
as the "scjview.exe" file. Here's
where the other files come from:

(shared)\java\SCEditor13.jar
(shared)\java\jsyblib13.jar
(shared)\java\helpmanager11.jar
(shared)\sun\JavaHelp-1_1\jh.jar

where "(shared)" is the location of the directory which contains components
which are shared between
multiple Sybase applications. This directory is read from the Windows Registry
from
"HKLM\SOFTWARE\Sybase\Sybase Central\4.1\Shared Location". Use REGEDIT to read
that registry
string. In a canonical installation, its value is "C:\Program
Files\Sybase\Shared". Make sure that this value is
correct for your machine (i.e. that the folder really exists, and that the files
listed above really do exist in the
locations indicated.) If the Registry string value is wrong, update it and try
launching Sybase Central again.

STEP 3. When all else fails, run "scjview -batch". This will create a file
called "sybasecentral.bat". Open the file with your favorite text editor, and
look for "-classpath". It will be followed by a series of JAR file names,
separated by semicolons. Confirm that each of these file names is valid. Also
check that there are no duplicates. If you find invalid file names or
duplicates, you'll have to forward that information to Sybase Tech Support for
further diagnosis. If the only thing wrong are the file paths, you can change
the paths in the batch file. Running the batch file will then launch Sybase
Central, given that your command processor (e.g. CMD or 4NT) can handle the
length of the command.

Caveats: The "-batch" option for SCJVIEW is undocumented, and is subject to
change without prior notification. The list of files required to run Sybase
Central are specific to Sybase Central version 4.1.1 and are subject to change.

-- Chris Irie
iAnywhere Solutions