I’ve just rolled out the March 2013 Public Update (PU kb2767999) and August 2013 Cumulative Update (CU kb2817616) to a SharePoint server. Got to admit, it’s been a while since I did any of this, but… yeah… never had to re-register SharePoint Services or stop and start services in order to patch an app. Guess I’m getting lazy…
From March Public Update onwards, the process is to stop the following 3 services in this order, run the update then restart the services in the reverse order.
net stop SPTimerV4
net stop OSearch15
net stop SPSearchHostController
net start SPSearchHostController
net start OSearch15
net start SPTimerV4
The info is covered here… http://blogs.technet.com/b/tothesharepoint/archive/2013/03/13/how-to-install-update-packages-on-a-sharepoint-farm-where-search-component-and-high-availability-search-topologies-are-enabled.aspx (I mean, is there a deployment out there somewhere not running search?)
Not only that, since the PU (http://support.microsoft.com/kb/2767999) for every non-service pack update applied to the server you need to follow the process as indicated above… AND re-register the Workflow engine. I’m sorry, what?????
Microsoft.Workflow.Client.ActivityValidationException: Workflow XAML failed validation due to the following errors:
Cannot set unknown member ‘CheckInItem.ItemId’. HTTP headers received from the server – ActivityId: 0a36dc6a-c872-41c9-8302-310378bfc1de. NodeId: 2013-SP. Scope: /SharePoint/default/7bf81cf4-ef48-4507-a0b5-53f948d26fd0/b44b51c4-8b55-4cfb-993f-66f6f873bafa. Client ActivityId : ea960b9c-dd02-5067-249a-2f0446fce574. —> System.Net.WebException: The remote server returned an error:
Not sure why they have to throw away the association for a CU or hotfix… ah well.