Hello, yesterday i have try to upgrade my enterprise Server ( Database Server ) from 1.4.2 to 1.4.3 and the update failed.
I see after the failed upgrade that the SolidCP installer was not more installed at the server so i make first a backup of the existing Database and try to reinstall the SolidCP installation with the newest Version.
The Setup run normaly, it tells me the database exist, so i drop it and create a new one.
When the Setup was done, i restore the backup but i was not able to login with the serveradmin password.
So i try to reset it but when i do that the SolidCP app crash.
Can anyone help me to get my solidCP running ?
This is a realy important problem now, i want make a internal Presentation of SolidCP for future use in my company.
Thanks
Christian.
Hello,
Do you also have a backup of the enterprise web.config? as it contains a crypto key that is used to encrypt passwords (such as serveradmin passes) to the database, if it doesn't match then the serveradmin pass doesn't work.
You can also optionally check the installer config file and make the enterprise values match the current (new) enterprise web.config, it should then be able to reset the password by chosing "settings" --> at the end it will ask to reset serveradmin pass.
Regards,
Marco
Hello Marco, thansk for the fast answer. No i dont have any backup of the webconfig file. I am sorry that i dont have a backup. At the moment it was only a evaluation i stallation and i dont have a backup of it.
No problem,
Then just open up the Enterprise web.config, then go to the installer directory and find the .config of it, match up the Enterprise values there (cypher key, connection string, etc).
You then open up the installer, select the installed Enterprise module, Click settings, it will ask to reset the serveradmin password, type in your new password and it should be all working.
I got burned by this, unfortunately I lost all my data and has to start from scratch with a new DB. Fortunately this server is for testing and not for production yet, so basically I only had a couple of test user accounts in there so it was not a big deal.
I have this running on an AWS machine and update to 1.4.2 to 1.4.3 always fails, regardless of how many times I launch a new instance. So I just gave up and removed the thing (thinking I could restore the DB) since this was taking too much of my time.
