Recently, I have been using the new and vastly improved installer where you just point the new install at the old database and it upgrades in place - this worked flawlessly to get 7.2 up to 7.6.4 on a test server; now I'm trying to do the same on the live server to the newest version.
Update: I have just tested going to 7.6.4 and getting a similar error, so I must be doing something differently to how I remembered doing the old test upgrade!
What I am doing is:
Clone old database
Create entirely new 7.7.1 website
Add existing version number to new web.config
Change connection string to clone of old database
Browse to website
I get the login screen for authorizing the upgrade
LOGIN FAILS ON MISSING DB objects
Once succeeded, I would merge views / custom code etc
AHA! Forgot to use the membership provider settings from the old web.config. Did that and installed in seconds. Must have had serious brain problems yesterday,
So, the process is:
Create an IIS site for new install
Extract new version to that
Update web.config to have:
Connection string pointing at old DB (ideally duplicate!)
Old version number in umbracoConfigurationStatus
Old UsersMembershipProvider key
Start site, browse to site, go
Merge all old Views
Merge all additional custom config / scripts / etc.
Hi Gijs, funnily enough I just tried my own technique on another site, this one a really old 4.11 version, and got the same result as you.
I did actually get it working, but tbh I was messing around so much I'm not sure what it was! The last thing I tried was a UserProvider section from a 7.2 install, and it started working around then.
Sorry I can't be any more help, wish I unambiguously knew what had worked as I have other sites to upgrade. Will post back if I can identify a consistent working upgrade process! The new process is 1000% better than it used to be, but I still can't find clear docs / blog posts on how to do it beginning to end, including getting the users working to authorize the upgrade in the first place.
Good luck! Post an answer if you find anything yourself.
P.S. Try using the new web.config provider settings for type, but make sure all the attributes from the old key are put in, including useLegacyEncoding="true" if it's an old site, or if it's already set to true.
Upgrade 7.6.4 to 7.7.1
I am trying to upgrade a 7.2.0 site to 7.7.1.
Recently, I have been using the new and vastly improved installer where you just point the new install at the old database and it upgrades in place - this worked flawlessly to get 7.2 up to 7.6.4 on a test server; now I'm trying to do the same on the live server to the newest version.
I cannot login to authorize the upgrade:
I presume this is because of the big changes to the security system, but how am I supposed to upgrade now?
The umbracoConfigurationStatus is set to 7.2.0 which I understood should upgrade the DB automatically?
Update: I have just tested going to 7.6.4 and getting a similar error, so I must be doing something differently to how I remembered doing the old test upgrade!
What I am doing is:
Basically following these instructions: https://cultiv.nl/blog/an-umbraco-database-upgrade-tip-from-the-trenches/
AHA! Forgot to use the membership provider settings from the old web.config. Did that and installed in seconds. Must have had serious brain problems yesterday,
So, the process is:
Hey Rob,
I have the same problem, but using the old usermembershipprovider key didn't work. It gives a YSOD:
This is the one I used:
Do you have any thoughts on how to proceed forwards?
Hi Gijs, funnily enough I just tried my own technique on another site, this one a really old 4.11 version, and got the same result as you.
I did actually get it working, but tbh I was messing around so much I'm not sure what it was! The last thing I tried was a UserProvider section from a 7.2 install, and it started working around then.
Sorry I can't be any more help, wish I unambiguously knew what had worked as I have other sites to upgrade. Will post back if I can identify a consistent working upgrade process! The new process is 1000% better than it used to be, but I still can't find clear docs / blog posts on how to do it beginning to end, including getting the users working to authorize the upgrade in the first place.
Good luck! Post an answer if you find anything yourself.
P.S. Try using the new web.config provider settings for type, but make sure all the attributes from the old key are put in, including useLegacyEncoding="true" if it's an old site, or if it's already set to true.
is working on a reply...