Page 1 of 1

Failed to initialize Simantics database

Posted: July 2nd, 2015, 11:36 am
by systect

when I try to open Simantics, after choosing the workspace, the following error message pops up and simantics is not started:

Failed to initialize Simantics database.
cause: Failed to create Simantics database.
cause: Could not connect to C:\Users\MyName\Documents\workspaces\sysdyn\db

db-client.log shows no info (though there are some exceptions from former sessions, i.e. org.simantics.db.exception.DatabaseException: No objects 200709 4101 or the following AssertionError org.simantics.db.impl.graph.ReadGraphImpl.getPossibleObject(

2015-07-02 10:43:33,437 260 [ main] INFO ics.db.common.utils.LogManager - ProCoreServer exe: C:\Program Files\Sysdyn\plugins\org.simantics.db.server_1.4.1.r031272\win32.x86_64\ProCoreServer.exe
2015-07-02 10:43:33,438 261 [ main] INFO ics.db.common.utils.LogManager - ProCoreServer folder: C:\Users\MyName\Documents\workspaces\sysdyn\db
2015-07-02 10:43:33,439 262 [ main] INFO ics.db.common.utils.LogManager - ProCore version information:
ProCoreServer version=1.4 protocol=24.1 folder=C:\Program Files\Sysdyn\plugins\org.simantics.db.server_1.4.1.r031272\win32.x86_64
svn id=$Id: r31270 2015-05-08 08:07:00Z $

.metadata/.log does not report any details neither:

!SESSION 2015-07-02 10:43:15.709 -----------------------------------------------
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE
Framework arguments: -fixerrors
Command-line arguments: -os win32 -ws win32 -arch x86_64 -fixerrors -data @noDefault

!ENTRY org.simantics 1 0 2015-07-02 10:43:33.453
!MESSAGE Creating database at C:\Users\MyName\Documents\workspaces\sysdyn\db

!ENTRY org.simantics.workbench 4 0 2015-07-02 10:43:36.448
!MESSAGE Failed to initialize Simantics database.

Thanks for your assistance.

Re: Failed to initialize Simantics database

Posted: July 2nd, 2015, 12:56 pm
by jkauttio
It looks like your database might be corrupted, and even though recovery is technically possible it is not straightforward and unfortunately the easiest solution is to start over with a fresh workspace.

Both the tool and the Simantics platform are under constant development, and sometimes bugs which can result in database corruption can slip through into release versions. If you are able to reliably reproduce the issue we would very much like to hear about it, but currently the best practice is to simply save the model frequently into a file (so work is not lost even when this happens).

For future reference, there are some known issues with the database server that can cause it to stay alive after the tool itself has been closed which can lead into similar errors. If the tool can not be started and a process called ProCoreServer.exe can be found running on the background, terminating it manually can sometimes solve the issue. It is important that the process is idle when it is terminated though, since the database can also be corrupted if the process happens to be inside a read or write transaction when it is terminated.

P.S. thanks for the detailed issue report, we will forward this to the author of the database server when he returns from summer vacation