Monthly Archives: December 2011

SharePoint / Project Server – Service Pack 1 and June CU Refresh Package


This is for installation of “Service Pack 1” and the “June CU Refresh” upgrade to Project Server 2010. I have listed out the process for updating a farm (including the sequence of app server, project server, web front end).
 
Updating SharePoint 2010 is relatively OK, but introducing Project Server is a challange in itself. After reading a fair share of blogs, technet, here is how we proceeded.
 
Read Me First
  • Both packages are cumulative in terms of updates, refer to the KB articles below for additional details and download links. Project Server 2010 SP1 – http://support.microsoft.com/kb/2460047 Project Server 2010 June CU Refresh – http://support.microsoft.com/kb/2536600
  • Both packages are cumulative in terms of product version. You do not need to install SharePoint Foundation 2010 or SharePoint Server 2010 “Service Pack 1” or “CU” when you are installing the Project Server 2010 Service Pack 1 or Project Server 2010 June CU Refresh package. 
High Level Procedure Overview
  1. Run all command prompts and execute all packages using “Run As Administrator” (UAC)
  2. Download the installer locally on all SharePoint servers, ensure you have enough temp storage space
  3. Run Service Pack 1 installer on all SharePoint servers
  4. Run the June CU Refresh installer on all SharePoint servers
  5. Run Configuration Wizard on all SharePoint servers in the order starting with server hosting Central Admin, other Application servers and then any Web Front End servers.
Detailed Overview

Group Commands are listed below as they are referenced in the table.

  • Col A – net stop w3svc
  • Col B – net stop ProjectQueueService14
  • Col C – Install Project Server 2010 SP1
  • Col D – reboot
  • Col E – net stop w3svc
  • Col F – net stop ProjectQueueService14
  • Col G – Install Project Server 2010 June CU Refresh
  • Col H – reboot
  • Col I – net stop w3svc
  • Col J – net stop ProjectQueueService14
  • Col K – run SharePoint Configuration Wizard
The table below outlines the sequence in which you need to execute commands for that particular Group. There is a total of 43 tasks you need to complete, starting with #1.
  
Server Names
Col A
Col B
Col C
Col D
Col E
Col F
Col G
Col H
Col I
Col J
Col K
APP SERVER 1
Central Admin
1
 
7
12
17
 
23
28
33
 
39
APP SERVER 2
Project App
2
6
8
13
18
22
24
29
34
38
40
APP SERVER 3
something else
3
 
9
14
19
 
25
30
35
 
41
WFE 01
4
 
10
15
20
 
26
31
36
 
42
WFE 02
5
 
11
16
21
 
27
32
37
 
43
  • Complete all steps in a Column in the order indicated before moving to the next Column . As an example for “Column A”, perform steps 1, 2, 3, 4, 5 on the servers indicated in “Server Names” column before moving to Column B : Task 6. Column A command is “net stop w3svc”.
  • Steps in Column C can be run in parallel to save time.
  • Steps in Column G can be run in parallel to save time.
  • There will be a delay of 2~5 minutes (or more) before you see installer screen after executing “Run as Administrator” for Column C and Column G and that is normal. Do not log off or cancel any process from Task Manager.
  • If any installer asks you to reboot now, choose to reboot later (or choose ‘do not close applications’ and ‘reboot later’). Complete the installation and follow the reboot order listed above.
  • Steps in Column K needs to be executed and finished in whole before moving to the next step. None of the steps in Group K can be run in parallel.
Error at Step 39

There were two issues & resolutions described below.

Issue #1

This was a known issue. The SharePoint Configuration Wizard will fail at #39 in Column K. After it fails, close the wizard and start the “User Profile Synchronization Service” from Central Administration. The account to use (as logged in, and the service account) while starting is the farm account.

The User Profile Synchronization Service takes couple of minutes (10 maybe 15) to start. Once the User Profile Synchronization Service is started, open a command prompt and run following to complete #39.

psconfig.exe -cmd upgrade -inplace b2b -wait
 
After the above command is 100% complete, you can move to Step 40.
 
Issue #2
 
This was a new issue in Production only. In addition to the above Issue #1, another issue was resulting in the psconfig not completing. The error after running psconfig was
 
Failed to upgrade SharePoint Products.
 
An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException was thrown. Additional exception information: An update conflict has occurred, and you must re-try this action. The object SPUpgradeSession Name=Upgrade-20111020-172808-203 was updated by CORP\ACCOUNT, in the PSCONFIG (6100) process, on machine APPSERVER1. View the tracing log for more information about the conflict
 
This is caused due to the SharePoint 2010 Timer service not starting at all. Resolution is to manually start this “SharePoint 2010 Timer” service immediately after you run the psconfig command. The “SharePoint 2010 Timer” service is available under Control Panel, Administrative Tools and Services.
 
Clearing the cache was an option discussed in newsgroups http://support.microsoft.com/kb/939308, but it did not solve the issue of SPUpdatedConcurrencyException, the resolution was manually starting the Timer service.
 
Hope this helps you.
Advertisements