Error A Web Configuration Modification Operation Is Already Running
Jameson - MSFTMarch 31, 20100 0 0 0 This week I finally got around to fixing a bug that would occasionally occur when deploying our solution based on Microsoft Office SharePoint Server (MOSS) 2007. In the solution we use a variety of different features to configure different aspects of the site (for example, creating a /Public site and configuring the default page for that site with a login Web Part as well as some initial content). We also use features to add Web.config elements, such as those required for configuring Forms-Based Authentication and integrating with various Web services. One of the problems that I encountered during the first deployment to the Production environment (PROD) is that when activating the features through a script, the following error occurred sporadically: A web configuration modification operation is already running. As a workaround, I simply activated the remaining features manually (initially by directly invoking stsadm.exe -o activatefeature, but later by making a temporary copy of the script and removing the features that had already been successfully activated). Note that the error only occurred in PROD (at least in the beginning) and therefore we didn't consider it a high priority to fix. Months went by and each time the solution was deployed to PROD, the workaround would be used whenever the error occurred. I thought about putting a simple hack in the code to sleep for 5 or 10 seconds (assuming the Web.config modifications would finish running in that amount of time), but I never implemented that hack since my preference was to fix the fundamental problem instead. This week, I had some time to tackle the problem so I modified my local development environment to more closely mimic PROD (i.e. by adding a second front-end Web server to the farm). Consequently I was able to reproduce t
O'Brien's Blog Dave Coleman's Blog Eric Shupp's Blog Glyn Clough's Blog Jaap Vosser's Blog Martin Hatch's Blog Paul Culmsee's Blog Seb Matthew's Blog Stephen Cummins Blog Stuart Starrs Blog The MOSS Show (Podcast) The SharePoint Podshow UK SharePoint User Group Wes Hackett's Blog Featured PowerShell: Getting Sandbox Solutions in a SharePoint WebApplication November 30, 2015December 21, 2015 by Simon Doy SharePoint 2013/Online Attachment ViewerEnhancement November 17, 2014January 22, 2016 https://blogs.msdn.microsoft.com/jjameson/2010/03/31/waiting-for-sharepoint-web-config-modifications-to-finish/ by Simon Doy Search Search for: Recent Posts Dev Diary S01E09: Implementing Azure Document Db and MVCWebAPI PowerShell: Script to Update SharePoint Content Type DocumentTemplate Use NPM and gulp build tasks to support Continuous Integration with VSTS and Azure for an AngularJSapp Dev Diary S01E08: Fleshing out the Angular and Azure Web https://blog.ithinksharepoint.com/2012/01/08/powershell-to-detect-web-configuration-modification-jobs/ APIcomponents Most Active Posts How we deployed SharePoint WSP Solutions without downtime PowerShell Script: Add user as Site Collection Admin to all sites in Web Application Open PDF files from a Document Library in a New Window Corrupted List Url Fix: Link to SharePoint List points to /_layouts/listedit.aspx?List=[ListGuid] PowerShell to Detect Web Configuration Modification jobs Tagsangular PowerShell SharePoint SharePoint 2010 SharePoint 2013Links Archive Archive Select Month May 2016 (10) April 2016 (1) December 2015 (1) November 2015 (1) August 2015 (1) November 2014 (1) June 2014 (3) May 2014 (1) February 2014 (1) November 2013 (2) October 2013 (1) September 2013 (1) August 2013 (1) April 2013 (1) March 2013 (1) February 2013 (1) July 2012 (4) June 2012 (3) January 2012 (1) December 2011 (1) November 2011 (1) October 2011 (2) September 2011 (1) August 2011 (1) July 2011 (1) June 2011 (2) May 2011 (3) April 2011 (3) March 2011 (1) Febru
alreadyrunning…. Posted on May 13, 2011 by Stephen Songer Ran into the above message when trying to activate a web application feature in https://stephensonger.wordpress.com/2011/05/13/a-web-configuration-modification-operation-is-already-running/ MOSS 2007. Looking at the Timer Job Status, I could see two jobs for "Windows SharePoint Services Web.Config Update" with success. Problem is we have three servers: one app server and two web front ends. Didn't see the success (nor a failure) job listing for the newest web front end. Found the error a answer on this thread: http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/5bb97bf7-d15b-4f56-a9a4-eedf95001042/ Simply restarted the SharePoint Administration and SharePoint Timer jobs on the problem web front end and then executed the "stsadm -o execadmsvcjobs" on that server and all was good. Share this:TwitterFacebookLinkedInEmailLike this:Like Loading... Related This entry was posted in SharePoint. Bookmark the permalink. ← SharePoint solution stuck in error a web RetractingStatus SQL Server Database stuck in "Restoring" state → Leave a Reply Cancel reply Enter your comment here... Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are commenting using your Facebook account. (LogOut/Change) You are commenting using your Google+ account. (LogOut/Change) Cancel Connecting to %s Notify me of new comments via email. AJAX ASP.NET C# iTextSharp JavaScript LINQ PDF Powershell SharePoint SQL SQL Server SSIS SSRS Testing Uncategorized Visual Studio Search for: Archives June 2012 February 2012 December 2011 November 2011 October 2011 August 2011 July 2011 June 2011 May 2011 April 2011 March 2011 February 2011 January 2011 October 2010 September 2010 June 2010 May 2010 April 2010 January 2010 June 2009 April 2009 March 2009 February 2009 January 2009 December 2008 October 2