Our Production SharePoint environment is managed by a dedicated team who recently applied April CU KB2965294 to our farm/all servers. We manage our own Test environment which should be as near a replica of Production as possible (with the exception its a stand alone box not a farm & the everything is all on the one box), so I installed the same update.

The upgrade was installed on test from the downloaded .msi & I ran psconfig afterwards. All seemed fine except in Central Admin\Review Database Status, one of the databases advised under status "Database is up to date, but some sites are not completely upgraded." The stsadm tool showed 19/32 site collections still required upgrading.

So I queried SP Powershell using Get-SPContentDatabase to get the content db's Id's, then ran Upgrade-SPContentDatabase. The window goes through the process but once at 100% I'm advised that the upgrade completed with errors. Consulting the log file it references it is littered with the following errors:

[powershell] [SPSiteWssSequence2] [WARNING] [8/20/2015 2:16:41 PM]: Feature could not be upgraded. Exception: Feature definition id 'cf51d108-a87f-4051-aae1-e275fc9caca6' could not be found.
[powershell] [SPSiteWssSequence2] [WARNING] [8/20/2015 2:16:41 PM]: Feature could not be upgraded. Exception: Feature definition id '758f13d1-e7d8-447d-83f2-426f72479bf2' could not be found.

&

[powershell] [SPSiteWssSequence2] [ERROR] [8/20/2015 2:16:41 PM]: Feature upgrade failed for Feature 'CompanyName.SharePoint.Platform.Feature.Setup_SeriesVisualizationRulesetConfiguration' (Id: '95abc29d-a4ca-4372-84b4-645b07b71450') in Web 'https://Weburl etc etc'.
[powershell] [SPSiteWssSequence2] [ERROR] [8/20/2015 2:16:41 PM]: Exception: Object reference not set to an instance of an object.
[powershell] [SPSiteWssSequence2] [ERROR] [8/20/2015 2:16:41 PM]:    at Microsoft.SharePoint.SPFeature.HandleUpgradeException(Exception e, Boolean continueUpgrade, Boolean markAsUpgraded, Boolean force)
   at Microsoft.SharePoint.Administration.SPFeatureDefinition.Upgrade(SPFeature feature, SPWebService webService, SPWebApplication webApp, SPSite site, SPWeb web, Boolean fForce)
   at Microsoft.SharePoint.SPFeature.Upgrade(SPSite site, SPWeb web, Boolean fForce)
   at Microsoft.SharePoint.Upgrade.SPSiteWssSequence2.DoUpgrade()

Now in Central Admin if I look under Upgrade & Migration/Upgrade Status the status has changed from "Successful" which it was at after the .msi/psconfig part to "Failed" - 7 Errors, 12 Warnings.

I'm completely stuck............can anyone help on how to update this database?

• Edited by bc1sjw Friday, August 21, 2015 8:24 AM

This smells like custom code:

'CompanyName.SharePoint.Ssp.Pv.Setup_SeriesVisualizationRulesetConfiguration'

Do you have any features with that name or have you had similar ones in the past? Would these be upgraded site collections from another farm?

Hi Alex,

I edited my original post as hadn't noticed how I'd worded it, but trying to keep my companies details as generic as possible.

'CompanyName.SharePoint.Platform.Feature.Setup_SeriesVisualizationRulesetConfiguration'

Yes I'm pretty sure this is a custom object by our developers; the emboldened parts I've replaced with more generic descriptions. This does relate to a custom component/feature on one of the sites that users query for information. I don't think they'd be from another farm but I'm not certain, our Test environment for our platform is a stand alone server not a farm.

Overall the entire update seemed complete and everything checked out until I saw the "Some sites not being upgraded" alert, everything seems fine to me although 19/32 collections still requiring update doesn't sound ideal.

Is this something that's fixable, and how big a deal is this in reality?

Hi,

The first exception shows the feature id "cf51d108-a87f-4051-aae1-e275fc9caca6" and "758f13d1-e7d8-447d-83f2-426f72479bf2" is not found or these feature were orphaned.

You have to remove the orphaned features before upgrading, please check this tool on CodePlex

https://featureadmin.codeplex.com

The second exception seems to be the problem with the workflow, may be Visio related, You have to install the WSP package related to this feature or activate before upgrade.