while upgrading the SP 2013 RTM to SP1 with April 2o17 CU,and after running the command psconfig.exe -cmd upgrade -inplace b2b -force on the command prompt
am getting the below error in the error.log file: having a custom timer job feature is beamea orphaned/unwanted element. how can i remove this feature/soln from this farm,so that my farm is upgraded successfully.
Timestamp Process TID Area Category EventID Level Message Correlation 06/28/2017 18:57:44.05 PSCONFIG (0x1E9C) 0x2320 SharePoint Foundation Upgrade SPUpgradeSession ajxmm INFO SPContentDatabase Name=SharePoint_AdminContent_f8c70f4f-4086-4ab... 00000000-0000-0000-0000-000000000000 06/28/2017 18:57:44.05 PSCONFIG (0x1E9C) 0x2320 SharePoint Foundation Upgrade SPUpgradeSession ajxmm WARNING Exception occured when querying feature with id [57996672-7e89-4082-b77e-66b6020ac924], skipping. Microsoft.SharePoint.SPException: Failed to find the XML file at location '15\Template\Features\JobReminders_TimerJob_Timer_JobRemindersFeature\feature.xml' at Microsoft.SharePoint.SPXmlDocCache.GetGlobalXmlDocument(String pathTemplateRelativeXml, SPFeatureDefinition featdef, Int32 compatibilityLevel) at Microsoft.SharePoint.Administration.SPFarmFeatureDefinitionContext.LoadFileAsXmlDocument(SPFeatureDefinition featdef, String feature RelativePath) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_Scope() at Microsoft.SharePoint.Upgrade.SPUpgradeSession.PopulateFeaturesTable(StringBuilder sqlstr) 00000000-0000-0000-0000-000000000000
Would like to add one more info. on this. the site collec in which i am runing these operations was a content-db-restore from another SP 2013 farm with same config-db version.
So does it mean that, this orphaned timer job info./feature was not removed from that farm? since its a timer job and deployed on a web appln scope, its still available in the farm.