Upgrade to Umbraco 7.7.0+ returns error Invalid object name 'umbracoUser2UserGroup'.
Attempting to upgrade Umbraco from version 7.2.1. Upgrading the database separately from the code:
Create empty ASP.NET Web Application (.NET Framework)
Add NuGet package for version 7.3.0
Add connection string.
Run the upgrade.
Rinse and repeat the above steps for additional upgrades. However, unable to get past version 7.7.0 - the highest I could get was version 7.6.13 because of error Invalid object name 'umbracoUser2UserGroup' in the UmbracoTraceLog.
Because I'm using a clean web site for my database upgrade, I am confident the issue is not due to third-party add-ons or the like.
I have a solution which I will post in a reply. Adding this forum post in the hopes it will help others, as I see multiple similar unresolved tickets.
Ran my web site. I was able to get past the failing authentication and proceed with the upgrade.
Old BackOfficeSignInManager:
//check the password for the user, this will allow a developer to auto-link
//an account if they have specified an IBackOfficeUserPasswordChecker
if (await UserManager.CheckPasswordAsync(user, password))
New BackOfficeSignInManager:
//check the password for the user, this will allow a developer to auto-link
//an account if they have specified an IBackOfficeUserPasswordChecker
if (true)
Hi Dave - I did try an Incognito window, did not help. I should have mentioned I tried a number of the other solutions posted to the forum but none of them worked for me.
I suspect there might be several paths to ending up with this error as the authentication code is somewhat convoluted. For example there are code comments suggesting some of the new user group tables might have actually existed (at least with the same name) at one time in much older Umbraco versions.
I haven't tried it but in my case, it might have been possible to authenticate in version 7.6.13, update to the 7.7.0 Nuget packages, and then rerun the site before the original 7.6.13 auth cookie expired, because the issue is just in getting past the initial authentication so that the upgrade code can kick in.
I found another successful work-around which is more straight-forward than my initial solution:
Created empty ASP.NET Web Application (.NET Framework)
Added NuGet package for UmbracoCms version 7.6.13
Added connection string
minRequiredPasswordLength="8" useLegacyEncoding="true" (for my application originally Umbraco 7.2.1)
Created local domain in my hosts file
Logged in to the back office using my local domain, ran the upgrade to version 7.6.13. Did not log out.
Upgraded my empty ASP.NET Web Application to Umbraco 7.7.0, accepted all .config overwrites when prompted.
Refreshed the /umbraco link at my local domain.
Was prompted to login again, but this time did not encounter the Invalid object name 'umbracoUser2UserGroup' error.
Ran the 7.7.0 migration to successful completion.
I would recommend this as the first attempt to resolve the Invalid object name 'umbracoUser2UserGroup' issue, and resort to my code solution only as a last resort.
I recommend performing Umbraco database upgrades separately from code upgrades by using this empty ASP.NET Web Application (.NET Framework) approach for the database anytime it's necessary to jump many Umbraco versions. This recommendation comes from extensive experience upgrading various Umbraco applications from as far back as version 6.x. Once the database is upgraded successfully, then the code can be upgraded "all at once" directly to the latest version.
Upgrade to Umbraco 7.7.0+ returns error Invalid object name 'umbracoUser2UserGroup'.
Attempting to upgrade Umbraco from version 7.2.1. Upgrading the database separately from the code:
Rinse and repeat the above steps for additional upgrades. However, unable to get past version 7.7.0 - the highest I could get was version 7.6.13 because of error Invalid object name 'umbracoUser2UserGroup' in the UmbracoTraceLog.
Because I'm using a clean web site for my database upgrade, I am confident the issue is not due to third-party add-ons or the like.
I have a solution which I will post in a reply. Adding this forum post in the hopes it will help others, as I see multiple similar unresolved tickets.
My solution was to do the following (see a later reply for an easier alternative to try first):
Source code: NV Interactive github
Old BackOfficeSignInManager:
New BackOfficeSignInManager:
Hi Kevin,
I saw this last week where it was solved by starting the upgrade in a incognito window.
It can be that the authentication cookie is causing this.
Can you try that ?
Dave
Hi Dave - I did try an Incognito window, did not help. I should have mentioned I tried a number of the other solutions posted to the forum but none of them worked for me.
I suspect there might be several paths to ending up with this error as the authentication code is somewhat convoluted. For example there are code comments suggesting some of the new user group tables might have actually existed (at least with the same name) at one time in much older Umbraco versions.
I haven't tried it but in my case, it might have been possible to authenticate in version 7.6.13, update to the 7.7.0 Nuget packages, and then rerun the site before the original 7.6.13 auth cookie expired, because the issue is just in getting past the initial authentication so that the upgrade code can kick in.
I found another successful work-around which is more straight-forward than my initial solution:
I would recommend this as the first attempt to resolve the Invalid object name 'umbracoUser2UserGroup' issue, and resort to my code solution only as a last resort.
I recommend performing Umbraco database upgrades separately from code upgrades by using this empty ASP.NET Web Application (.NET Framework) approach for the database anytime it's necessary to jump many Umbraco versions. This recommendation comes from extensive experience upgrading various Umbraco applications from as far back as version 6.x. Once the database is upgraded successfully, then the code can be upgraded "all at once" directly to the latest version.
is working on a reply...