Servoy 3 Runtime only works on machine which runtimed it

Classic Servoy
1

Hi all

We’re trying to build a runtime and have an odd problem where the only machine that can run the runtimes subsequent to building is the machine with the copy of servoy developer that developed the runtime. It doesn’t work when copied to any other machine. I don’t think it has anything to do with dbsrv9 or dbeng9 as it still works perfectly after a system restart without any servoy / sybase stuff started first… Copy it to any other mac or pc and we get “Can’t connect to the database server”. Although I gather the chmod tricks are no longer necessary to solve this problem, we have still been doing it (chmod +x dbeng9 in the runtime_db folder) If we do it on a machine we’ve copied the runtime to, it still doesn’t work. On the machine it DOES work, we can copy it anywhere to other users etc. and no problems.

The development machine is a 1.4Ghz G4 Mac mini with Servoy 3.1 (404). it subsequently does not run on a Sony Vaio desktop, an intel Macbook Pro or a G5 Powermac.

Any help would be appreciated

Bevil

2

update:

Even moving the runtime to an external firewire disk works fine on the development machine, move that disk to my intel Macbook Pro and it won’t have it. “Can’t connect to database”

Is there a home folder invisible preference file created on the development machine?

Perplexing

3

Thunder:
update:

Even moving the runtime to an external firewire disk works fine on the development machine, move that disk to my intel Macbook Pro and it won’t have it. “Can’t connect to database”

Is there a home folder invisible preference file created on the development machine?

Perplexing

What happens if you rename the folder on the MacMini?
If it stops working on that machine too, you probably have created the db using an absolute path.