database shuts down when I import solution

[wgrayson]

I have a solution that I've been managing and updating for a few years. With my latest update, I export from developer and go to Servoy Server to import it the same way I do about once a week. But now, upon import, every time it errors out saying java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused: connect.

My Windows Service that starts my database shuts down. I go in and restart the service, try the import again, and get the same error and the database service shuts down again.

I've tried completely removing the solution and importing it clean with the same result. I've re-exported it from Develop with the same result.

My Developer machine and server machine are two different machines. My developer machine is running Postgres database with Servoy Developer 5.2.9. My server machine has Sybase at the database. Some of my lasest changes in this import include adding about 10 new fields in my database.

Any thoughts as to what would cause my database to continue shutting down every time on import?

thanks!

[ROCLASI]

Hi,

Do you see anything in the Postgres logs ? Or in any of the system logs?

[wes.s.grayson]

I don't see anything in the Postgres logs. All the servoy server logs just reference connection refused, which is a result of the problem (the database shutting down during import).

[ROCLASI]

What about the system/event logs?
Also can you log into PostgreSQL with a DBA tool and create new records manually? In any of the databases ?

[wes.s.grayson]

From the server's event logs, here's the error message I get when I try to manually create a new column in my sybase database:

SQLANYs_ServoyDatabase: *** ERROR *** Assertion failed: 200608 (11.0.1.2331)
Freeing page not in arena

[ROCLASI]

AH! Now I read that your Dev machine uses Pg but the server uses Sybase.
So yes, I should have asked what's in the Sybase logs.

Anyway, it seems your database is in a weird state. Perhaps you need to rebuild your database by unloading it and then loading it into a new database file.
But I am not a Sybase expert so perhaps someone else can give you better advice.

Hope this helps.

[wes.s.grayson]

thanks! I went back in and unloaded and loaded into a new file and now all is well. Much appreciated.