The problem is that I don’t know how to start the Sybase SQL Anywhere instance so that Servoy can access the repository.
I can’t find this information in the documentation. Does anyone know what to do?
BTW, I just want to start the database used as the Servoy repository. I don’t want to install it as a Service - primarily because I don’t want to install Sybase Central.
Ok, I think I got the database instance working. I went inside the sybase_db directory and click on the database engine file (dbeng11.exe). I had then the option of opening a database. See the image below:
Then I started the Servoy Service and set it to Start up “automatically.” Then I started Servoy Server by triggering the servoy_server.bat. I also checked port 8080 for HTTP traffic and port 1099 for RMI. They are both open.
Ok, I resolved the issue. Still, I do not understand the underline reason of the problem.
This is what did:
I noticed that there was a directory named .Servoy into the server user directory. I think that it was taking over port 8080. I think that this was created while I was testing a client application in that machine. I removed this directory
I also uninstall Servoy ‘entirely’ – and I remove ServoyService too
I perform a clear Servoy Application Server installation but this time I did NOT install the server as a service.
Then I got started the database instance as I explained before.
I started the Servoy server and everything seems to be working just fine.
Does anybody have an explanation of what happened here?
Could have this been a conflict between the Servoy Server as a Service and just the Servoy Server?
Could have this been a problem originated by the directory downloaded with the client application a couple of days ago?
If you install Servoy as a Service and the service is started, it means that a Servoy Application Server is started, so you don’t need to start Servoy Server manually.
So, if you had both the service and an manually started Servoy App Server running, it’s quite likely you had port conflicts, unless you changed the port settings yourself.