We have several SP 2010 sites.  When we first put the first of them up we had a little trouble with the User Profile Synchronization service but managed to get it working.  In the subsequent installations all was good.  Recently all of the UPA services stopped.  Both Filefront identity manager services show disabled and stopped.  Trying to start the UPS service in the configuration manager doesn't work on any of them.

 

I double checked everything stated here for permissions and whatnot..

http://blogs.msdn.com/b/russmax/archive/2010/03/20/sharepoint-2010-provisioning-user-profile-synchronization.aspx

All of our local and AD domain permissions are present.  When we try to fire up the UPA this exception is logged.

The configuration database was queried for a non-existent object with the id 213b3181-bc35-4b42-8aa4-a4c1c0455ed3. Most commonly, this is caused by removing an SPFeatureDefinition without writing upgrade code to remove references to the feature from each site.

Updating SPPersistedObject UserProfileApplication Name=User Profile Service Application. Version: 749423 Ensure: False, HashCode: 3276456, Id: f5cbf5a6-5113-4afd-952b-c73e35d69932, Stack:  
 at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()   
 at Microsoft.SharePoint.Administration.SPIisWebServiceApplication.Update()   
 at Microsoft.Office.Server.Administration.UserProfileApplication.Update()   
 at Microsoft.Office.Server.Administration.UserProfileApplication.ResetILMFlags()   
 at Microsoft.Office.Server.Administration.ProfileSynchronizationSetupJob.Execute(SPJobState state)   
 at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)   
 at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result)

Updating SPPersistedObject ProfileSynchronizationSetupJob Name=ProfileSynchronizationSetupJob. Version: 749435 Ensure: False, HashCode: 8255333, Id: 7b73978a-04c5-4b03-b999-3403ab537514, Stack:  
 at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()   
 at Microsoft.SharePoint.Administration.SPJobDefinition.Update()   
 at Microsoft.Office.Server.Administration.ProfileSynchronizationSetupJob.Execute(SPJobState state)   
 at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)   
 at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result)

The Execute method of job definition Microsoft.Office.Server.Administration.ProfileSynchronizationSetupJob (ID 7b73978a-04c5-4b03-b999-3403ab537514) threw an exception. More information is included below.  An update conflict has occurred, and you must re-try this action. The object UserProfileApplication Name=User Profile Service Application was updated by IBTS\wap2010adm, in the OWSTIMER (8128) process, on machine SIAMAT.  View the tracing log for more information about the conflict.

Exception stack trace:  
 at Microsoft.SharePoint.Administration.SPConfigurationDatabase.StoreObject(SPPersistedObject obj, Boolean storeClassIfNecessary, Boolean ensure)   
 at Microsoft.SharePoint.Administration.SPConfigurationDatabase.Microsoft.SharePoint.Administration.ISPPersistedStoreProvider.PutObject(SPPersistedObject persistedObject, Boolean ensure)   
 at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()   
 at Microsoft.SharePoint.Administration.SPIisWebServiceApplication.Update()   
 at Microsoft.Office.Server.Administration.UserProfileApplication.Update()   
 at Microsoft.Office.Server.Administration.UserProfileApplication.ResetILMFlags()   
 at Microsoft.Office.Server.Administration.ProfileSynchronizationSetupJob.Execute(SPJobState state)   
 at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)

I'm thinking something is wrong with the database?  But I'm at a loss..

• Moved by Mike Walsh FIN Tuesday, April 26, 2011 6:00 AM "We have several SP 2010 sites. " Not a general question and not a pre-SP 2010 question. (From:SharePoint - General Question and Answers and Discussion (pre-SharePoint 2010))

Thanks for the interest.  We went ahead last week and called Microsoft and paid them to help us.  After a few days of troubleshooting using a ULS viewer the MS tech discovered this article which perfectly fit my problem.  The answer was installing these two SharePoiint patches in to our environments.  I did so and fixed them all.

 

I found the below KB article that explains the issue you are facing.

http://support.microsoft.com/kb/983497

 

Solution : Install June 2010 CU

 

Procedure to install
===============
1. Before installing above updates please take the SQL Backup of SharePoint Databases ( Particularly Configuration and Content Databases )
2. Take Farm backup using the Central Administration > Backup and Restore > Perform a backup.
3. On the SharePoint Server first install http://support.microsoft.com/kb/2028568 (SharePoint Foundation 2010)
4. Reboot the Server
5. On the SharePoint Server  install http://support.microsoft.com/kb/983497 (SharePoint Server 2010)
6. Reboot the Server
7. Click on Start > All programs > Microsoft 2010 SharePoint Products > Run SharePoint 2010 Product and Configuration Wizard > Next > Yes > Do not disconnect from this server farm > Next >
No this machine will continue to host the Web Site > Next  > finish all the steps. ( In short keep all the Settings as default and needs to be done on all servers in the farm)
8. SharePoint upgrade to june2010 CU completes .
9. Check the Result.

 

Regards,

Moreno Fernandes

Support Engineer | SharePoint Technologies | Microsoft Corporation

• Proposed as answer by Thomas Balkeståhl Wednesday, February 15, 2012 7:39 AM

Kindly remove the config cache under program data in c drive.

• Proposed as answer by Daniel Fioqui 12 hours 32 minutes ago

Resolved in SharePoint 2013 15.0.4667.1000.

http://blogs.msdn.com/b/jamesway/archive/2011/05/23/sharepoint-2010-clearing-the-configuration-cache.aspx

Thanks!