Jaa

SharePoint Services 3 Search event errors after an SBS 2008 Update Rollup

  • Artikkeli

[Today's post comes to us courtesy of Damian Leibaschoff]

After installing an SBS 2008 Update Rollup (2 or higher) you might see the following event in the application event log happening very 5 to 10 minutes:

Log Name: Application
Source: Windows SharePoint Services 3 Search
Date: 8/5/2009 10:10:02 AM
Event ID: 2424
Task Category: Gatherer
Level: Error
Keywords: Classic
User: N/A
Computer: SBS01.wingtiptoys.local
Description:
The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.
Context: Application 'Search', Catalog 'index file on the search server Search'

New content will not be added to the search index and in consequence it will not be found when doing a full text search within the CompanyWeb application.

In order to resolve this issue, please follow the same resolution presented in this blog post, you will need to add the host name that you created using the Internet Address Management Wizard for public access, it will usually be in the form “Remote.Contoso.com”, If you are not sure on what URL to use, you can look for the event id 2436 as mentioned on the other blog post or you can do the following:

  • Open an elevated command prompt by right-clicking on Command Prompt and choosing ‘Run as administrator’
  • Navigate to the following folder:
    • CD C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12BIN
  • Type the following command:
    • stsadm -o enumzoneurls
  • The output will look like this:

<ZoneUrls>
  <Collection Name="Central Administration">
     <Default>https://sbs01:4721</Default>
  </Collection>
  <Collection Name="SBS SharePoint">
     <Default>https://remote.Contoso.com:987</Default>
     <Intranet>https://companyweb</Intranet>
  </Collection>
</ZoneUrls>

  • From this output, you are looking for the URL in the <DEFAULT> tags under the “SBS SharePoint” collection. You will only use the host.domain name portion and not the protocol or port, so, “Remote.Contoso.com” is what you are looking for to be added to the registry.

Articles referenced:   
https://blogs.technet.com/sbs/archive/2009/05/07/event-2436-for-sharepoint-services-3-search.aspx

Comments

  • Anonymous
    August 10, 2009
    I still get 2424 erros on all my customers' SBS2008 servers a few times per day rather than every 5 to 10 minutes with the fix.

  • Anonymous
    August 18, 2009
    Continuing: I tried the fix suggested but it did not help of fix the issue which is reflected in the companyweb page. I also noted that the port access is no longer 987 - sorry I am not at home and cannot give the new port address. SharePoint does not appear to be running even with all share point services functioning normally. Neither the server nor the clients can access the company web and other SharePoint functions are not running. So, though I am not dead in the water my SBS2008 is dead in the water. Suggestions, fixes, resolutions are welcome here.

  • Anonymous
    December 02, 2015
    The comment has been removed