SharePoint 2013 Cumulative Updates can be problematic…

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
Install Update
net start SPSearchHostController
net start OSearch15
net start SPTimerV4

The info is covered here… (I mean, is there a deployment out there somewhere not running search?)

Not only that, since the PU ( 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.


About Brad Saide

I'm a SharePoint consultant. I'm also slowly going bald, seem to have a permanent spare tyre around my waist and enjoy socialising with friends over a beer or 10. The last 2 may possibly be related. Started working with SharePoint when the first version was in limited beta release (participated in the Technology Adoption Program while at Woolworths) and have been committed to the adoption of the technology as a business enabler ever since.
This entry was posted in Uncategorized. Bookmark the permalink.

2 Responses to SharePoint 2013 Cumulative Updates can be problematic…

  1. Amit says:

    The sharepoint designer activities and tasks are tied to activites.dll and its version… and it screws up current workflows created in previous CU…..

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s