Home » Polarsys » Capella workbench » installation problem(capella crashes after splash screen, before welcome screen)
installation problem [message #1826122] |
Sun, 19 April 2020 20:16  |
Eclipse User |
|
|
|
I am new to Capella, want to try out the tool for MBSE study.
The tool started but stopped right after the splash screen, as reported in detail below. Any help is appreciated!
(1) Installed jre-8u202-windows-x64.exe on my ThinkPad, running Win10 64-bit.
(2) Created a folder C:\capella140, and installed Capella 1.4.0 for Win 64
in the folder.
(3) In C:\capella140\capella\eclipse, i have double-clicked "eclipse.exe"
(4) Splash screen appeared, and disappeared.
(5) The welcome screen didn't appear, but instead, a small error window appeared
saying "an error occurd. See the log file".
(6) In the log file, a Java runtime Exception is reported saying, "org.polarsys.capella.core.platform.sirius.ui.perspective.id" could not be found in the registry.,
where the top of the stacktrace is at "org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:252)".
note1: the logfile, eclipse.ini etc are attached in the zip file.
note2: Tried jre-8u121-windows-x64.exe also, resulted same problem.
note3: In my pc, I have other JREs and eclipse installation, in 32-bit configuration. So I added -vm option in eclipse.ini to specify the 64-bit JRE explicitly.
|
|
| | | |
Re: installation problem [message #1826195 is a reply to message #1826172] |
Mon, 20 April 2020 20:39   |
Eclipse User |
|
|
|
Thank you Stephane,
I re-installed Capella and it worked fine this time!
The difference I can remind of is that this time I "moved" the directory "capella" to "C:\",
after unzipped the download package in Downloads directory,
whereas in previous trials I moved "eclipse" directory to the hand made directory "C:\capella140".
Not sure if the above is the real cause, maybe I did something else.
Before the re-installation, I tried things related to environment variables (JAVA_HOME, JRE_HOME, PATH, CLASSPATH).
They didn't worked, but one thing to be noted is that setting CLASSPATH changed the name of the
"not found" item in the log file report, so the direct cause could be related to classpath.
Now my problem is solved, and Id like to leave the investigation off here.
Sorry about the incomplete report, and thank you for your support!
-- hiroshi
|
|
| | | | | |
Goto Forum:
Current Time: Sun Aug 31 11:14:30 EDT 2025
Powered by FUDForum. Page generated in 0.06663 seconds
|