central Admin: An update conflict has occurred, and you must re-try this action.
I started to get this message everytime I try to Quiesce Farm. An unhandled exception occurred in the user interface.Exception Information: An update conflict has occurred, and you must re-try this action. The object SessionStateService Parent=SPFarm Name=SharePoint_Config is being updated by DOMAIN\username, in the w3wp process, on machine XXXXXX. View the tracing log for more information about the conflict. Here is the error messagefrom the trace log. Updating SessionStateService ID=f7c77330-df6e-48ba-b47f-e7102206d8ee, Version=34038 Updating SPPersistedObject SessionStateService Parent=SPFarm Name=SharePoint_Config. Version: 34038 Ensure: 0, HashCode: 66228199, Id: f7c77330-df6e-48ba-b47f-e7102206d8ee, Stack: at Microsoft.SharePoint.Administration.SPPersistedObject.Update() at Microsoft.SharePoint.Administration.SPService.Update() at Microsoft.Office.Server.Administration.SessionStateService.Update() at Microsoft.Office.Server.Internal.UI.QuiesceFarmPage.BtnStartQuiesce_Click(Object sender, EventArgs e) at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) at System.Web.UI.Page.ProcessRequest(HttpContext context) at ASP._admin_quiescefarm_aspx.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step,Boolean& completedSynchronously) at System.Web.HttpApplication.ResumeSteps(Exception error) at System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData) at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) at System.Web.HttpRuntime.ProcessRequestNoDemand(HttpWorkerRequest wr) at System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32 iWRType) UpdatedConcurrencyException: The object SessionStateService Parent=SPFarm Name=SharePoint_Config 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: DOMAIN\USER1 Process:w3wp Machine:HQ-SPSWEB-1 Time:February 27, 2007 10:04:42.0000 Current update information: User: DOMAIN\USER2 Process:w3wp Machine:HQ-SPSWEB-1 Time:May 30, 2007 01:36:34.7874 ConcurrencyException: Old Version : 34038 New Version : 0 Concurency exception happened during update of SessionStateService. ID=f7c77330-df6e-48ba-b47f-e7102206d8ee, Version=34038, Message=(null) Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SessionStateService Parent=SPFarm Name=SharePoint_Config is being updated by DOMAIN\USER1, in the w3wp process, on machine HQ-SPSWEB-1. View the tracing log for more information about the conflict. at Microsoft.SharePoint.Administration.SPConfigurationDatabase.StoreObject(SPPersistedObject obj, Boolean storeClassIfNecessary, Boolean ensure) at Microsoft.SharePoint.Administration.SPConfigurationDatabase.PutObject(SPPersistedObject obj, Boolean ensure) at Microsoft.SharePoint.Administration.SPPersistedObject.Update() at Microsoft.SharePoint.Administration.SPService.Update() at Microsoft.Office.Server.Administration.SessionStateService.Update() Not reporting to Watson because the appropriate timespan hasn't passed Unhandled page level exception. Path: /_admin/QuiesceFarm.aspx, Error: An update conflict has occurred, and you must re-try this action. The object SessionStateService Parent=SPFarm Name=SharePoint_Config is being updated by DOMAIN\USER1, in the w3wp process, on machine HQ-SPSWEB-1. View the tracing log for more information about the conflict., Details: Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SessionStateService Parent=SPFarm Name=SharePoint_Config is being updated by DOMAIN\USER1, in the w3wp process, on machine HQ-SPSWEB-1. View the tracing log for more information about the conflict. at Microsoft.SharePoint.Administration.SPConfigurationDatabase.StoreObject(SPPersistedObject obj, Boolean storeClassIfNecessary, Boolean ensure) at Microsoft.SharePoint.Administration.SPConfigurationDatabase.PutObject(SPPersistedObject obj, Boolean ensure) at Microsoft.SharePoint.Administration.SPPersistedObject.Update() at Microsoft.SharePoint.Administration.SPService.Update() at Microsoft.Office.Server.Administration.SessionStateService.Update() at Microsoft.Office.Server.Internal.UI.QuiesceFarmPage.BtnStartQuiesce_Click(Object sender, EventArgs e) at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SessionStateService Parent=SPFarm Name=SharePoint_Config is being updated by DOMAIN\USER1, in the w3wp process, on machine HQ-SPSWEB-1. View the tracing log for more information about the conflict. at Microsoft.SharePoint.Administration.SPConfigurationDatabase.StoreObject(SPPersistedObject obj, Boolean storeClassIfNecessary, Boolean ensure) at Microsoft.SharePoint.Administration.SPConfigurationDatabase.PutObject(SPPersistedObject obj, Boolean ensure) at Microsoft.SharePoint.Administration.SPPersistedObject.Update() at Microsoft.SharePoint.Administration.SPService.Update() at Microsoft.Office.Server.Administration.SessionStateService.Update() at Microsoft.Office.Server.Internal.UI.QuiesceFarmPage.BtnStartQuiesce_Click(Object sender, EventArgs e) at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) Not reporting 837w to Watson because the appropriate timespan hasn't passed Anyone encountered this issue before? Please let me know if anyone found a way to resolve this conflict. - Thanks, Karthik.
May 31st, 2007 1:44am

Karthik, I have the same problem when I attempt to extend one of my web applications or change the authentication provider for it. As of yet, I still haven't found a resolution for the problem. I know other people have experienced the same problem as well, but so far I'm unaware of anyone else that has found a solution for it either. Here is a post I put up a few weeks ago address the problem: http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sharepoint.setup_and_administration&mid=d09b257b-1038-4494-8f6e-f23d8741ceb4 If you come up with any solution I would love to hear it. Thanks and I'll let you know if I manage to come up with anything, Ben
Free Windows Admin Tool Kit Click here and download it now
May 31st, 2007 4:18pm

Did anyone find a solution to this issue?
July 24th, 2007 1:41am

I have yet to see a solution to this problem or two find a solution in all the looking I have done. If anyone has ever come up with a solution I would love to hear it! ~Ben
Free Windows Admin Tool Kit Click here and download it now
July 24th, 2007 2:49am

I had this error occur after having to restore an older copy of the configuration database. I was able to fix it by rerunning the SharePoint Products and Technologies Configuration Wizard and specifying to not removethe serverfrom the current server farm.
July 31st, 2007 10:30pm

Did anyone ever find a solution to this problem?I had the same thing occur on my MOSS 2007 Enterprise install and I don't even know what caused it. As a side effect I noticed that the Search Service was stuck in a status of Stopping aswell as not being able to create SSP's.There was other weirdness and after having MS work on my case for two months the whole site came crashing down, so my fix was to reinstall the front end and point it back to the content databases. Ofcourse now I'm having other problems with permissions and for some strange reason i can't access the /ssp/admin page for my SSP but the site's back!If anyone has a solution for this I'd really like to know and so would MS because I called on behalf of a Platinum partner and they couldn't even hazard a guess as to what caused this.Cheers,DOHC
Free Windows Admin Tool Kit Click here and download it now
February 4th, 2008 8:24am

I still don't have a solution or a reason as to why this happens. We had some other problems in our SharePoint installation, and I ended up having to rebuild the environment, recreate the sites and point them back to the old Content DBs. Not the ideal way to fix the problem as you lose any configuration settings and search information, but it did fix the problem. As weno longer have the problem, I haven't looked into it much lately, but I'll keep my eyes and ears open as it appears that this continues to be a problem. When I rebuilt our SharePoint environment I also upgrade to SP1. I have no idea if this helps the problems or clears up the issue in any way, but it might be something to try if you don't mind doing the upgrade.
February 11th, 2008 7:18pm

I have thesame issue and finally found this it worked for me. http://support.microsoft.com/kb/939308
Free Windows Admin Tool Kit Click here and download it now
March 17th, 2008 8:14pm

Actually the reseting the file system cache have resolved many issues we had in our farm. Microsoft tech support gave me this resolution to fix some issues we had with Usage Analysis. That fixed the issues I started in this thread. Good times! To resolve this issue, clear the file system cache on all servers in the server farm on which the Windows SharePoint Services Timer service is running. To do this, follow these steps: 1. Stop the Timer service. To do this, follow these steps: a. ClickStart, point toAdministrative Tools, and then clickServices. b. Right-clickWindows SharePoint Services Timer, and then clickStop. 2. Delete or move the contents of the following folder: %ALLUSERSPROFILE% \Application Data\Microsoft\SharePoint\Config\GUID 3. Start the Timer service. To do this, follow these steps: a. ClickStart, point toAdministrative Tools, and then clickServices. b. Right-clickWindows SharePoint Services Timer, and then clickStart.NoteThe file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm on which the Timer service is running.
March 24th, 2008 9:24pm

Thanks much for posting this. Following the steps to stop the timer, clear the file cache, and then restart the timer finally solved my problem (unable to set outgoing email and get it working in Sharepoint Central Admin, which we're using as part of Team Foundation Server).The link I followed was: http://support.microsoft.com/kb/939308Immediately after following these steps, I was able to configure outgoing email for both the server and virtual servers, and have alerts sent out.Thanks!Kirk Davis
Free Windows Admin Tool Kit Click here and download it now
July 16th, 2008 11:34am

Thanks! It is really works for me
September 25th, 2008 10:40am

Just another thumbs up for this post.Clearning the file cache worked a treat after I couldn't mod auth provider.
Free Windows Admin Tool Kit Click here and download it now
December 23rd, 2008 7:25pm

Thanks a lot..this really worked well and saved me.Veeramani.S
April 8th, 2009 5:09pm

After try this solution, the site and central admin are down, they say "file not found" until y restore all content deleted, someone have the same error?MFC
Free Windows Admin Tool Kit Click here and download it now
November 9th, 2009 5:47pm

The feature is: Microsoft Chart Controls feature My specific error is: Se ha producido un conflicto de actualizacin y debe volver a intentar esta accin. CSHLENGAHV\Administrador est actualizando el objeto SPWebConfigFileChanges Name=WebConfigChanges - 5840102e-8fef-40e9-9480-81c4d0b5b7ee Parent=SPWebApplication Name=SharePoint - 25719, en el proceso GaugeMSSInstaller, en el equipo CSHLENGAHV. Para obtener ms informacin sobre el conflicto, vea el archivo de seguimiento. MFC
November 9th, 2009 5:51pm

Hi I have followed same steps given in article, but still its not resolved. Please help me. I have cleared the cache and chaned the value to 1. I was stoped the timer service before going to perform the steps. Every thing has done by following artcile only. But still getting same error. Please help me..
Free Windows Admin Tool Kit Click here and download it now
October 12th, 2010 8:35am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics