SharePoint 2007 to SharePoint 2013 Upgrade - Need to Goto SharePoint 2010 First?

All,
I've seen some posts that say one can go from SharePoint 2007 to SharePoint 2013 - without upgrading to SharePoint 2010. Other posts say otherwise.
Therefore, what is indeed the answer. Ideally I'm looking to stand-up a new SharePoint 2010 or SharePoint 2013 farm then likely do a detach then upgrade of the SharePoint 2007 content databases to SharePoint 2010 or 2013.
Thanks

If you want to do a standard SharePoint upgrade, yes you must go to SharePoint 2010 prior to 2013. If you want to use a 3rd part/in-house custom application content migration upgrade, then you can go straight from SharePoint 20xx to 2013.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Similar Messages

  • Unable to edit document from SharePoint 2007 using Office 2013 and IE 11

    I am getting the following error when I try to edit a document from SharePoint 2007: "Edit document
    requires a Windows Sharepoint services-compatible application and Microsoft Internet Explorer 6.0 or greater". I am using Windows 7 with Office 2013 and Internet Explorer 11. Troubleshooting steps that I've tried so far (that haven't worked) are as follows:
    1) repaired Office; 2) switched from 64 bit version of IE to 32 bit version; 3) moved the owssupp.dll from C:\Program Files (x86)\Microsoft Office\Office14\ to C:\Program Files (x86)\Microsoft Office\Office15; 4) tried removing old versions of Office (but
    I still need to use Office Communicator 2007 r2 and couldn't figure out how to get rid of the Office14 files from Program Files); and 5) running SharePoint in IE compatibility mode. Please advise...thanks!

    Hi,
    It seems you installed mixed version Office2007/2010/2013 on your client machine?
    I would suggest you remove all Office 2007 and 2010 version, and reinstall Office 2013(include Office Tools->Microsoft SharePoint Foundation Support component) on your machine, and make sure "Open SharePointDocuments class" add-on is enabled
    from IE11, then check if it could fix the issue.
    If above works, please test again after installing the Office Communicator 2007 r2 on your machine.
    http://social.microsoft.com/Forums/en-US/3e8c0976-2794-49a2-92fe-6a254b3cc4ca/a-microsoft-sharepoint-foundation-compatible-application-could-not-be-found?forum=projserv2010setup
    http://blogs.technet.com/b/emeaoffice/archive/2013/04/29/you-get-an-error-message-when-you-open-an-office-file-from-sharepoint-on-a-computer-on-which-you-installed-more-than-one-version-of-office.aspx
    Thanks,
    Daniel Yang
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Daniel Yang
    TechNet Community Support

  • SharePoint 2007 performance issue after upgrading the operating system

    We upgraded the operating system of our SharePoint Server 2007 from 2003 to 2008 R2. After upgrade we rebuilt the SharePoint using content DBs we backed up before upgrade. All settings is same except that we moved the DBs to new SQL servers. Now users are
    reporting performance issue with sites. I experienced it myself some of the pages takes 9-30 seconds to load. Also our SharePoint server is single server. I monitored the SharePoint Server and it is fine. I did fiddler trace and here are the result. I see
    lots of 401 (login failed) errors then 302 (redirect) then 200 (OK). Do you know why we are getting 401 errors?
    Result
    Protocol
    Host
    URL
    Body
    Caching
    Content-Type
    Process
    184
    401
    HTTP
    sp07.ourcompany.com
    /bif/EUROPE-AMA
    341
    text/html; charset=us-ascii
    iexplore:15344
    185
    302
    HTTP
    sp07.ourcompany.com
    /bif/EUROPE-AMA
    196
    text/html; charset=UTF-8
    iexplore:15344
    186
    401
    HTTP
    sp07.ourcompany.com
    /bif/EUROPE-AMA/default.aspx
    341
    text/html; charset=us-ascii
    iexplore:15344
    187
    200
    HTTP
    sp07.ourcompany.com
    /bif/EUROPE-AMA/default.aspx
    105,487
    private, max-age=0; Expires: Mon, 22 Dec 2014 21:37:48 GMT
    text/html; charset=utf-8
    iexplore:15344
    188
    401
    HTTP
    sp07.ourcompany.com
    /_layouts/1033/styles/calendar.css?rev=BrbrIU86qTG2EHx1ZUuFBQ%3D%3D
    341
    text/html; charset=us-ascii
    iexplore:15344
    189
    200
    HTTP
    sp07.ourcompany.com
    /_layouts/images/prevbuttonltr.gif
    76
    max-age=31536000
    image/gif
    iexplore:15344
    190
    200
    HTTP
    sp07.ourcompany.com
    /_layouts/images/nextbuttonltr.gif
    78
    max-age=31536000
    image/gif
    iexplore:15344
    191
    200
    HTTP
    sp07.ourcompany.com
    /_layouts/images/day.gif
    1,051
    max-age=31536000
    image/gif
    iexplore:15344
    192
    200
    HTTP
    sp07.ourcompany.com
    /_layouts/images/month.gif
    1,068
    max-age=31536000
    image/gif
    iexplore:15344
    193
    200
    HTTP
    sp07.ourcompany.com
    /_layouts/1033/styles/calendar.css?rev=BrbrIU86qTG2EHx1ZUuFBQ%3D%3D
    28,814
    max-age=31536000
    text/css
    iexplore:15344
    194
    200
    HTTP
    sp07.ourcompany.com
    /_layouts/images/week.gif
    1,057
    max-age=31536000
    image/gif
    iexplore:15344
    195
    200
    HTTP
    sp07.ourcompany.com
    /_layouts/images/weekbox.gif
    149
    max-age=31536000
    image/gif
    iexplore:15344
    196
    200
    HTTP
    sp07.ourcompany.com
    /_layouts/images/alldayDefault.gif
    157
    max-age=31536000
    image/gif
    iexplore:15344
    197
    200
    HTTP
    sp07.ourcompany.com
    /_layouts/images/calnumBttntoday.gif
    146
    max-age=31536000
    image/gif
    iexplore:15344
    198
    200
    HTTP
    sp07.ourcompany.com
    /_layouts/images/calnumBttn.gif
    95
    max-age=31536000
    image/gif
    iexplore:15344

    Hi
    when you request a  Site collection (http://domain/) or a Site (http://domain/foo/) of your Publishing Site you get redirected to the http://domain/Pages/<WelcomePage>.aspx. SharePoint 2007 uses the 302 header (location temporarily moved) for
    this purpose. Surprisingly even WSS uses the 302 header to redirect a root url to the default.aspx. In comparison ASP.NET uses an internal redirect to render the default page when the root url requested: there is no redirect in this situation.
    Check the link which can give more input
    http://blog.mastykarz.nl/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/
    for error 401 you can check this link
    http://discussions.citrix.com/topic/97027-no-resources-401-unauthorized/d
    and check SharePoint ULS logs and event viewer for any exceptions.
    Please mark the Answer and Vote me if you think that it will help you to resolved your issue

  • SP-2007 to SP-2013 Upgrade - Visual Upgrade?

    Hi,
    We will upgrading the existing SP-2007 application to SP-2013 using database attach method. The current SP-2007 application is using custom master page.
    So the approach is, we will first upgrade from SP-2007 to SP-2010 then to SP-2013. I would like to know if I have to do Visual upgrade in 2010 environment before I take the SQL database backup of SP-2010 application, or I can do the UI upgrade
    only once after I move to SP-2013?
    Thanks,
    Pat

    I'm not 100% positive of the answer, but I think you would need to do that.  More importantly I definitely believe you will have fewer issues if you upgrade fully at the 2010 level.
    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

  • Lightroom 5 upgrade: need to re-install LR2 first?

    I own a copy of Lightroom 2.  I have just moved from pc to iMac and wish to upgrade to Lightroom 5 with no carry-over of photo files.  Will I have to load Lightroom 2 onto the iMac before uploading Lightroom 5 Upgrade or does it come as a complete package?

    Lightroom 5 is a complete standalone install. No need to install LR2 on the PC first.
    When you enter your LR5 serial number, you will be asked to enter the serial number from an earlier qualifying version.
    Enter your LR2 serial number and the LR5 install will complete.

  • Installing SharePoint 2007 Integration Kit on BO XI R2 SP5

    Hi there,
    We are trying to install sharepoint 2007 integration kit but keep getting the error message:
    "SP3 patch is required to install the sharepoint 2007 integration kit"
    Our setup...
    SharePoint 2007 running on its own Windows 2003 server
    BusinessBojects Enterprise XI Release 2 Support Pack 5 running on its own Windows 2003 server
    We installed the .Net SDK and Web Componet Adapter (WCA) of BusinessBojects Enterprise XI Release 2 Support Pack 5 on our SharePoint server
    Now, both versions of .Net SDK and WCA are the same on BO and SharePoint as required
    However after two attempts of installing the PIK we still get the message
    "SP3 patch is required to install the sharepoint 2007 integration kit"
    Does anyone know what is requried here?
    Thanks,
    Bernard.

    Hi Amit,
    Thanks for your response. I am not 100% sure of the answer to question 1 as we had someone external patrhing our servers and attempting to install the PIK. But I have detailed below the Crystal related products that were put onto the SharePoint server:
    1)
    Crystal Reports Server XI
    Crystal Reports Server XI R2 Service Pack 2
    Crystal Reports Server XI R2 Service Pack 5
    Crystal Reports Server XI Release 2 .NET 2005 Server
    I think he could have selected just the .NET SDK and WCA components from the main install and got to SP5 that way.
    2) The PIK I believe is to be SP2 from looking at the setup.ini file
    Msi=win32\cesp2k7.msi
    ProductName=BusinessObjects XI SharePoint 2007 Portal Integration Kit
    MsiMajorVersion=2
    MsiMinorVersion=0
    MsiBuildNumber=2600

  • From Exchange 2007 to exchange 2013

    hi everyone,,
    I need a video with brief description of how to deploy exchange 2007 to four servers exchange 2013
    please to help,
    thnx 

    Hi,
    For your reference, here are some articles and step by steps migration from Exchange 2007 to Exchange 2013:
    Upgrade from Exchange 2007 to Exchange 2013
    https://technet.microsoft.com/en-us/library/jj898581(v=exchg.150).aspx
    Part 1: Step-by-Step Exchange 2007 to 2013 Migration
    http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
    Additionally, we can use Microsoft Exchange Server Deployment Assistant for deployment help. It is a web-based tool that asks you a few questions about your current environment and then generates a custom step-by-step checklist that will
    help you deploy different versions of Exchange Server for different types of scenarios:
    https://technet.microsoft.com/en-us/office/dn756393.aspx
    Regards,
    Winnie Liang
    TechNet Community Support

  • Upgrade SharePoint 2007 SSRS integrated mode to SharePoint 2013 Reporting Service (SSRS-2014)

    Hi
    We are upgrading a SP-2007 site with SSRS integrated reports to SP-2013 and SSRS-2014. As there are many changes done in SP-2013, I would like to know if any of the existing SP-2007 reporting service database need to upgraded to SP-2013 or just upgrading
    the SP-2007 content database to SP-2013 and creating a new Reporting Service application will be working fine?
    Thanks,
    Pat

    You'll want to do a few things:
    Export the encryption key from the SSRS Configuration application in SharePoint 2007.
    Migrate the content database from SharePoint 2007 SP2+ to SharePoint 2010, to finally SharePoint 2013.
    Install SSRS 2012 SP1+ on SharePoint 2013.
    Migrate the SSRS databases to the SharePoint 2013 SQL Server.
    Create a new SSRS Service Application in SharePoint 2013 using the same named databases on the new SQL Server.
    Import the encryption key to the SSRS SA.
    http://msdn.microsoft.com/en-us/library/jj219068.aspx
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • SharePoint 2007 to 2013 Upgrade - Load Control Template Failures

    I am trying to upgrade SharePoint 2007 content databases to 2013 using 2010 as interim migration platform.
    When the databases are attached and upgraded to 2010, everything works fine. Once the databases are moved to 2013 environment and upgraded, the sites start to fail. Some pages/sites open up fine but most of the time they take a long time loading and ultimately
    return 'Sorry something went wrong' errors and logs point to load control template failures. The errors are not specific to one site or one specific set of files, every time I try to open the page I get failure with a new random ascx file. I have tried a lot
    of things but nothing has worked so far. It is really getting really hard to get to the root of the problem. I would really appreciate if someone can help me with fixing the issue.
    Here is what I have tried to far to try to fix the issue:
    1- Restarted IIS on all WFEs (2013)
    2- Cleared Configuration Cache and restarted everything
    3- Tried to manually change the layouts folder path under IIS site for the web application
    4- Cleared .net temporary files 
    5- Setup whole new 2013 environment on a single server as WFE/APP and tried restoring to this new Farm, faced exactly the same issue.
    6- Tried to upgrade Web application under 2010 to use Claims Based Authentication and then Upgrade to 2013, still same issue.
    7- Attached classic mode databases to 2013 then upgraded from within 2013 to claims based authentication but this did not affect anything related to control templates.
    PS. There are some customizations in the original 2007 farm (a few Fab 40 templates and 3-4 third party solutions), none of which have been deployed to upgraded enviornments. Does this have anything to do with load control template failures? Although the
    error is thrown even on sites that did not use custom templates.
    Is there anything I can do to fix this? This is kind of a major road block now and really affecting our migration schedule. I hope someone can help or direct me in the right direction. Thanks.

    AB
    Please share ULS log for more detail.
    As for now you can check with user control appearing randomly in error if any of these contains " &#44
    " code in page directive or reference directives and replace them with comma ",". Fab 40 controls do not work straight away in SharePoint 2013. you need to have install then one by one after copying them over to
    new environment. User PowerShell command to Install them. Please share log detail

  • Third party tools to upgrade sharepoint 2007 to sharepoint 2013

    I'm looking for third party tools that can be used to upgrade sharepoint 2007 to sharepoint 2013. Any suggestions?
    Thanks,
    JohnWeb

    Hi,
    To migrate from 2007 to 2013 directly.  I believe AvePoint and possibly Axceler have such products.
    https://social.technet.microsoft.com/Forums/office/en-US/f46e4593-1283-4aec-bd63-564779883ac8/upgrade-moss2007-to-sharepoint-2013?forum=sharepointadmin
    http://social.technet.microsoft.com/wiki/contents/articles/15743.sharepoint-2013-upgrading-from-sharepoint-2007-q-a.aspx
    http://www.threewill.com/the-final-four-or-five-sharepoint-migration-tools/
    Regards
    Prasad Tandel

  • SharePoint 2007 (WSS 3.0) migration to SharePoint Foundation 2013

    Hi
    I have a requirement to migrate a SharePoint 2007 (WSS 3.0) farm to a SharePoint Foundation 2013 farm. The WSS 3.0 farm has SQL Server 2005 Standard running so no restrictions on the size of the content database. The SharePoint Foundation 2010 and 2013 farms
    will share the same SQL Server 2012 Standard instance (as I know WSS 3.0 will have to be migrated to 2010 before 2013). I also have two other WSS 3.0 farms (so three WSS 3.0 Farms, lets call these A (250GB), B (90GB) and C (60GB)) that I need to migrate
    into WSS 3.0 Farm A before the migration to SP 2010.
    My question is, can I migrate a 400GB WSS 3.0 site collection to SP 2010 or will I have to split this into separate site collections? I have read that there is a best practice limit of 100GB per site collection but this does not stop a larger migration from
    happening. Obviously over time when the migration has completed to SharePoint Foundation 2013 the single site collection will grow and grow so perhaps now is the right time to split this out into, say, year named site collections, but surely this will incur
    an end of year process to create new site collections and a custom dev headache due to different locations to send newly created sites?
    Thanks.

    The answer is Yes, and you are correct about the best practice of a limit of 100GB,
    although, document and record centers (e.g. non collaborative) can go much higher.
    http://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx#ContentDB
    That being what it is, your sites will perform better if you find a topology that allows the content databases to be under 100GB each.  You can use Move-SPSite to accomplish that feat.
    You'll want a separate instance for 2010 and a separate instance for 2013
    and finally, put some quota's in place and then governance document\statement that informs users that 100 GB is the max for any given site collection that uses collaborative features (calendars, lists, workflows, etc.)
    The simple path is explained on technet, go from 2007 to 2010 (you can inplace upgrade if you want) then go from 2010 to 2013, database detach and attach is only way.
    please check the below link that explains more about the migration from share point 2007->2013.
    http://technet.microsoft.com/en-us/library/cc262483(v=office.15)
    Stacy www.sharepointpapa.com

  • What is the best way to migrate SharePoint 2007 to 2013?

    HI All,
    I would like to migrate SharePoint 2007 to 2013, may i know the easiest way to migrate? Thanks in advance

    Hi,
    “You cannot upgrade directly from the server products in the Office 2007 release to SharePoint 2013. The changes between versions are too great, and the hardware requirements differ so much between versions that a direct upgrade is not possible
    or supported. However, you can perform a series of database-attach upgrades to first upgrade your content to SharePoint 2010 Products and then to SharePoint 2013. This article describes how to perform these sequential database-attach upgrades.”
    Agree with Jesper, and here are the links for your reference:
    http://blogs.msdn.com/b/ronalg/archive/2013/01/28/can-i-upgrade-from-sharepoint-2007-directly-to-sharepoint-2013.aspx
    http://technet.microsoft.com/en-us/library/ee947141.aspx
    Should you need more assistance, feel free to ask here.
    Regards,
    Rebecca Tu
    TechNet Community Support

  • Upgrading from Sharepoint 2007

    I am going to be upgrading my Sharpoint 2007 Intranet to either Sharepoint 2010 or 2013.
    I want to create an Intranet and an Extranet in this new upgraded version. I want that if a document is added to the Intranet then it will also be replicated to the Extranet.
    Does anyone know would I be better upgrading to SP 2010 or 2013 to facilitate this replication?
    Thanks.

    Hi,
    You need to migrate your SP 2007 to SP 2010 first then you can migrate to SP 2013.
    First ensure there is no error and green signal using "pre upgrade checker tool on your SP 2007 server".
    If everything is fine then explore the approaches which feasible to you with in your cost and hardware upgrade plan.
    If your SP 2007 site is just collaboration,I meant there is no custom application deployed on your web application,then DB attach method is the best approach.
    You can download the SharePoint 2010 VM for this migration or try the trial Windows Azure.
    Once done,create the host header based site collection in SP 2010(best to have) and extend "Extranet" zone.
    Murugesa Pandian.,MCTS|App.Development|Configure

  • SharePoint 2013 Upgrade Issue

    We are running a small farm with one app server and wfe server and sql server and in the process of upgrading SharePoint servers from RTM version 15.0.4420.1017 to SP1. However, app server shows the status of "upgrade required" in Servers in
    Farm in CA. When I run stsadm.exe -o localupgradestatus, the output results on app server are:
    38] content database(s) encountered.
    [0] content database(s) still need upgrade or cannot be upgraded.
    [56] site collection(s) are contained in the content databases.
    [0] site collection(s) still need upgrade.
    [49] other objects encountered, [1] of them still need upgrade or cannot be upgraded.
    Also, logs on app server after running psconfig are 
    PSCONFIG.EXE -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures 
    Timestamp              
    Process                                
    TID   Area                          
    Category                      
    EventID Level    
    Message Correlation
    01/14/2015 11:27:07.81 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    INFO SPWebApplication Name=SharePoint - name of the URL
    .... 10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:27:07.81 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    ERROR CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] failed.
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:27:07.85 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    INFO SPWebApplication Name=SharePoint - name of the URL....
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:27:07.85 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    ERROR Exception: Object reference not set to an instance of an object.
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:27:07.88 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    INFO SPWebApplication Name=SharePoint - name of the URL....
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:27:07.88 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    ERROR   at Microsoft.SharePoint.Administration.SPWebApplication.SetVersionOnIisWebSite(String binaryVersion, String buildVersion, DirectoryInfo di)     at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()
        at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CanUpgrade(Object o)
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:27:07.90 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxnf
    INFO SPWebApplication Name=SharePoint - name of the URL....
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:27:07.90 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxnf
    ERROR Cannot upgrade [Microsoft.SharePoint.Administration.SPIisWebSite].
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:28:06.25 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    INFO No context object
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:28:06.25 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    ERROR CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] failed.
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:28:06.28 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    INFO No context object
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:28:06.28 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    ERROR Exception: Object reference not set to an instance of an object.
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:28:06.34 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    INFO No context object
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:28:06.34 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession ajxme
    ERROR   at Microsoft.SharePoint.Administration.SPWebApplication.SetVersionOnIisWebSite(String binaryVersion, String buildVersion, DirectoryInfo di)     at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()
        at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CanUpgrade(Object o)
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:28:06.43 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession aj0ur
    INFO No context object
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    01/14/2015 11:28:06.43 OWSTIMER (0x2C94)
    0x1764 SharePoint Foundation Upgrade
    SPUpgradeSession aj0ur
    ERROR Upgrade Timer job is exiting due to exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft
    Shared\Web Server Extensions\15\LOGS\Upgrade-20150114-112257-939.log.  The number of errors and warnings is listed at the end of the upgrade log file.     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CheckPoint()     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.LogEnd()
        at Microsoft.SharePoint.Administration.SPUpgradeJobDefinition.Execute(Guid targetInstanceId)
    10b7df9c-5c81-a0c7-dd9d-a7c4dd5a14e7
    I checked event logs and ULS logs but find nothing which can help fix this issue ?

    Hi Sharma,
    According to your description, my understanding is that the app server shows "upgrade required" when you upgrade your SharePoint 2013 from RTM to SP1.
    Whether you upgrade your SharePoint on app server from RTM to SP1.
    If not, please install SP1 for your SharePoint on the app server.
    After installing SP1, you need to run SharePoint Product Configuration Wizard.
    Best Regards,
    Wendy
    Wendy Li
    TechNet Community Support

  • Master Page Gallery contents renders in old Sharepoint 2007 style after upgrade

    I have a site collection that is still rendering the Master Page Gallery items in the Sharepoint 2007 style instead of the Sharepoint 2013 style, and I can't pinpoint where this is coming from.  I'm sure it's from a resource that was customized some
    time before our Sharepoint 2010 upgrade, preventing the view from upgrading properly at this point.  I'm looking for advice on where to look to get to the root of this issue.
    Possibly other libraries are affected, but it is most apparent in the Master Page Gallery.
    Here's what the items should look like in Sharepoint 2013.  In html, the item name column dropdown menus are populated with div elements, and it has a blue background dropdown arrow when hovering over it.
    Here's what this site collection renders.  In html, the item name column dropdown menus are populated using table elements, and it has a solid border with a different dropdown arrow when hovering over it.
    Functionality wise, this is preventing master pages and page layouts from being checked in and checked out and approved from this view.  I'm only able to do these changes using the sitemanager page for this site collection right now.
    Other information:
    - There are other site collections and web applications in this same farm that are not affected, so I don't believe it is a modification made in the hive files
    - I've tried making new views of the master page gallery with no success
    - I've compared the contents of the AllItems.aspx form in this collection with the AllItems.aspx in a working collection and could not find any difference.
    - I suspected that the ListViewWebPart is not current, but I can't find where I can check on this and possibly reset it to site definition.  I reviewed all webparts in the _catalogs\wp gallery but can't find a webpart in there that is named ListViewWebPart.
    So, the million dollar question is where else should I be checking to get to the bottom of this?  Thanks!

    Hi Brad ,
    For your issue, you can view the Upgrade Status page in Site Settings to verify that upgrade has succeeded for a site collection.
    To view upgrade status in Site Settings 
    1.Verify that the user account that performs this procedure is a site collection administrator.
    2.On the Site Settings page for the site collection, in the Site Collection Administration section, click Site collection upgrade.
    3.On the Site Collection Upgrade page, click Review Site Collection Upgrade Status.
    4.The Upgrade Status page for the site collection is displayed.
    For more information, see
    Manage site collection upgrades to SharePoint 2013
    Also you can  go to _layouts/15/reghost.aspx (Site Settings -> Site Actions -> Reset to site definition) and reset the master page gallery to site definition version.
    Best Regards,
    Eric
    Eric Tao
    TechNet Community Support

Maybe you are looking for