Lately, we have been getting a lot of errors on our content deployment jobs.  The error that the jobs seem to have in common is “An update conflict has occurred, and you must re-try this action”.

I followed this Microsoft KB Article to resolve the issue: Error message when you try to modify or to delete an alternate access mapping in Windows SharePoint Services 3.0: "An update conflict has occurred, and you must re-try this action" – 939308

!!!*** NEVER, NEVER, NEVER, NEVER EVER STOP WINDOWS SHAREPOINT SERVICES WEB APPLICATION ***!!!

The Windows SharePoint Services Web Application is what identifies your server as a SharePoint Web Front-End.  If you stop this “service” it will remove all SharePoint websites and the directories from which they are served. 

So, unless you know exactly what you are doing, DO NOT STOP THE WINDOWS SHAREPOINT SERVICES WEB APPLICATION!!!

I installed a Windows SharePoint Services (WSS) Web Front End (WFE) onto an external server to be used for the External Collaboration Tool-Kit.

Once I got it installed I ran the SharePoint Products & Technologies Configuration Wizard and received the following error:

Failed to register SharePoint services.

The log pointed to several different registry keys located at HKEY_LOCAL_MACHINESOFTWAREMicrosoftShared ToolsWeb Server Extensions12.0WSSServices.

I deleted everything under that location and it completed successfully.

One day, we noticed that our search was not working.   Well really, one of the applications managers noticed that it wasn’t working.  Anyway, we found the following errors in the event viewer on our SharePoint 2007 Server:

Event Type:      Warning
Event Source:      Windows SharePoint Services 3 Search
Event Category:      Gatherer
Event ID:      2436
Date:            4/11/2009
Time:            11:45:02 PM
User:            N/A
Computer:      <servername>
Description:
The start address <{somesite}> cannot be crawled.

Context: Application ‘Search index file on the search server’, Catalog ‘Search’

Details:
Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content.   (0×80041205)

Apparently, this error was caused by a recent Microsoft Windows Update that was installed that affected the "Loopback Check" in order to make the system more secure.

In order for the SharePoint Search Services to work we needed to add the following registry entry with a REG_DWORD value of 0×00000001 (1):

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLsaDisableLoopbackCheck

Have you ran into this issue or one like it?