locked
SharePoint Up-Gradation from 2010 to 2013 RRS feed

  • Question

  • Hi,

    I am going to perform SharePoint up-gradation first time from 2010 to 2013. I have gone through some procedures on msdn for up-gradation but I am confused from where to start.

    Actually, I have a lot of custom solutions deployed on 2010. Also there are multiple sites and Project Server 2010.

    I need expert opinions for successful up gradation.

    Regards,

    Mehar

    Friday, April 11, 2014 12:51 PM

All replies

  • Hi Mehar,

    Here are the some of below article which guides to perform upgradation.

    Upgradation from SharePoint 2010 to SharePoint 2013 (Step by Step):

    http://blogs.msdn.com/b/alimaz/archive/2012/07/17/upgrading-from-sharepoint-2010-to-sharepoint-2013-step-by-step.aspx

    SharePoint 2013 Upgrade Process: http://www.microsoft.com/en-in/download/details.aspx?id=30371              

    Upgrade worksheet for SharePoint 2013: http://www.microsoft.com/en-us/download/details.aspx?id=30370

    Regards,

    Senthil

    Friday, April 11, 2014 1:14 PM
  • On top of this, I'd suggest mentioning what you're confused about. We can perhaps provide more direct assistance that way

    Steven Andrews
    SharePoint Business Analyst: LiveNation Entertainment
    Blog: baron72.wordpress.com
    Twitter: Follow @backpackerd00d
    My Wiki Articles: CodePlex Corner Series
    Please remember to mark your question as "answered" if this solves (or helps) your problem.

    Friday, April 11, 2014 1:22 PM
    Answerer
  • Hi Steven / Senthil,

    How to handle the custom solutions deployed at 2010. Do I need to first deploy all these solutions on 2013 before up-gradation start ?

    Regards,

    Mehar

    Friday, April 11, 2014 1:32 PM
  • @Mehar,

    While you are doing the upgrade analysis you can plan for the custom solutions that will run in SharePoint 2013. Below technet article explains indetail.

    http://technet.microsoft.com/en-us/library/cc263203%28v=office.15%29.aspx14

    Once you done the analysis, based on your plan you can deploy the custom solutions to 14 hive or 15 hive or to both hives using compatibility level option.

    Read here about compatibility level

    http://blogs.technet.com/b/mspfe/archive/2013/02/04/planning-deployment-of-farm-solutions-for-sharepoint-2013.aspx

    http://social.technet.microsoft.com/Forums/sharepoint/en-US/21a9cad1-a8db-448f-9f12-75d10da402cf/migrating-custom-solutions-from-sharepoint-2010-to-sharepoint-2013?forum=sharepointadmin

    Once you are done with customizations later you can mount databases to upgrade them.


    My Blog- http://www.sharepoint-journey.com|
    If a post answers your question, please click Mark As Answer on that post and Vote as Helpful

    Friday, April 11, 2014 1:54 PM
  • Hi Mehar,

    Before upgrading the content databases, you can deploy all solution.

    Sequence order:

    1. Inventory about your SP 2010 farm.
    2. Prepare SP 2013 farm.
    3. Copy databases from old server to new server.
    4. Upgrade service application.
    5. Create and confgure web application-
    6. Reapply customization- Install necessary customization for your environment:solution packages,custom site definitions,style sheets,web parts,features,solutions,assemblies,web.config changes,form templates and so on.
    7. Verify with Test-SP Content Database cmdlet in windows powershell to verify that the new environment has all of the componnets you need before you upgrade any databases.
    8. Upgrade the content databases.

    I hope this helps you.

    Regards,

    Senthil

    Friday, April 11, 2014 2:02 PM
  • Hi Senthil,

    How to proceed with Project Server 2010 up-gradation along with database. As there are three database's of Project Server. Are there some specific steps for Project Server up-gradation as well ?

    Regards,

    Mehar

    Saturday, April 12, 2014 3:06 PM
  • >>Are there some specific steps for Project Server up-gradation as well ?

    Pl check the project server upgrade process below

    http://technet.microsoft.com/en-us/library/gg502590%28v=office.15%29.aspx

    http://technet.microsoft.com/en-us/library/ee662496%28v=office.15%29.aspx


    My Blog- http://www.sharepoint-journey.com|
    If a post answers your question, please click Mark As Answer on that post and Vote as Helpful

    Saturday, April 12, 2014 10:25 PM
  • For Project server, check the below link for step by step method with screen shot.

    http://epmsource.com/2013/05/02/migrating-ps-2010-to-ps-2013-walkthrough/

    some consideration before migration for project server.

    https://www.youtube.com/watch?v=1JI3yY70A54


    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

    Sunday, April 13, 2014 4:38 AM
  • Hi,

    I have started up-gradation to SharePoint 2013, Test-SPContentDatabase command gives me a list of missing features and setup files.

    I have deployed all the solutions on SP2013 which were visible on SP2010 Solutions Management page.

    Following are the software that are installed on my SP2013 machine:

    1 - SharePoint 2013

    2- Project Server 2013

    3- TFS 2010

    Log file is

    https://drive.google.com/file/d/0B9-qOqDYFR56TDJXQllTSkkyMXc/edit?usp=sharing

    Also log is showing some features that are already deployed on SP2013.

    Any resolution to these hidden features ?

    Regards,

    Mehar


    Tuesday, April 15, 2014 6:56 AM
  • Any one who can help in these issues ?

    Category        : MissingSetupFile
    Error           : True
    UpgradeBlocking : False
    Message         : File [Features\ReportServer\ReportViewer.dwp] is referenced [] times in the database 
                      [WSS_Content_94af0a10e6964c2ebcad4bc689af7b7], but is not 
                      installed on the current farm. Please install any 
                      feature/solution which contains this file.
    Remedy          : One or more setup files are referenced in the database 
                      [WSS_Content_94af0a10e6964c2ebcad4bc689af7b7], but are not 
                      installed on the current farm. Please install any feature or 
                      solution which contains these files.
    Locations       : 
    
    Category        : MissingSetupFile
    Error           : True
    UpgradeBlocking : False
    Message         : File [Features\VAL3102_TestCaseSteps_TestCaseFeature\TestCase
                      s\TestCases.webpart] is referenced [1] times in the database 
                      [WSS_Content_94af0a10e6964c2ebcad4bc689af7b7], but is not 
                      installed on the current farm. Please install any 
                      feature/solution which contains this file.
    Remedy          : One or more setup files are referenced in the database 
                      [WSS_Content_94af0a10e6964c2ebcad4bc689af7b7], but are not 
                      installed on the current farm. Please install any feature or 
                      solution which contains these files.
    Locations       : 
    
    Category        : MissingSetupFile
    Error           : True
    UpgradeBlocking : False
    Message         : File [SiteTemplates\PWA\dwp\OWCViewPart.webpart] is 
                      referenced [1] times in the database 
                      [WSS_Content_94af0a10e6964c2ebcad4bc689af7b7], but is not 
                      installed on the current farm. Please install any 
                      feature/solution which contains this file.
    Remedy          : One or more setup files are referenced in the database 
                      [WSS_Content_94af0a10e6964c2ebcad4bc689af7b7], but are not 
                      installed on the current farm. Please install any feature or 
                      solution which contains these files.
    Locations       : 
    
    Category        : MissingSetupFile
    Error           : True
    UpgradeBlocking : False
    Message         : File [SiteTemplates\PWA\OWCView.aspx] is referenced [1] 
                      times in the database 
                      [WSS_Content_94af0a10e6964c2ebcad4bc689af7b7], but is not 
                      installed on the current farm. Please install any 
                      feature/solution which contains this file.
    Remedy          : One or more setup files are referenced in the database 
                      [WSS_Content_94af0a10e6964c2ebcad4bc689af7b7], but are not 
                      installed on the current farm. Please install any feature or 
                      solution which contains these files.
    Locations       : 
    
    Category        : MissingWebPart
    Error           : True
    UpgradeBlocking : False
    Message         : WebPart class [ae8a06e7-f5f2-fab2-667f-35b33ef3bf50] (class 
                      [VAL3102_TestCaseSteps.BrandRedirect.BrandRedirect] from 
                      assembly [VAL3102_TestCaseSteps, Version=1.0.0.0, 
                      Culture=neutral, PublicKeyToken=ae4e2cdf4db439bf]) is 
                      referenced [9] times in the database 
                      [WSS_Content_94af0a10e6964c2ebcad4bc689af7b7], but is not 
                      installed on the current farm. Please install any 
                      feature/solution which contains this web part.
    Remedy          : One or more web parts are referenced in the database 
                      [WSS_Content_94af0a10e6964c2ebcad4bc689af7b7], but are not 
                      installed on the current farm. Please install any feature or 
                      solution which contains these web parts.
    Locations       : 
    
    Category        : MissingWebPart
    Error           : True
    UpgradeBlocking : False
    Message         : WebPart class [94b5bae7-436c-dcc2-5869-d491181c283b] is 
                      referenced [1] times in the database 
                      [WSS_Content_94af0a10e6964c2ebcad4bc689af7b7], but is not 
                      installed on the current farm. Please install any 
                      feature/solution which contains this web part.
    Remedy          : One or more web parts are referenced in the database 
                      [WSS_Content_94af0a10e6964c2ebcad4bc689af7b7], but are not 
                      installed on the current farm. Please install any feature or 
                      solution which contains these web parts.
    Locations       : 
    
    Category        : Configuration
    Error           : False
    UpgradeBlocking : False
    Message         : The [SharePoint - 33955] 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.
    Locations       : 
    

    Regards,

    Mehar


    Wednesday, April 16, 2014 12:17 PM
  • that's tell us that you have missing webpart and template in your farm. two things you can do it.

    1) install & deploy the Webpart and template to target farm

    2) try to remove these refrences if you are not going to use them. to remove you can use one of these Codeplex tools.

    SharePoint Feature Administration and Clean Up Tool

    SharePoint Feature Administration Tool | Remove Missing Features


    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

    Wednesday, April 16, 2014 1:29 PM
  • Hi,

    Can start with MOUNT database ?  while Test-ContentDatabase still showing some erros with BlogUpgrade false ?

    I tried to mount database and getting following error

    PS C:\Users\sp_farm> Mount-SPContentDatabase -Name WSS_Content_94af0a10e6964c2eb
    cad4bc689af7b7 -WebApplication http://msapps:33955 >C:\PackagesList\Mount1.log
    100.00% : SPContentDatabase Name=WSS_Content_94af0a10e6964c2ebcad4bc689af7...
    Mount-SPContentDatabase : Action 15.0.19.1 of Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence failed.
    At line:1 char:1
    + Mount-SPContentDatabase -Name WSS_Content_94af0a10e6964c2ebcad4bc689af7b7
    -WebAp ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ~~~
        + CategoryInfo          : InvalidData: (Microsoft.Share...ContentDatabase:
       SPCmdletMountContentDatabase) [Mount-SPContentDatabase], SPUpgradeExceptio
      n
        + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletMountCon
       tentDatabase

    Regards,

    Mehar


    Thursday, April 17, 2014 8:51 AM
  • can you share the log file?

    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

    Thursday, April 17, 2014 5:28 PM
  • Hi Waqas,

    Here are log files:

    Upgrade-20140417-024612-238

    Upgrade-20140417-024612-238-error

    Regards,

    Mehar

    Thursday, April 17, 2014 6:12 PM
  • No access, i send you request.

    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

    Thursday, April 17, 2014 6:31 PM
  • Hi Waqas,

    Sorry was forget to make the links public.

    Can you please try now ?

    Regards,

    Mehar

    Thursday, April 17, 2014 6:43 PM
  • Error from the Logs clearly telling us that your database is not right, did take the backup and restore it 2013 or what?

    run the DBCC CHECKDB against the db will tell you the story, looks like some pages corrupted.

    here is the error in log:

    "04/17/2014 02:46:50.49 powershell (0x1744) 0x1444 SharePoint Foundation Upgrade SPContentDatabaseSequence al2pi ERROR Error running SQL DDL Script:   UPDATE      ADS  SET      ADS.Partition = 0,      ADS.BSN = 100+AD.Level,      ADS.Size = AD.Size,.... System.Data.SqlClient.SqlException (0x80131904): SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:2907039; actual 0:0). It occurred during a read of page (1:2907039) in database ID 26 at offset 0x0000058b73e000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\WSS_Content_94af0a10e6964c2ebcad4bc689af7b7.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online."


    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

    Thursday, April 17, 2014 7:14 PM
  • I am using fresh backup. I also check database status through DBCC. There are errors:

    Here is the thread I have already started for it.

    http://social.msdn.microsoft.com/Forums/sharepoint/en-US/bf3c14be-d8a7-4917-b4f3-2bb4dc8168a8/can-we-bypass-dbcc-errors-using-skipintegritychecks-in-mountspcontentdata-?forum=sharepointadmin

    Thursday, April 17, 2014 7:28 PM
  • two things, either the backup is not completing successfully or you source database having the issue.

    Now, i would recommend you to open the Case with Support and fix it, because if Trevor's recommendation failed or you have in security about the data lost then you need to contact MSFT.


    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

    Thursday, April 17, 2014 7:33 PM