SBS 08, Event ID 2436 Windows SharePoint Services 3 Search

Discussion in 'Windows Small Business Server' started by Leythos, Mar 29, 2009.

  1. Leythos

    Leythos Guest

    Interesting error. I've seen this reported all over the internet, but in
    testing, I have found that this didn't start until I installed the 20+
    updates for SBS 08 after the installation was already running for a
    couple days from the Action Pack DVD.

    I have another person that has the same issue, nothing seems to resolve
    this for anyone, unless you trash the services and assign them to new
    accounts - which should break SBS wizards if I understand the

    Anyone else running SBS 08 seeing Event ID 2436 in their Windows
    Application logs?

    Log Name: Application
    Source: Windows SharePoint Services 3 Search
    Date: 3/29/2009 4:20:05 PM
    Event ID: 2436
    Task Category: Gatherer
    Level: Warning
    Keywords: Classic
    User: N/A
    Computer: ZXZXZXSERVER.ZXZXZX.local
    The start address <sts3s://{d4078aab-
    ce82-4581-8d4f-973e1e6eac23}> cannot be crawled.

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

    Access is denied. Check that the Default Content Access Account
    has access to this content, or add a crawl rule to crawl this content.
    Event Xml:
    <Event xmlns="">
    <Provider Name="Windows SharePoint Services 3 Search" />
    <EventID Qualifiers="32768">2436</EventID>
    <TimeCreated SystemTime="2009-03-29T20:20:05.000Z" />
    <Security />

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

    Access is denied. Check that the Default Content Access Account
    has access to this content, or add a crawl rule to crawl this content.
    Leythos, Mar 29, 2009
    1. Advertisements

  2. It won't break any wizards.

    SharePoint Search uses two different accounts - one for the search service,
    and one to access the content in SharePoint sites. When configuring
    SharePoint search in Central Administration, SharePoint explicitly tells you
    that these two accounts cannot be built-in (e.g. Local Service / Network
    Service) accounts. By default, SBS *is* using built-in accounts for these
    two SharePoint search accounts.

    Creating two new standard user accounts and updating the SharePoint Search
    configuration will eliminate these errors. I reconfigured SharePoint search
    on my SBS 08 back in December - I haven't had any 2436 errors since then,
    and I haven't seen any adverse affects with the wizards either. And the
    wizards shouldn't care about these two accounts anyway.

    I'm guessing that the new image-based installation approach is part of the
    reason why the SBS team didn't configure SharePoint search properly. I'm
    drafting a blog post on optimizing SharePoint search in SBS 2008 which will
    include changing these accounts. Should be posted yet tonight.
    Chad A. Gross, Mar 30, 2009
    1. Advertisements

  3. Leythos

    Leythos Guest

    Can you give me a generic step-by-step to do this, if it won't take more
    than a couple minutes of your time?

    Leythos, Mar 30, 2009
  4. Chad A. Gross, Mar 30, 2009
  5. Leythos

    Leythos Guest

    Leythos, Mar 30, 2009
  6. Leythos

    Leythos Guest

    On a new install, before doing any updates, using the dvd that was
    shipped with my AP subscription, I didn't see that event ID error once,
    not that I can tell, and I was looking for it.

    After running the 24 updates I started getting it.
    Leythos, Mar 30, 2009
  7. UPDATE -

    OK guys - I missed a step in the blog post, which explains the error that
    Duder encountered. My bad for doing a quick post from notes and not testing
    the process. Short story is that I used the notes on configuring SharePoint
    search on a clean SharePoint install (not on SBS 08). The difference
    between that scenario and the SBS 08 scenario is that SharePoint Search is
    previously configured on SBS, where it has not yet been configured on a
    clean install. I have updated the blog post to include stopping the
    SharePoint search service before changing the configuration.
    Chad A. Gross, Mar 30, 2009
  8. Leythos

    Leythos Guest

    I followed the directions and still get error ID 2436 every 5 minutes.

    Double checked all settings, got no errors, and yet the beast persists.
    Leythos, Mar 30, 2009
  9. Leythos

    Leythos Guest

    I'm seeing Security Event ID: 4625 Logon Audit Failure for

    An account failed to log on.

    Subject: Security ID: SYSTEM

    ProcessName C:\Program Files\Microsoft\Exchange Server\Bin

    After following the changes at the blog.
    Leythos, Mar 30, 2009
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.