Cannot find recent repository (version) on current server...

I could’nt connect to my repository anymore, even though I haven’t changed anything in Servoy. Upon opening Sercoy I got the message above and was asked if I wanted to upgrade/create the repository. The only thing I can remember doing was installing the OS X Security Update 2005-008. Before that I just quit Servoy. Now I’m trying to open Servoy and get this error.
I saw that the dbsrv9 was running - and it also was the correct one (I also have Servoy 2.1 installed, but get the same error):

/Applications/Servoy2.2
/Applications/Servoy2.2/sybase_db/dbsrv9
/private/tmp/.SQLAnywhere/servoy_repository/shmem/shm_00000002
/Applications/Servoy2.2/sybase_db/libdbtasks9_r.dylib
/Applications/Servoy2.2/sybase_db/libdbunic9_r.dylib
/Applications/Servoy2.2/sybase_db/libdbserv9_r.dylib
/usr/lib/dyld
/usr/lib/libSystem.B.dylib

/Applications/Servoy2.2/sybase_db/dblgen9.res
obj=0x02a61860
/private/tmp/.SQLAnywhere/servoy_repository/lock
/Applications/Servoy2.2/sybase_db/sybase_log.txt
/Applications/Servoy2.2/database/servoy_repository.db
/Applications/Servoy2.2/database/user_data.db
/Applications/Servoy2.2/database/example.db
/Applications/Servoy2.2/database/log_data.db
/Applications/Servoy2.2/database/crm.db
/private/tmp/.SQLAnywhere/servoy_repository/tmp/tmp_00000000
/private/tmp/.SQLAnywhere/servoy_repository/tmp/tmp_00000001
/private/tmp/.SQLAnywhere/servoy_repository/tmp/tmp_00000002
/private/tmp/.SQLAnywhere/servoy_repository/tmp/tmp_00000003
/private/tmp/.SQLAnywhere/servoy_repository/tmp/tmp_00000004
/Applications/Servoy2.2/database/example.log
/Applications/Servoy2.2/database/servoy_repository.log
/Applications/Servoy2.2/database/crm.log
/Applications/Servoy2.2/database/log_data.log
/Applications/Servoy2.2/database/user_data.log
->0x0282ff48
/tmp/.SQLAnywhere/servoy_repository/lrm_socke

*:sybaseanywhere
*:sybaseanywhere
localhost:sybaseanywhere->localhost:49239

I then made a copy of the file servoy_repository.db and clicked “yes” to upgrade/create the repository in the opening error dialog. When opening Servoy now, I get the message “Starting Repository” on the bottom for the longest time and when click on open solution, I get an empty list!
Any ideas on that one? I have put in quite a few hours of work since the last backup :-(

Reto

Sounds to me like you connected to your servoy 2.1 databases which asked you to upgrade. Close all copies of Servoy, stop all dbsrv processes and launch servoy again. If it still connects to your 2.1 repository check if there is a servoy.properties file in your home directory, if so remove it.

I am also having the same problem. Jan, the servoy.properties file that you mention, where exactly will I find it?

Thanks

Jan Aykroyd:
I am also having the same problem. Jan, the servoy.properties file that you mention, where exactly will I find it?

Thanks

In your home directory.

If servoy cannot write to the servoy directory (this can happen for example if you quit server and relaunch it before it is done quitting or on multi user systems) it will write the properties file in your home directory and use that at launch. As this appears to be a problem many people have we have changed this behaviour in 2.2.1: in 2.2.1 it will not read the properties file unless you explicitely tell it to do so.

Looked in there, no servoy.properties file. Any other suggestions?

Thanks

Jan

Have you tried searching all files/folders for *.servoy - must be in there somewhere

Graham Greensall
Worxinfo Ltd

Hi Graham

I have a servoy.properties file in the Servoy application folder (and in the other 2 folders containing older versions of Servoy) Have ditched that but problem still persists.

Is that Martin Scorsese?

Hello

My first thought was also that Servoy just connected to the 2.1 repository, but it looked like the dbsrv9 process was really running out of my 2.2 installation (see my quote in the original post, which shows the details of the dbsrv process…).
Well, after reading your replies, I removed the servoy.properties file and now get the error “Could not find repository server: ‘repository_server’” (see attachment).
When I check, there’s no dbsrv process running. In “Application Preferences” the tab “DB Servers” is empty…

Appreciate your frustration as I’ve spent many an hour trying to get to grips with these problems - the good news is that once you’ve got a stable install of Servoy these errors will rarely reappear.

Not sure if you’ve already seen these but there have been a number of threads on repository problems - here’s some that I had bookmarked:

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

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

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

http://forum.servoy.com/viewtopic.php?t … b11220837a

May not have a specific answer to your situations but plenty of great tips.

HTH

Graham Greensall
Worxinfo Ltd

xtsr:
Hello

My first thought was also that Servoy just connected to the 2.1 repository, but it looked like the dbsrv9 process was really running out of my 2.2 installation (see my quote in the original post, which shows the details of the dbsrv process…).
Well, after reading your replies, I removed the servoy.properties file and now get the error “Could not find repository server: ‘repository_server’” (see attachment).
When I check, there’s no dbsrv process running. In “Application Preferences” the tab “DB Servers” is empty…

If your db server tab is empty there is either a completely missing servoy.properties file (did you delete the main one?) or an incorrect one. If you havn’t created any new connections yet simply copy a new version of an new install into your servoy directory to fix. If you have created connections do the same and then recreate your custom connections.

Jan Aykroyd:
Hi Graham

I have a servoy.properties file in the Servoy application folder (and in the other 2 folders containing older versions of Servoy) Have ditched that but problem still persists.

What problem? that you can’t connect or that you don’t see solutions? If you don’t see solutions you developed that solution in a different repository. If you can’t connect make sure that you have a servoy.properties with connections in it.