Sign in
 
HomeWindows 8Windows 7Windows VistaWindows XPMDOPWindows IntuneLibraryForums
Windows Client >
> 
> 
Gatherer Error Event ID 3036

الإجابة Gatherer Error Event ID 3036

  • Monday, June 28, 2010 5:39 PM
     
     
    Sign In to Vote
    0

    On a Latitude E6410 Laptop running Windows 7 x64 Enterprise with Office 2010 x32 installed the following errors are being produced as warnings:

    Source: Search
    Content source: <SharePointWorkspaceSearch://{S-1-5-21-1934113286-1215789848-953900138-22874}/> cannot be accessed
    Context: Application, SystemIndex Catalog
    Event ID: 3036
    Level: Warning
    Task Category: Gatherer
    Details: A server error occured. Check that the server is available. (HRESULT : 0x80041206) (0x80041206)

    Source: Search
    Content source: <ONEINDEX14://{s-1-5-21-1934113286-1215789848-953900138-22874}/> Cannot be accessed.
    Context: Application, SystemIndex Catalog
    Event ID: 3036
    Level: Warning
    Task Category: Gatherer
    Details: (HPRESULT:0x80004005) (0x80004005)

    Source: Search
    Content Source: <csc://{S-1-5-21-2194601408-1245679439-3179337323-1000}/> cannot be accessed
    Context: Application, SystemIndex Catalog
    Event ID: 3036
    Level: Warning
    Task Category: Gatherer
    Details: (HRESULT:0x80004005) (0x80004005)

    The errors are produced at times when there was no one using the machine as well ex. 04:08:07 AM.

    It might also be important to note that before everything was reinstalled on the machine Outlook 2010 was having a gatherer error that would crash the program on searches.

     

     

