E: Can't connect to the repository server specified in ...

Providence1:
What actually launches ‘dbsrv9’ on Mac OS X?

If you mean on your development machine, simply launching Servoy Developer starts the dbserv9 process. This is what’s meant by “embedded database” … the Servoy Developer application is also a database server.

If you mean, OTOH, on a computer that is being used as a Servoy Application Server, it is best to start SAS as a service rather than merely launching Servoy Developer as an application.

See the Servoy Developer User Guide, chapters 14 and 15.

kazar

Now, what would prevent or why would ‘dbsrv9’ fail to load when launching Servoy Developer on OS X?

Well, I found that it failed to load for me because I did not have all my databases inside the sybase_db folder.

I had Activity Monitor open while I was launching Servoy and I could watch it try to open as a process and then close itself having found a problem.

I tied it down to missing db’s purely becasue the problem exhibited itself just following my creating a new db but saving it in the wrong place !

Cheers
Harry

With the problem I was having before (mentioned earlier in thread), dbsrv9 was failing to load. I reinstalled Servoy, then the problem went away. When I added back my repository db, it failed again. So, I am starting over. My assumption is that the repository was corrupt.

By the way, it appears that when I add a new repository db and log back into the database folder in a failed solution, it “works” again, in the sense that dbsrv9 loads, the application shows up as expected, etc. Of course, MY stuff is gone. So, it looks like there may be no need to reinstall the applications, but rather just revert to last backup of the repository database and log.

Jim

Now, what would prevent or why would ‘dbsrv9’ fail to load when launching Servoy Developer on OS X?

Jim Schliestett:
My assumption is that the repository was corrupt.

That would highly surprise me. I think something else is wrong. The solution to non launching sybase is very simple: read the sybase logfile in the sybase_db directory, it will tell you what is going on.