This first part has been rewritten from original for sake of non-confusion.

I have created my first WebApplication in my Sharepoint 2013 Farm. I now want to move some of my SP 2010 Content Databases from a WebApplication over to this new test farm. 

1. I  have verified that my 2010 WebApplication is defined as Claims Based Authentication using Sharepoint 2010 Central Adminstration Authentication Providers.  

2. I did a Backup of the Content Database and then Restored it on my new server that has SP 2013 using SQL Server Management Studio backup and restore. 

3. I run the PowerShell command on my SP 2013 server of Test-SPContentDatabase -Name WSS_OLD_ContentDB -WebApplication http:NewWebApplicationURL.com

I get the following error message when I run this:

When I go ahead and run the Mount-SPContentDatabase cmdlet it finishes but I cannot get into my SiteCollection. 

Is this a bug or am I not doing this right?

Hi Steve,

How did you set up the new web application, was it through PowerShell? It seems from the error that the content database is correctly associated for Claims Authentication, but the new web application is set for Classic Authentication.

With PowerShell, when using New-SPWebApplication, if you provide the AuthenticationMethod parameter, the web application will be set up for Classic Authentication. If you want to set it up for Claims Authentication and support Windows Integrated Authentication, omit the AuthenticationMethod parameter and include the AuthenticationProvider parameter instead. For example (extra line breaks added for readability):

$ap = NewSPAuthenticationProvider UseWindowsIntegratedAuthentication

New-SPWebApplication 
-Name "New Web Application" 
-URL "http://NewWebApplicationURL.com" 
-Port 80 
-ApplicationPool "NewWebAppPool" 
-ApplicationPoolAccount (Get-SPManagedAccount "DOMAIN\AppPoolServiceAccount") 
AuthenticationProvider $ap 

Actually, I created my new WebApplication through the Central Adminstration on SP 2013. 

Application Management ==> Manage Web Applications ==> New

If going through the "Create New Web Application" screen there is not a parameter anymore for Claims versus Classic  

Sorry if I confused everyone here. I am putting in the original message when using the Test-SPContentDatabase not the one I got when I went back and tried to do a convert on my SP 2010 content database to Claims Based Authentication (since it already was) and moved it again over to the SP 2013 server.

This is the original message:

To add to the confusion, once I tried the second method when I ran the Mount_SPContentDatabase command I get CurrentSiteCount : 0 -  so that didn't work either. 

i see this message just now.

my content database is upgraded from SharePoint 2007 to SharePoint 2010. And i am trying to upgrade it to 2013 now.

the content database contains two site collections, one is from 2007, and the other is created in 2010. I didn't remember what i did when i upgraded the 2007 content database to 2010 (it was really long time ago). But the SharePoint 2010 web application is claim based(i can see in CA in authentication provider for the web application).

I see this message no matter the web application in 2013 is claim or classic. I guess i must have missed something when uprading from 2007 to 2010.

I have the same problem.  2010 shows claims in the UI and I do the test-spcontentdatabase to 2013 and it gives the same error.  When I look in both web applications via the UI 2010 and 2013 it shows the apps to be claims????

I thought you may be on to something, GuYuming. I'm getting this same Test-SPContentDatabase message after following the conversion instructions at http://technet.microsoft.com/en-us/library/gg251985.aspx. My content databases contain site collections originally created in 2007. I know there is something lingering in them that didn't go quite right in the conversion to 2010 because I can't create Designer workflows in the converted site collections. Site collections created in 2010 have no issues for creating Designer workflows in the same content databases.

So, you're logic made sense and I put it to the test: I created a new content database and put a site collection in it with 2010. Exported that to my 2013 farm. Just to be on the safe side, I ran Test-SPContentDatabase on the new database and got the "...web application is configured with claims..." message. Attached (Mount-SPContentDatabase) and converted it to claims (Convert-SPWebApplication -- as I had done with the previous content databases), and then ran Test-SPContentDatabase: This time, no message.

At least in my case, it really does appear to have something to do with content coming from 2007. Now, if only someone can have some idea of WHY this is so we can fix it.

I run the test-spcontentdatabase again, the same result. But this time, i see that the message has UpgradeBlocking value set to False, this means i can just keep upgrading. There are also many other LegacyUIDetected messages with UpgradeBlocking value False too in the result.

So, i run Mount-spcontentdatabase and finished successfully, and i can open the upgraded sites. Please let me know if you find anything wrong when you review the upgraded content.