SharePoint migration – Resolving issue – The [] web application is configured with claims authentication mode however the content database you are trying to attach is intended to be used against a windows classic authentication mode. There is an inconsistency between the authentication mode of target web application and the source web application

Hi All,

Greetings for the day 🙂 LIFE IS BEAUTIFUL 🙂

SharePoint migration continues. Today new issue and resolution 🙂

Background :

  • SharePoint migration going on. We are in process of migration of SharePoint 2010 web application to SharePoint 2013 web application
  • We are using content database attach method
  • On SharePoint 2013 environment we have created new web application, removed its default content database
  • Databases are copied to SharePoint 2013 database server for mounting to our new SharePoint 2013 web application
  • Next step is to test the respective content databases against our new SharePoint 2013 web application
  • So we started executing Test-SPContentDatabse for our each database
  • In Test-SPContentDatabase logs we found the below Configuration category entry

Category : Configuration
Error : False
UpgradeBlocking : False
Message : The [webapplicationname] web application is configured with claims authentication mode however the content database you are trying to attach is intended to be used against a windows
classic authentication mode.
Remedy : There is an inconsistency between the authentication mode of target web application and the source web application. Ensure that the authentication mode setting in upgraded web
application is the same as what you had in previous SharePoint 2010 web application. Refer to the link “http://go.microsoft.com/fwlink/?LinkId=236865” for more information.

  • Test-SPContentDatabase checks if users within the UserInfo table are claim enabled for claim based web application and vice versa
  • But if we notice details, this is not error or blocking upgrade so we are good to proceed without any action
  • We can ignore this message/record and proceed if we want

But then lets explore this in more detail :

Cause for this record / entry :

  • We have started migration from MOSS to SharePoint 2010 with content database attach process
  • MOSS and SharePoint 2010 by default uses classic mode authentication
  • With successful migration from MOSS to SharePoint 2010, we started migration to SharePoint 2013
  • MOSS web application is using classic mode and we migrated as it is SharePoint 2010 so users were not migrated to claims since default authentication is classic mode for SharePoint 2010
  • It will not automatically convert the users in the content database from classic to claims when attaching a content database from classic web application to claims-enabled web application

Our migration approach / Solution for this :

  • We could migrate the valid users from classic to claims-enabled by using MigrateUsers() of web application or using Convert-SPWebApplication CMDLET as
 $webApp = Get-SPWebApplication <"My Webapplication URL">
 $webApp.MigrateUsers($true)

OR

Convert-SPWebApplication -Identity <"My Webapplication URL"> -To Claims  -RetainPermissions

  • Once above CMDLETS executed successfully warning from Test-SPContentDatabase will also go

Thanks for reading 🙂 If its worth at least reading once, kindly please like and share 🙂 SHARING IS CARING 🙂 

 Enjoy the beautiful life 🙂 Have a FUN 🙂 HAVE A SAFE LIFE 🙂 TAKE CARE ðŸ™‚

Prasham Sabadra

LIFE IS VERY BEAUTIFUL :) ENJOY THE WHOLE JOURNEY :) Founder of Knowledge Junction and live-beautiful-life.com, Author, Learner, Passionate Techie, avid reader. Certified Professional Workshop Facilitator / Public Speaker. Scrum Foundation Professional certificated. Motivational, Behavioral , Technical speaker. Speaks in various events including SharePoint Saturdays, Boot camps, Collages / Schools, local chapter. Can reach me for Microsoft 365, Azure, DevOps, SharePoint, Teams, Power Platform, JavaScript.

You may also like...

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: