Enabling enterprise features on SharePoint 2010 or upgrading from Standard license to Enterprise license fails on multiple server farm with the following error in GUI
An error occurred while enabling Enterprise features. Refer to the event logs on your server machines for more details. For more information on how to fix this error, refer to help.
Click OK to return to the SharePoint Central Administration Operations page."
Same time following concurrency exception is logged in eventlogs
An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException wasthrown. Additional exceptioninformation: An update conflict has occurred, and you must re-try this action
Every time we try to enable or upgrade to enterprise license in Multiple Server SP 2010 farm, it creates a one time job of each of the Server which kicks off psconfig simultaneously on all of the Server due to which we keep on getting the concurrency exception and feature activation never completes
2. First to make sure that the psconfig doesn’t start on all the Servers simultaneously we disable the timer service on all the Servers in the farm except the Server hosting Central Admin.
3. Try to enable enterprise features, it will fail but check event logs we should see a success for psconfig along MSInstaller logs for successful installation of Infopath, visio and other Services.
4. Now one by one run “Psconfig.exe –cmd services –install –cmd installfeatures” on all the Servers
5. Make sure we get success for psconfig and MSinstaller logs on all the Server after psconfig command completes
6. On Server hosting central admin run powershell cmdlet “set-spfarmconfig –installedproductrefresh”
7.Now we should see enterprise features enabled in Central admin
<p>Great article and fixed my issue which was driving me bonkers. </p>
<p>This worked as well for a SharePoint 2013 farm I upgraded from standard to enterprise. To be honest it's not immediately clear why it works but it did.</p>
Great, this worked for me! Some remarks: * At step 3 a messag appeared that the Upgrade Timer Job was still present on my farm. I had to manually delete that job before I was able to continue. * At step 4 I was unsure if I had to first enable the Timer
Service on that particular server, before doing the PSCONFIG. I decide to leave it stopped and that appeared to be OK. I also noticed that after executing the PSCONFIG command on the server, this also restarts the Timer Service. So no need to enable the Timer
Services on each server after the process. * It should be 'set-spfarmconfig –installedproductsrefresh' (you forget the 's' in the parameter).