Код события 3036 для службы windows search

Context: Application, SystemIndex Catalog

(HRESULT : 0x80004005) (0x80004005)

Log Name: Application

Date: 8/2/2010 3:00:51 AM

Task Category: Gatherer

The content source cannot be accessed.

Context: Application, SystemIndex Catalog

(HRESULT : 0x80004005) (0x80004005)

Context: Application, SystemIndex Catalog

(HRESULT : 0x80004005) (0x80004005)

Log Name: Application

Date: 8/2/2010 6:32:07 AM

Task Category: Gatherer

The content source cannot be accessed.

Context: Application, SystemIndex Catalog

(HRESULT : 0x80004005) (0x80004005)

Context: Application, SystemIndex Catalog

(HRESULT : 0x80004005) (0x80004005)

All replies

• Proposed as answer by Naresh Negi Microsoft employee Monday, October 17, 2011 1:27 AM

So, my limited understanding is that this is an issue betwixt the Indexer and Offline files, and perhaps something else. What I would like to do is be able to Modify all the indexed locations. I know it says you can, but on some machines there is no way I can remove certain objects. This error occurs on almost all of our x64 workstations, XP and 7.

I can get rid of the csc errors if I disable indexing of offline files entirely. I still cannot get rid of the mapi errors. On most machines, other users/profiles have exchange OSTs that are being indexed so they are protected. I’ve even tried picking through the registry and removing search roots attached to the offending SID(s) but to no avail. Upon reboot and a forced re-index (which is how I can reproduce these warnings) the same offending SIDs show up with either csc or mapi errors.

Ok, I’ve get rid off error 3036, I’ve used Method 1 and it’s worked

Method 1: Restore Index to its original settings

Here’s how:
a. Go to Start > Control Panel.
b. Double click on the Indexing Options.
c. Click on the Advanced button.
d. Click on on Restore Defaults.

Method 2: Rebuild index from registry

You can rebuild the searcher index manually by editing the following registry key: HKLM/Software/Microsoft/Windows Search/SetupCompletedSuccessfully

Important: This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the windows help article below.

Follow these steps to rebuild the index.

a. Go to start, type “regedit” without the quotes and press Enter.
b. Navigate to the registry branch HKLM/Software/Microsoft/Windows Search.
c. Right-click on “Windows Search” and choose Permissions. On the Security tab, verify that Administrator is the owner and has full control of the key.
d. Within the «Windows Search» registry key, find the SetupCompletedSuccessfully value on the right pane.
e. Double-click SetupCompletedSuccessfully and change its value to 0.

Restart the computer once this is done. Check if indexing works.

Код события 3036 для службы windows search

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

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: 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: Cannot be accessed.
Context: Application, SystemIndex Catalog
Event ID: 3036
Level: Warning
Task Category: Gatherer
Details: (HPRESULT:0x80004005) (0x80004005)

Source: Search
Content Source: 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.

• Moved by Carey Frisch MVP Tuesday, June 29, 2010 2:19 AM Moved to relevant forum (From:Windows 7 Miscellaneous)

Answers

All replies

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.

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. ”

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 cannot be accessed.

Context: Application, SystemIndex Catalog

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 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

Что делать, если служба WSearch не запускается из-за отказа в доступе

Скорость поиска файлов и папок в Windows 10 можно существенно увеличить, если включить индексирование. Однако через некоторое время после этого обнаруживаешь, что индексирование не работает, а его включение ни к чему не приводит. Вернее, приводит оно к появлению в журнале событий ошибки с кодом 700 и описанием «Сбой при запуске службы Windows Search. Отказано в доступе» .

Пытаешься исправить неполадку, инициировав запуск службы вручную, но и здесь терпишь фиаско.

Любая попытка ее запустить заканчивается ошибкой отказа в доступе с кодом 5.

Что делать в таком случае и в чём может быть причина ошибки? Чаще всего с подобной неполадкой приходится сталкиваться либо вследствие изменения прав доступа к исполняемому файлу службы SearchIndexer.exe , либо его повреждению.

Исключить последнее можно выполнив в запущенной с повышенными правами команду sfc /VERIFYFILE=C:\Windows\System32\SearchIndexer.exe . Если целостность файла не нарушена, откройте его свойства на вкладке «Безопасность» и посмотрите разрешения. По умолчанию для всех групп и пользователей кроме TrustedInstaller для файла должны быть установлены права на чтение и выполнение. Объект TrustedInstaller как владелец должен иметь полные права на файл. Попробуйте выставить разрешения для файла SearchIndexer.exe так, как показано на скриншоте.

Если изменить разрешения не удается (система не позволяет этого сделать) , поступаем следующим образом. Копируем файл SearchIndexer.exe с другого компьютера с той же версией системы и переносим его в произвольную папку на ПК с неработающей службой. Пусть для примера это будет папка Data в корне диска C.

Затем открываем редактор реестра, разворачиваем указанную на скриншоте ветку и заменяем значение-путь в параметре ImagePath путем к «новому» исполняемому файлу SearchIndexer.exe в папке Data .

Теперь попробуйте запустить службу Windows Search из оснастки управления службами. На этот раз служба должна запуститься без ошибок.

Event 3036, Search The content source…cannot be accessed (Solved)

A Windows 7 machine becomes un-responsible after a while and the following error is displayed on Event Viewer’s Application log:
«Event 3036, Search.
The content source cannot be accessed.
Context: Application, SystemIndex Catalog
Details: (HRESULT : 0x80004005) (0x80004005)».

The Event 3036 error, is related to Windows Search service and specifically to Windows Index feature. The «csc» in event details means «Client Side Caching» and is occurred if the indexing of Offline Files is enabled.

How to resolve the «Event 3036, Search ‘The content source cannot be accessed’ error in Event log.

To fix the Event ID 3036 error(s), first try to repair Windows Desktop Search problems using the Microsoft FixIt tool. If after running the tool you still receive the error, then exclude Offline Files from Indexing and then rebuild the Index. To do that:

1. Open Windows Control Panel.

2. Double click to open Indexing Options.

3. Click Modify.

4. Uncheck Offline Files* and press OK.

* Optional uncheck and the Internet Explorer History checkbox.

5. Then click Advanced.

6. At Troubleshooting section, click the Rebuild button.

7. Press OK to rebuild the Index.

8. Wait until the index rebuilding is completed and then close Indexing options.

9. Restart you computer and check if you still receive the «Event 3036» warning message in Event Log.

That’s all folks! Did it work for you?

Please leave a comment in the comment section below or even better: like and share this blog post in the social networks to help spread the word about this solution.

5 Comments

Bill Westrup
March 24, 2017 @ 7:53 pm

No. This did not help. Fixit from Microsoft is no longer available.

Lakonst2013
March 25, 2017 @ 11:29 am

Bill Westrup: Have you tried to rebuild the Index or not?

glnz
April 16, 2017 @ 11:27 pm

Bill Westrup – did you rebuild?

Daniel Swan
May 12, 2017 @ 9:38 pm

Graham JONES
April 13, 2020 @ 2:15 pm

Followed your instructions to rebuild and I no longer have the Event 3036 error. Thanks ! 🙂