ianywhere_utils - Can't create Sybase database

Classic Servoy
1

Hello,

i’ve problems with creating a new Sybase Database, using the Servoy example solution “ianywhere_utils”, shipped with Servoy 3.5.6.

When i try to create a database, i get the following error:

"SQL exception: com.sybase.jdbc3.jdbc.SybSQLException: SQL Anywhere Error -82; Unable to start specfied database: unable to start database "C:\Users\LXS\Desktop\Servoy4\database\test.db" SQL Anywhere Error -82: Unable to start specified database:
unable to start database"C:\Users\LXS\Desktop\Servoy4\database\test.db"

I’ve already tried it on Vista 32bit Business and Win XP Prof, both with Servoy 4.0 and Servoy 3.5.6
It’s always the same error message :-/

In the database directory isn’t a file created, too.

The same issue is described (on the bottom) in the following thread:

http://forum.servoy.com/viewtopic.php?t=10425

Can anyone help me?

Thanks a lot!

Alexander Stefan

2

I’m not sure what causes your error, but note that in Servoy 4.0 you can create new sybase databases without the “ianywhere_utils”-solution. Just rightclick a database under the “Database Servers”-node in the solution explorer and click “Create Sybase Database”.

3

Hello Joan,

thanks for your help!
I’ve just tried to create a Sybase database over the right-click.

I get the same error message on this way :(
This time i used Servoy 4 with Windows XP Prof SP2.

Does this feature work on your machine?

Thanks,
Alexander Stefan

create_sybase_database.JPG
create_sybase_database.JPG1412×747 126 KB

4

LXS:
Does this feature work on your machine?

I just tried it, also with Win XP Pro SP2, and it works correct, the db is created and started. Are you sure that the file doesn’t exist already?

5

yes, i’m sure.
When i clicked on the OK Button (to create the database) i watched the database folder. The test.db file is created and after a few seconds it is deleted, then the error message pops up.

Alexander Stefan

6

Hmmm, I haven’t seen this before, do you have the same behavior in a fresh installation of Servoy?

7

I am having problems with this too.
Creating the Sybase database went fine, also adding
tables works like a charm IF…you do not restart Developer.
After a restart the database can no longer be opened: databaseicon with red cross.

Servoy 4.0.0 + XP_SP3

8

Ron:
like a charm IF…you do not restart Developer.

This is probably a different problem. Check the “sybase.config” file in the “application_server/sybase_db”-folder of your servoy installation. Make sure that there is a line like “database/<db_name>.db” for your new database, so that it is started automatically.

9

Hi Joas,

You’re right this is another problem, at first I thought the
database creation was fake.
The sybase config file is always updated perfectly.
Restarting Developer (only) gives the described access-error.
Rebooting the XP box AND restarting Developer however solves the problem. Is this expected behavior?.

Now I have your attention Joas, can you have a look at this post plse:

http://forum.servoy.com/viewtopic.php?t=10857

I did’nt want to post it as an bug/issue since I’m not sure if it is possible
to open (whatever) release from Checkout.

Thanks in advance,

Ron

10

Hi Ron,

You also have to restart Sybase engine after creating the database from Servoy 4.0 option. So both developer and database engine have to be restarted.

About: SQL exception: com.sybase.jdbc3.jdbc.SybSQLException: SQL Anywhere Error -82; Unable to start specfied database - We had this error when sybase script directory is not in system path variable. It cannot find the scripts to create the database.

11

lvostinar:
Hi Ron,

About: SQL exception: com.sybase.jdbc3.jdbc.SybSQLException: SQL Anywhere Error -82; Unable to start specfied database - We had this error when sybase script directory is not in system path variable. It cannot find the scripts to create the database.

THANKS Laurian!

That was the problem! The script directory wasn’t in the system path variable. I’ve added it, restarted Servoy4 and the Sybase Database was created without any problems!

I’m wondering why this feature works on other machines without adding the script folder to the path variable…

Greetings,
Alexander Stefan