There is an unsaved comment in progress. You will lose your changes if you continue. Are you sure you want to reopen the work item?
UpdatedConcurrencyException: FarmSettingStore Name=_pnpFarmConfig_ was updated by another user
Similar to what occurred at the end of issue 6889, I have been able to reproduce this problem. The complete text is:
08/18/2010 16:09:16.64 w3wp.exe (0x0FAC) 0x04DC SharePoint Foundation Topology 75bd High UpdatedConcurrencyException: The object FarmSettingStore Name=_pnpFarmConfig_ was updated by another user. Determine if these changes will conflict, resolve any differences,
and reapply the second change. This error may also indicate a programming error caused by obtaining two copies of the same object in a single thread. Previous update information: User: AA\administrator Process:vssphost4 (5348) Machine:AASP2010DEV Time:August
18, 2010 03:14:23.0000 Current update information: User: AA\administrator Process:w3wp (4012) Machine:AASP2010DEV Time:August 18, 2010 04:09:16.5230 e4057d12-e469-4f5d-9d06-4886da9a7497
08/18/2010 16:09:16.64 w3wp.exe (0x0FAC) 0x04DC SharePoint Foundation Topology 8xqy High ConcurrencyException: Old Version : 21301 New Version : 21301 e4057d12-e469-4f5d-9d06-4886da9a7497
08/18/2010 16:09:16.73 w3wp.exe (0x0FAC) 0x04DC Patterns and Practices SharePoint Guidance 0000 High SPFarmPropertyBag: Concurrency update failure when updating Key: 'PnP.Config.Key.Microsoft.Practices.SharePoint.DiagnosticAreas' e4057d12-e469-4f5d-9d06-4886da9a7497
08/18/2010 16:09:16.73 w3wp.exe (0x0FAC) 0x04DC Patterns and Practices SharePoint Guidance 0000 High ConfigManager: Failure saving config to 'CurrentSPFarm' level, retry count: '0', key: 'Microsoft.Practices.SharePoint.DiagnosticAreas' e4057d12-e469-4f5d-9d06-4886da9a7497
I have been redeploying the same feature multiple times which registers the diagnostic areas. I've had a lot of problems with the DLL from the feature being locked by VS2010, IIS, the SharePoint timer service, and the SharePoint User Code service (why this
is happening beats me). So I've been regularly recycling/restarting these components such that the latest version of the DLL will deploy correctly to the GAC. I also began using the Central Admin to deploy the solution package and feature instead of VS2010
to try and minimise this problem. There is a chance VS2010 might have been activating/deactivating the feature while I also was in Central Admin although I don't remember doing this.
I'm going to run the little app I wrote at the end of issue 6889 to delete the farm setting store so I can continue working. However I thought you might like to know this occurred.