Killing Server Config distroys database
I've made an upgrade from RC2 to RC4 and 1.0.2. on my server (with three clients in seperate rooms). When importing the data, all worked fine and the message "successful" appeared in the process window. Shortly after that the erver config kill was executed. Restarting the server config showed an almost clear server config screen all settings or even menus are totally gone. The only way out of the dilemma is to complete uninstall and reinstall the TV server.
I played around with the settings of the backup and found a setting where the kill is not executed. Savely executing the config then stores everything. It seems that the backup expects a single seat installtion and doesn't work properly when some parts of the client are not found although it is selected that also MediaPortal client shall be resotred. But in general the kill server config should not be executed at all to avoid problems.
I've made an upgrade from RC2 to RC4 and 1.0.2. on my server (with three clients in seperate rooms). When importing the data, all worked fine and the message "successful" appeared in the process window. Shortly after that the erver config kill was executed. Restarting the server config showed an almost clear server config screen all settings or even menus are totally gone. The only way out of the dilemma is to complete uninstall and reinstall the TV server.
I played around with the settings of the backup and found a setting where the kill is not executed. Savely executing the config then stores everything. It seems that the backup expects a single seat installtion and doesn't work properly when some parts of the client are not found although it is selected that also MediaPortal client shall be resotred. But in general the kill server config should not be executed at all to avoid problems.