"An update conflict has occurred, and you must re-try this action. The object SPWebApplication Name=SharePoint – WebApp80 Parent=SPWebService is being updated by DOMAIN\Account, in the OWSTIMER process, on machine SERVER. 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.SPWebApplication.Update() at Microsoft.SharePoint.ApplicationPages.PolicyUserPage.BtnFinish_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.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)"
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:
- Stop the Timer service. To do this, follow these steps:
a. Click Start, point to Administrative Tools, and then click Services.
b. Right-click Windows SharePoint Services Timer, and then click Stop.
c. Close the Services console.
- On the computer that is running Microsoft Office SharePoint Server 2007 and on which the Central Administration site is hosted, click Start, click Run, type explorer, and then press ENTER.
- In Windows Explorer, locate and then double-click the following folder: Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\GUIDNotes o The Drive placeholder specifies the letter of the drive on which Windows is installed. By default, Windows is installed on drive C. o The GUID placeholder specifies the GUID folder. o The Application Data folder may be hidden. To view the hidden folder, follow these steps:
1. On the Tools menu, click Folder Options.
2. Click the View tab.
3. In the Advanced settings list, click Show hidden files and folders under Hidden files and folders, and then click OK.o In Windows Server 2008, the configuration cache is in the following location: Drive:\ProgramData\Microsoft\SharePoint\Config\GUID
- Back up the Cache.ini file.
- Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt.
Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.
- Double-click the Cache.ini file.
- On the Edit menu, click Select All.
- On the Edit menu, click Delete.
- Type 1, and then click Save on the File menu.
- On the File menu, click Exit.
- Start the Timer service. To do this, follow these steps: .
Click Start, point to Administrative Tools, and then click Services.
a. Right-click Windows SharePoint Services Timer, and then click Start.
b. Close the Services console. Note The 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.
- Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.
- Click Start, point to Programs, point to Administrative Tools, and then click SharePoint 3.0 Central Administration.
- Click the Operations tab, and then click Timer job status under Global Configuration.
- In the list of timer jobs, verify that the status of the Config Refresh entry is Succeeded. This may show “Aborted” as the status. Ignore this and check in 10 mins (you can tell if the process has completed successfully on each server that displays “aborted” by the CPU utilization (when the timer job is reconfiguring the CPU will be at 100%).
- On the File menu, click Close.
You still may run into this error when deleting the web applicaton that has no content database (DBA accidently deleted it). Just deselect the "delete database" option in the Central Admin when deleting the database and you should be able to remove the web application.