MarcViste
asked on
Sharepoint Error After Live Migration
I followed the instructions in this guide:
http://www.codeproject.com/Articles/663663/Live-Migration-of-SharePoint-2010-to-SharePoint-20?msg=4739463#xx4739463xx
Due to not being able to use the interal copy function I just copied the DB manually via command line.
I am able to get the WSS-Content DB with all of my sites into the 2013 installation. But when I try to access the sites I get the following error:
Error
An unexpected error has occurred.
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: a1446b9c-8c9d-2092-0000-09 8df2499809
Date and Time: 1/17/2014 2:31:03 PM
Go back to site Go back to site
in the log this corresponds to:
01/17/2014 14:31:03.00 w3wp.exe (0x0634) 0x14C4 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (GET:http://sharepointtest2:80/sites/hcms) a1446b9c-8c9d-2092-0000-09 8df2499809
01/17/2014 14:31:03.00 w3wp.exe (0x0634) 0x14C4 SharePoint Foundation Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=, ClaimsCount=0 a1446b9c-8c9d-2092-0000-09 8df2499809
01/17/2014 14:31:03.01 w3wp.exe (0x0634) 0x14C4 Web Content Management Publishing adjr0 Medium CatalogConfig.ReadFromProp ertyBag; Catalog configurations don't exist for site collection http://sharepointtest2/sites/hcms. a1446b9c-8c9d-2092-0000-09 8df2499809
01/17/2014 14:31:03.01 w3wp.exe (0x0634) 0x14C4 Web Content Management Publishing ai23f Medium SiteServicesAddins.ReadFro mPropertyB ag: Site services addins don't exist for site collection http://sharepointtest2/sites/hcms. a1446b9c-8c9d-2092-0000-09 8df2499809
01/17/2014 14:31:03.01 w3wp.exe (0x0634) 0x14C4 SharePoint Foundation General 8kh7 High List does not exist. The page you selected contains a list that does not exist. It may have been deleted by another user. a1446b9c-8c9d-2092-0000-09 8df2499809
But the sites are listed in the content database "Current Number of sites" number on the central administration page. It lists there are 4 sites....
Any ideas?
http://www.codeproject.com/Articles/663663/Live-Migration-of-SharePoint-2010-to-SharePoint-20?msg=4739463#xx4739463xx
Due to not being able to use the interal copy function I just copied the DB manually via command line.
I am able to get the WSS-Content DB with all of my sites into the 2013 installation. But when I try to access the sites I get the following error:
Error
An unexpected error has occurred.
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: a1446b9c-8c9d-2092-0000-09
Date and Time: 1/17/2014 2:31:03 PM
Go back to site Go back to site
in the log this corresponds to:
01/17/2014 14:31:03.00 w3wp.exe (0x0634) 0x14C4 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (GET:http://sharepointtest2:80/sites/hcms) a1446b9c-8c9d-2092-0000-09
01/17/2014 14:31:03.00 w3wp.exe (0x0634) 0x14C4 SharePoint Foundation Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=, ClaimsCount=0 a1446b9c-8c9d-2092-0000-09
01/17/2014 14:31:03.01 w3wp.exe (0x0634) 0x14C4 Web Content Management Publishing adjr0 Medium CatalogConfig.ReadFromProp
01/17/2014 14:31:03.01 w3wp.exe (0x0634) 0x14C4 Web Content Management Publishing ai23f Medium SiteServicesAddins.ReadFro
01/17/2014 14:31:03.01 w3wp.exe (0x0634) 0x14C4 SharePoint Foundation General 8kh7 High List does not exist. The page you selected contains a list that does not exist. It may have been deleted by another user. a1446b9c-8c9d-2092-0000-09
But the sites are listed in the content database "Current Number of sites" number on the central administration page. It lists there are 4 sites....
Any ideas?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Central Admin - System Settings - Farm Solutions will show you solutions installed at the farm level.
To check for claims in 2010, pull up a SharePoint Management Shell window on one of your farm servers and run the following:
Get-SPWebApplication | Select Name, URL, UseClaimsAuthentication
If any of them are "False", you need to migrate them to Claims, then migrate to 2013. Or (not best practice) you can manually create a Classic Auth web app in 2013 and migrate as is to that web app.
http://technet.microsoft.com/en-us/library/gg251985.aspx
To check for claims in 2010, pull up a SharePoint Management Shell window on one of your farm servers and run the following:
Get-SPWebApplication | Select Name, URL, UseClaimsAuthentication
If any of them are "False", you need to migrate them to Claims, then migrate to 2013. Or (not best practice) you can manually create a Classic Auth web app in 2013 and migrate as is to that web app.
http://technet.microsoft.com/en-us/library/gg251985.aspx
ASKER
If both are supposed to be widnows auth why do I need to change to claims first?
Because Microsoft said to :)
Claims auth is what the default is in 2013 and will likely be the only choice in the next version. Classic auth is being deprecated. It's better to get on claims now. Yes both use Windows auth but the actual token is formatted differently between claims and classic.
The switch isn't that bad. It sounds scarier than what it is.
Claims auth is what the default is in 2013 and will likely be the only choice in the next version. Classic auth is being deprecated. It's better to get on claims now. Yes both use Windows auth but the actual token is formatted differently between claims and classic.
The switch isn't that bad. It sounds scarier than what it is.
ASKER
What does changing to claims auth on a live system before copying the DB do on the user level? Would people possibly have log in issues or anything of that nature?
Yes you can have login issues. You need to run a test prior to make sure you get the process down. In my experience the number one issue is forgetting to set the cache accounts properly. They must be in the "claims" format. Do a Google search.
Doing a SharePoint upgrade/migration is a big task. It's not something that should be taken lightly. It will take some research, planning, and testing.
Doing a SharePoint upgrade/migration is a big task. It's not something that should be taken lightly. It will take some research, planning, and testing.
ASKER
I've noticed. Although the link in my question makes it seem oh so super easy. And I am finding it's the opposite.
You have any links to guides you prefer for the migration?
You have any links to guides you prefer for the migration?
ASKER