All Replies

  • Tuesday, June 29, 2010 3:35 AM
    Moderator
     
     
    Sign In to Vote
    2

     

    Hello,

     

    Based on my research, the issue can be caused by Windows Index feature. Please refer to the following steps to rebuild index database:

     

    1. Click on the Start Button, type "Indexing Options" (without quotation marks) in the Start Search box and press Enter.

    2. In the "Index these locations" section, remove all the Internet Explorer History items. Click the "Advanced" button.

    3. Click on the "Index Settings" tab.

    4. Under Troubleshooting, click the "Rebuild" button.

     

    Meanwhile, I would like to explain that regarding the warning logs, they are just internal status which will not affect the system. You can just ignore them.

     

    Thanks,

    Novak

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked As Answer by Novak WuModerator Monday, July 05, 2010 1:40 AM
    • Unmarked As Answer by Dave Grina Wednesday, July 07, 2010 11:48 PM
    •  
     
  • Wednesday, July 07, 2010 11:51 PM
     
     
    Sign In to Vote
    0
    Actually, repairing the index in IE History only created error messages on the machine that did not exist before. In fact, the number of warnings has doubled since running the index repair. They do not seem to be causing problems as warnings but they are not on any other machines that we have (to our knowledge). I hope to get them fixed at some point but it has become difficult as the computer was sent out to a user.  
     
  • Friday, July 16, 2010 7:36 PM
     
     Answered
    Sign In to Vote
    0
    In regards to the Gatherer warnings we believe that the indexing that is causing these warnings is directly linked to Outlook 2010 crashed (http://social.technet.microsoft.com/Forums/en-US/officesetupdeploy/thread/826e13af-785f-48e1-8fee-e2be25d43361 ). Upon testing we have made an assumption that when indexing is enabled on archive files it causes Outlook to crash. Only after Indexing is disabled is Outlook workable with archives. Our main reason for this is many gatherer warnings that have been directly linked to indexing.
    • Proposed As Answer by Dukies Monday, December 12, 2011 9:35 AM
    • Marked As Answer by Dave Grina Friday, December 23, 2011 9:59 PM
    •  
     
  • Monday, February 27, 2012 9:11 AM
     
     
    Sign In to Vote
    0

    This happens on XP (SP3+) systems also.  The problem of poor recovery is inherent in the Search gatherer/indexer, but that is the symptom.  The cause of the corruption is IE8/Bing Bar.  This looks like an amazingly old bug finding its way back into much newer systems and programs.  See Q296136, circa 2007 discussion about a bug that goes way back to the 2K days.  I think this is the same bug.  XP systems recently became able to use Windows Search and IE8 and Bing Bar, and I too was bit by this old bug.  My uncommanded system shutdowns seem to have been triggered initially by BB in IE8 attempting to post into Outlook Express, a mail client I don't use and have not configured.  According to Q296136, this bug can arise with access to any MailStore when the access fails at an inopportune moment (I was creating a System checkpoint at the moment, what a coincidence!).  Windows Search is just responding to a perceived corruption in the SystemIndex catalog.  Too bad it fails miserably, and it took a checkpoint restore and several shutdown cycles before it self-repaired the catalog.  Application Event log messages on my Windows XP Pro SP3+ system:

    Event Type:    Warning
    Event Source:    Windows Search Service
    Event Category:    Gatherer
    Event ID:    3036
    Date:        2/26/2012
    Time:        7:02:43 PM
    User:        N/A
    Computer:    JERRY_XP
    Description:
    The content source <outlookexpress://{s-1-5-21-1606980848-1972579041-839522115-1004}/{614de238-f5cb-48f9-94a6-4f387f1d2a93}/> cannot be accessed.

    Context:  Application, SystemIndex Catalog

    Details:
         (0x81270005)


    Event Type:    Information
    Event Source:    Windows Search Service
    Event Category:    Search service
    Event ID:    1005
    Date:        2/26/2012
    Time:        6:50:52 PM
    User:        N/A
    Computer:    JERRY_XP
    Description:
    The Windows Search Service has successfully created the SystemIndex search index.


    Event Type:    Error
    Event Source:    Windows Search Service
    Event Category:    Gatherer
    Event ID:    3029
    Date:        2/26/2012
    Time:        6:41:26 PM
    User:        N/A
    Computer:    JERRY_XP
    Description:
    The plug-in in <Search.TripoliIndexer> cannot be initialized.

    Context: Windows Application, SystemIndex Catalog

    Details:
        The content index cannot be read.   (0xc0041800)


    Event Type:    Error
    Event Source:    Windows Search Service
    Event Category:    Search service
    Event ID:    7040
    Date:        2/26/2012
    Time:        6:41:20 PM
    User:        N/A
    Computer:    JERRY_XP
    Description:
    The search service has detected corrupted data files in the index. The service will attempt to automatically correct this problem by rebuilding the index.

    Context: Windows Application, SystemIndex Catalog

    Details:
         0xc0041801 (0xc0041801)

     
  • Monday, June 11, 2012 2:45 PM
     
     
    Sign In to Vote
    0

    Happens on Windows 7 (32-bit, SP1, Professional) also:

    The content source <ONEINDEX14://{S-1-5-21-7605713-289287414-413607797-18519}/> cannot be accessed.

    Context:  Application, SystemIndex Catalog

    Details:
        (HRESULT : 0x80004005) (0x80004005)

    [Event 3036]

    - System
    - Provider
    [ Name] Microsoft-Windows-Search
    [ Guid] {CA4E628D-8567-4896-AB6B-835B221F373F}
    [ EventSourceName] Windows Search Service
    - EventID 3036
    [ Qualifiers] 32768
    Version 0
    Level 3
    Task 3
    Opcode 0
    Keywords 0x80000000000000
    - TimeCreated
    [ SystemTime] 2012-06-11T12:25:55.000000000Z
    EventRecordID 4788
    Correlation
    - Execution
    [ ProcessID] 0
    [ ThreadID] 0
    Channel Application
    Computer                       my-computer
    Security
    - EventData
    ExtraInfo Context: Application, SystemIndex Catalog Details: (HRESULT : 0x80004005) (0x80004005)
    URL ONEINDEX14://{S-1-5-21-7605713-289287414-413607797-18519}/

    tnjman

     
  • Wednesday, April 03, 2013 1:43 PM
     
     
    Sign In to Vote
    0

    This also occurs on Windows 7 machines (32 and 64 bit). Office 2007 Pro is installed but not Outlook 2007.