• SharePoint 2010 Site Experience With SharePoint 2016

    While testing an upgrade today, I was reminded of a requirement when upgrading to SharePoint 2016 using the database attach method – you must upgrade all site collections to the SharePoint 2013 experience before you attempt to attach the database to a SharePoint 2016 farm. My test today is using a SharePoint 2010 content database and attempting an upgrade to SharePoint 2016. I first performed a database attach upgrade with a SharePoint 2013 farm, then performed the Test-SPContentDatabase PowerShell command on the database from my SharePoint 2016 farm. It is important to notice that the LegacySiteDetected error shown above is an UpgradeBlocking error, meaning the upgrade will fail if you…

  • Upgrade SharePoint 2010 to 2016 Release Candidate

    It is a frequent question – can I skip a SharePoint version when upgrading? For example can I do a direct upgrade from SharePoint Server 2007 to 2013? The answer is no, you can’t without having to use a migration product – which isn’t really “upgrading.” The path to upgrade SharePoint 2007 to 2013 includes an upgrade to SharePoint 2010 first. In March of 2015, Bill Baer, Senior Product Marketing Manager at Microsoft, asked if there was any demand for skipping ahead when doing a SharePoint upgrade (a.k.a. N-2 upgrade). #SharePoint question…if you could N-2 upgrade would you? I.e. 2010 > 2016 without stopping at 2013 first… — Bill Baer (@williambaer) March…

  • SharePoint 2010 Updates and 503 Error

    Today I updated a SharePoint Server 2010 test virtual machine with service pack 1 (SP1; Foundation and Server) and the August 2011 cumulative updates for SharePoint Foundation and SharePoint Server. I ran the SharePoint configuration wizard after installing all the updates. When I rebooted the server (suggested when encountering the User Profile sync problem after applying the patches) and tried to open one of the team sites, I received a 503 Service Unavailable error (as shown in the picture below). Service Unavailable – HTTP Error 503. The service is unavailable. Once I got over the “what did I do??!?” moment, I of course recognized this as an IIS error, not…

  • Error Connecting to Database Server

    I recently setup yet another SharePoint farm (this time using virtual machines) and ran into a problem that happens all too often. The scenario is this: I setup MS SQL server in preparation for getting SharePoint installed on a separate server. After setting up your service accounts in Active Directory and installing MS SQL on Server1, I set off installing SharePoint on Server2. When I got to the screen in the Specify Configuration Database Settings within the SharePoint configuration wizard, I received the following error: Cannot connect to database master at SQL server at ServerName. The database might not exist, or the current user does not have permission to connect…