Upgrade to SharePoint 2010 Service Pack 2

Service Pack 2 for SharePoint 2010

Time to do some testing on my development server prior to upgrading the production system.  I will be doing the In Place upgrade with no rollback.  This will require a server restart and interruption of services intermittently.

  1. First determine the version you need to install.  Technet doesn't expose all of the installs on their page, thankfully Todd Klindt keeps his SharePoint version page up to date.
    1. http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=224
  2. Install the SharePoint Server with Project Server installer (KB2687452).
    1. In my case owstimer.exe threw lots of errors with the Visual Studio Just-In-Time debugger popup.
    2. I click cancel on debugging for each error.
    3. Reboot server after install complete.
  3. Install the Office Web Apps installer (KB2687470).
    1. Again more owstimer.exe issues that I cancel through.
  4. Open Powershell and run this command:
    1. psconfig.exe -cmd upgrade -inplace b2b
    2. This fails the first time, I have read this is common, perhaps to do with Forefront Identity Service used with the User Profile Service.
    3. Run the command again and it works this time.
  5. Central admin website works and I verify that the SP2 version is shown in the upgrade section as well as in the database, Config DB, Versions table.
  6. Main web application hosting a site collection does not resolve.
  7. Run iisreset, now none of the web applications browse, they show HTTP Error 503. The service is unavailable.
  8. Go to IIS Manager, browse the Application Pools.
    1. The Central Admin, Fast Search Admin, User Profile Service, and Security Token Service pools are stopped.
    2. Started the Security Token Service pool, success.
    3. Started the Central Admin pool, success.
    4. Started the User Profile Service pool, success.
    5. Started the Fast Search Admin pool, success.
  9. Query the status of Services on Server with this powershell command:
Write-Host "STARTED"
    Get-SPServiceInstance | Where-Object {$_.Status -eq 'Online'} | Sort-Object TypeName | Format-Table @{Expression={$_.TypeName};Label="SharePoint Service";width=65},@{Expression={$_.Id};Label="GUID - Identity";width=45}
      Write-Host "STOPPED"
        Get-SPServiceInstance | Where-Object {$_.Status -eq 'Disabled'} | Sort-Object TypeName | Format-Table @{Expression={$_.TypeName};Label="SharePoint Service";width=65},@{Expression={$_.Id};Label="GUID - Identity";width=45}
          If ((Get-SPServiceInstance | Where-Object {$_.Status -ne 'Disabled' -and $_.Status -ne 'Online'}) -ne $null)
            {
                  Write-Host "OTHER"
                    Get-SPServiceInstance | Where-Object {$_.Status -ne 'Disabled' -and $_.Status -ne 'Online'} | Sort-Object TypeName | Format-Table @{Expression={$_.TypeName};Label="SharePoint Service";width=65},@{Expression={$_.Id};Label="GUID - Identity"},Status
                  }
                  1. The only Stopped services are:
                    1. Application Registry Service
                    2. Claims to Windows Token Service
                    3. Document Conversions Launcher Service
                    4. Document Conversions Load Balancer Service
                    5. Lotus Notes Connector
                    6. Microsoft SharePoint Foundation Sandboxed Code Service
                    7. Microsoft SharePoint Foundation Subscription Settings Service
                    8. SharePoint Foundation Search
                  2. None of these are necessary so I browse to Central Admin.  Working fine.
                  3. Browse to the web applications, they all work.

                  Comments

                  Post a Comment

                  Popular posts from this blog

                  SharePoint Designer 2013 Approval Workflow with Comments

                  Image
                  Adding Comments to a SharePoint 2013 Approval Workflow I needed the ability to capture comments from Approval Tasks in a workflow.  This has changed greatly in 2013 workflows.  Everything is more modular and as such must be built somewhat from scratch.
                  SharePoint 2013 workflows can become corrupt.  This may have been fixed by a patch, but please refer to a previous post before creating any 2013 workflows in Designer: http://www.ericjochens.com/2014/12/sharepoint-2013-workflow-observations.htmlSharePoint 2013 does not have a built-in approval workflow, nor does a built-in task item include comments.  I solved this by building my own approval workflow, and using a custom content type to include a comments field.A SharePoint 2013 Workflow will not store the Task ID when a task is created, so you cannot do a lookup into that task list to grab comments or any other field.  I solved this by creating a separate workflow in the task list to read the Related Items column, and update the origin…
                  Read more

                  Change SharePoint server hostname and Web Application Names

                  Note: I realize that many admins are reluctant to delete web applications.  I personally know why I ma doing it and how to achieve this easily.  You should always retain any customization you have added to the site, like web.config mods, etc.  The Alternate Access Mappings are always available, but they leave open holes that I do not wish to keep active.  I like a clean setup.
                  Why? Perhaps you need to clone a development, test, or some SharePoint server and you need to change the hostname so that it can exist on the same domain without a SID conflict.  Or you just have a use-case for wanting to rename the hostname of a SharePoint server.  It can be done, just make sure you go through all of the steps.

                  The Rename-SPServer PowerShell command can also be used to change the SQL Server name, for the case where you might move the databases to a new SQL server or instance and you need to point all of the farm servers to this new hostname\instance.

                  Changing the hostname isn't that bad, bu…
                  Read more

                  The Timer Service Failed to Recycle

                  Image
                  SharePoint Timer Service Failed to Recycle In the Monitoring section of SharePoint Central Administration a Health Analyzer rule appears warning about:

                  The timer service failed to recycle.
                  Title The timer service failed to recycle. Severity 2 - Warning Category Performance Explanation
                  The last attempt to recycle the timer service failed as have most of the other attempts during the past week. Recycling typically fails because other timer jobs are running when the recycle is scheduled. To view which jobs blocked the recycle view the history for the recycle job and click on the failed status link for more information. The error message for the failed job entry will contain a list of jobs that were still running. Remedy
                  Change the schedule for the timer recycle job so that it does not conflict with other long-running timer jobs.
                  Failing Services
                  SPTimerService (SPTimerV4)
                  Environment SharePoint Server 2010 Enterprise
                  On-Premises
                  3 Web Servers, 3 Application Servers, 1 FAST Server, Acti…
                  Read more