We shut down our Servoy server this morning to swich repositories (by launcing Developer, go into Preferences and changing the data provider link).
When we restarted the server we discovered we had lost 10 of our licenses, they had become 10 Developer licenses and when user no 11 loaded Servoy he got a message saying there were no more licenses.
We logged into servoy_admin and changed this back to client licenses and everything is now OK.
this is a problem that should be looked at BUT it is very unwise to use the same property file for the server and developer. All kind of things could mess up then. If you want to startup the developer for doing stuff on a server directory: Make a copy of the servoy.properties file, name it for example servoy_developer.properties and then start the developer with an extra system property:
Unfortunately, this is a Windows 2003 server, so I can’t do any of the UNIX stuff to change it myself via ssh and they are not running terminal services.
Stopping Server service, Starting Developer, changing the setting and quitting Developer, starting the Server service is something I can instruct a client to do over the phone. Hacking the preference file is a little more difficult explain.
As far as I know, there is no way of changing the repository connecting via the web interface…
mail them a bat file that they should put in the servoy install dir that does the copy and start of the developer.
But i see that won’t help you with the problem you want to change. Because you really want to change the servoy.properties file. But be warned that this could causing some problems.
But make a case for that the client are converted to developer.
we never fill in an serial for using the developer on a servoy server.
We just sometimes, start developer, (stop servoy server first) for updating, or changes to the db-entries, that’s it. Never had any problems with licenses with that.
we never fill in an serial for using the developer on a servoy server.
We just sometimes, start developer, (stop servoy server first) for updating, or changes to the db-entries, that’s it. Never had any problems with licenses with that.
We finally switched to our new repository this morning…
Stopped Servoy service
Launched Developer
Modified Repository URL
Quit Developer
Restarted Servoy Service
The first 10 x client license in the list in Servoy Admin did switch to Developer license again and the serial check failed.
I can live with this, but it will sure confuse and frustrate some beginners
Somehow Developer or Server make an unwanted modification to the prefs.
If you are not supposed to use the same pref file for Developer and Server, I’d suggest Servoy change the default naming so the pref is only shared if you deliberatly set it up to do so. However, this also means you have to be able to fully edit database servers from the web interface.
I have also noticed that if you change the preferences in Developer, and you have to terminate the Servoy Developer application (like when you can’t escape from an infinte loop and have to force-quit), you loose all the changes you have made to the preferences.
Also, as far as I know, launching Developer is the only way of upgrading Servoy version…
jcompagner:
Please make a test case for the altering of servoy licences that we should just fix.
Hi Jan,
Thanks for looking into this.
Do I just upload my servoy_properties file as a test case?
Also, I noticed that servoy_properties fills up with old unused database_connections over time…
I don’t use Sybase at all, and I still have Sybase connections in the properties file, although you can’t see them in the user interface in Developer or server_admin web pages.
Since Jan is not answering to this post. I, Johan, will do it…
we fixed for 3.5 these stale databsae connections.
If you could make case and you can attach your properties file that is currently correct but after a start with the developer it is wrong, then we can look at it.
