We have a problem that in whenever the Servoy server is rebooted the license is replaced by an invalid license for one user. Subsequently all
clients are denied access unitl an administator can use the web administration tool to re-apply the actual multi-client license.
Furthermore, once the multi-client license is re-entered then the developer, running on the same machine as the server, reports an invalid license.
I see now that both the server and the developer are pulling the license information from the servoy.properties file. I have edited this file by
hand when the server was stopped in order to insure that the file is saved with the correct data. Still, the next time that I reboot the server the multi-client license is lost.
We are running Servoy 2.2.2.2.-Build 334.
Has anyone else seen these problems?
Does anyone know the solution to the license conflict between the Developer and the Server?
There is indeed a difference between the Developer license and the Server license.
When you enter a Server license in Developer then it will tell you it’s a bad code and vice-versa.
In other words you can’t use both licenses on the same machine at the same time.
The best way is to set up a dedicated server for Servoy Server and another machine for your development.
Now you can connect your Developer to the server database (repository/data) but that has it’s drawbacks as well.
The best way is to use a local repository and database and develop on it. Then export your solution (release) and import it into the server.
Btw for an occasional edit in the solution on the server you can launch Developer on the server and do your thing. Just don’t set the Developer license.
Also after the edit you have to relaunch Servoy Server to make it aware of the changes.
We put two instances of Servoy on the same machine. The Developer is always used in instance A and the server from instance B. Each instance has it’s own preference file so the problem is resolved.
idoctor:
We put two instances of Servoy on the same machine. The Developer is always used in instance A and the server from instance B. Each instance has it’s own preference file so the problem is resolved.
John McCann
I believe you will find that the conflict in the use of TCP ports is still not resolved. As a result I expect you will find that problem of port unavailable
when trying to send email.
idoctor:
We put two instances of Servoy on the same machine. The Developer is always used in instance A and the server from instance B. Each instance has it’s own preference file so the problem is resolved.
John McCann
I believe you will find that the conflict in the use of TCP ports is still not resolved. As a result I expect you will find that problem of port unavailable when trying to send email.
You can set up different ports for different instances of Servoy easy enough (server guide).
As stated above the issue of losing client licenses on restart is because you also have your developer license in the mix (if the developer license shows up first in the license page of the admin app then you will always lose the validation of following client licenses on restart). I think this is more of a bug than one of those things you shouldn’t do but that is the way it is for now.
So either use developer without a license key or use a different instance of developer with the ports changed or not with a license key. I guess if you want to send email from both you’ll need to change the ports
It’s easy to issue a server restart from the admin app when you’re done doing whatever in developer. I would however set up your developer instance of servoy with a different repository than your production instance. Then do an export/import of your solution. Keeps things cleaner.