Служба windows search была неожиданно завершена

A number of users with laptops have reported that searches in Outlook either don’t work or are incomplete.  All of these users are using Outlook in cached mode, and almost all of them were imaged recently.  I got my hands on one of these machines
and discovered that the Windows Search service seems to tank randomly.  The ‘SearchIndexer.exe’ process seems to crash also.  It appears to be an issue with the machines as a whole versus the profile since I encountered the same problem when
I logged on as myself.  (This was the first time I logged onto this machine.)  On Friday I logged on as myself for the first time, build the OST & left it on over the weekend to index.  I checked the machine this morning and found the System
event log full of errors :

• The Windows Search service terminated unexpectedly.  It has done this 5785 time(s). (Event ID: 7034; Source: Service Control Manager; OpCode: Info)
• The Windows Search service entered the running state.
• Wash, Rinse & Repeat (more details below)

I went through the following to no avail:

• Logged in as a new user — Problem persists.
• Ran through the
  Search & Indexer Troubleshooter.  Other than it being ‘aware’ that the service failed recently and that the service not running it found nothing wrong.  When I started the service & ran the troubleshooter again, it mentioned that the service
  had failed recently but that’s all.
• Explorered
  numerous potential options here to no avail.
• Tried Microsoft’s ‘fix it’ as well
• Set
  ‘HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search\SetupCompletedSuccessfully‘ from 1 to 0
• Rebuilt the index

Every time it gets up to a point (like 27kish) then breaks and starts the stop/start service process again.  Its hard to say what its choking on since I’m not aware of a way to ‘parse’ the mail file or enable super-verbose logging to see what its
having trouble with.

The only indexed locations are ‘Offline Files’ for my user, and ‘Microsoft Office Outlook’ for my user as well.  We’re not indexing any drives, libraries or network locations, even via the symlink ‘hack’.  This is a new profile so there’s not much
else here in terms of files to index.

At the same time of setting up the ‘problematic’ machine on Friday, I imaged & logged into 3 laptops as myself to build and index the OST.  All three machines finished indexing over 57k items without a problem, and there are no issues in the
Application or System event logs.

This is Windows 7 with just about every update available prior to the release of SP1 and Office Enterprise 2007 with SP2.  (Outlook 12.0.6539.5000 SP2 MSO 12.0.6535.5002)

Short messing around with the ‘Indexing Service’ (the Windows Feature), uninstalling/reinstalling WDS reimaging this machine, I don’t know what else to try.

——————————

APPLICATION LOG
Outlook Search has encountered an error and is temporarily disabling indexing for store C:\Users\jgp2750\AppData\Local\Microsoft\Outlook\outlook.ost (error=0x800706ba).
— <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
— <System>
  <Provider Name=»Outlook» />
  <EventID Qualifiers=»32768″>36</EventID>
  <Level>3</Level>
  <Task>0</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime=»2011-04-18T14:32:45.000000000Z» />
  <EventRecordID>218711</EventRecordID>
  <Channel>Application</Channel>
  <Computer>FQDN</Computer>
  <Security />
  </System>
— <EventData>
  <Data>C:\Users\jgp2750\AppData\Local\Microsoft\Outlook\outlook.ost</Data>

  <Data>0x800706ba</Data>
  </EventData>
  </Event>

Faulting application name: SearchIndexer.exe, version: 7.0.7600.16385, time stamp: 0x4a5bcdd0
Faulting module name: NLSData0001.dll, version: 6.1.7600.16385, time stamp: 0x4a5bda85
Exception code: 0xc0000005
Fault offset: 0x00260a0d
Faulting process id: 0xb38
Faulting application start time: 0x01cbfdd577062774
Faulting application path: C:\Windows\system32\SearchIndexer.exe
Faulting module path: C:\Windows\System32\NLSData0001.dll
Report Id: b967dd6d-69c8-11e0-99bd-0024d60226ee
— <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
— <System>
  <Provider Name=»Application Error» />
  <EventID Qualifiers=»0″>1000</EventID>
  <Level>2</Level>
  <Task>100</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime=»2011-04-18T14:32:45.000000000Z» />
  <EventRecordID>218710</EventRecordID>
  <Channel>Application</Channel>
  <Computer>FQDN</Computer>
  <Security />
  </System>
— <EventData>
  <Data>SearchIndexer.exe</Data>
  <Data>7.0.7600.16385</Data>
  <Data>4a5bcdd0</Data>
  <Data>NLSData0001.dll</Data>
  <Data>6.1.7600.16385</Data>
  <Data>4a5bda85</Data>
  <Data>c0000005</Data>
  <Data>00260a0d</Data>
  <Data>b38</Data>
  <Data>01cbfdd577062774</Data>
  <Data>C:\Windows\system32\SearchIndexer.exe</Data>
  <Data>C:\Windows\System32\NLSData0001.dll</Data>
  <Data>b967dd6d-69c8-11e0-99bd-0024d60226ee</Data>
  </EventData>
  </Event>

Faulting application name: SearchIndexer.exe, version: 7.0.7600.16385, time stamp: 0x4a5bcdd0
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000004c
Faulting process id: 0x10c8
Faulting application start time: 0x01cbfdd546f303ec
Faulting application path: C:\Windows\system32\SearchIndexer.exe
Faulting module path: unknown
Report Id: 87c5842d-69c8-11e0-99bd-0024d60226ee
— <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
— <System>
  <Provider Name=»Application Error» />
  <EventID Qualifiers=»0″>1000</EventID>
  <Level>2</Level>
  <Task>100</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime=»2011-04-18T14:31:22.000000000Z» />
  <EventRecordID>218698</EventRecordID>
  <Channel>Application</Channel>
  <Computer>FQDN</Computer>
  <Security />
  </System>
— <EventData>
  <Data>SearchIndexer.exe</Data>
  <Data>7.0.7600.16385</Data>
  <Data>4a5bcdd0</Data>
  <Data>unknown</Data>
  <Data>0.0.0.0</Data>
  <Data>00000000</Data>
  <Data>c0000005</Data>
  <Data>0000004c</Data>
  <Data>10c8</Data>
  <Data>01cbfdd546f303ec</Data>
  <Data>C:\Windows\system32\SearchIndexer.exe</Data>
  <Data>unknown</Data>
  <Data>87c5842d-69c8-11e0-99bd-0024d60226ee</Data>
  </EventData>
  </Event>

SYSTEM LOG
The Windows Search service terminated unexpectedly.  It has done this 5831 time(s).
— <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
— <System>
  <Provider Name=»Service Control Manager» Guid=»{555908d1-a6d7-4695-8e1e-26931d2012f4}» EventSourceName=»Service Control Manager» />

  <EventID Qualifiers=»49152″>7034</EventID>
  <Version>0</Version>
  <Level>2</Level>
  <Task>0</Task>
  <Opcode>0</Opcode>
  <Keywords>0x8080000000000000</Keywords>
  <TimeCreated SystemTime=»2011-04-18T14:34:52.973976600Z» />
  <EventRecordID>74749</EventRecordID>
  <Correlation />
  <Execution ProcessID=»520″ ThreadID=»4604″ />
  <Channel>System</Channel>
  <Computer>FQDN</Computer>
  <Security />
  </System>
— <EventData>
  <Data Name=»param1″>Windows Search</Data>
  <Data Name=»param2″>5831</Data>
  </EventData>
  </Event>

The Windows Search service entered the running state.
— <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
— <System>
  <Provider Name=»Service Control Manager» Guid=»{555908d1-a6d7-4695-8e1e-26931d2012f4}» EventSourceName=»Service Control Manager» />

  <EventID Qualifiers=»16384″>7036</EventID>
  <Version>0</Version>
  <Level>4</Level>
  <Task>0</Task>
  <Opcode>0</Opcode>
  <Keywords>0x8080000000000000</Keywords>
  <TimeCreated SystemTime=»2011-04-18T14:35:30.537732600Z» />
  <EventRecordID>74750</EventRecordID>
  <Correlation />
  <Execution ProcessID=»520″ ThreadID=»1364″ />
  <Channel>System</Channel>
  <Computer>FQDN</Computer>
  <Security />
  </System>
— <EventData>
  <Data Name=»param1″>Windows Search</Data>
  <Data Name=»param2″>running</Data>
  <Binary>57005300650061007200630068002F0034000000</Binary>
  </EventData>
  </Event>

• Changed type

  Friday, April 29, 2011 10:15 AM

• Edited by
  JuliusPIV
  Monday, May 9, 2011 9:02 PM
• Changed type
  JuliusPIV
  Friday, March 30, 2012 4:54 PM

• Remove From My Forums

• Вопрос

• После обновления Windows Server 2012 R2 до Windows Server 2019 не запускается служба Windows Search.

  Пробовал удалять и заново устанавливать компонент Windows Search, проработало несколько дней, и снова начались ошибки. Служба стартует и автоматически останавливается, в логах:

  Служба «Windows Search» перешла в состояние Работает.

  Код 7036

  Служба «Windows Search» перешла в состояние Остановлена.

  Код 7036

  Служба «Windows Search» завершена из-за ошибки 
  Не удается найти указанный файл.

  Код 7023

  - System 
  
    - Provider 
  
     [ Name]  Service Control Manager 
     [ Guid]  {555908d1-a6d7-4695-8e1e-26931d2012f4} 
     [ EventSourceName]  Service Control Manager 
   
    - EventID 7023 
  
     [ Qualifiers]  49152 
   
     Version 0 
   
     Level 2 
   
     Task 0 
   
     Opcode 0 
   
     Keywords 0x8080000000000000 
   
    - TimeCreated 
  
     [ SystemTime]  2019-12-16T07:26:50.543445500Z 
   
     EventRecordID 97369 
   
     Correlation 
   
    - Execution 
  
     [ ProcessID]  824 
     [ ThreadID]  74372 
   
     Channel System 
   
     Computer 123
   
     Security 
   
  
  - EventData 
  
    param1 Windows Search 
    param2 %%2 
     57005300650061007200630068000000 
  

  Служба «Windows Search» неожиданно прервана. Это произошло (раз): 57.

  Код 7034

   System 
  
    - Provider 
  
     [ Name]  Service Control Manager 
     [ Guid]  {555908d1-a6d7-4695-8e1e-26931d2012f4} 
     [ EventSourceName]  Service Control Manager 
   
    - EventID 7034 
  
     [ Qualifiers]  49152 
   
     Version 0 
   
     Level 2 
   
     Task 0 
   
     Opcode 0 
   
     Keywords 0x8080000000000000 
   
    - TimeCreated 
  
     [ SystemTime]  2019-12-16T07:26:50.543445500Z 
   
     EventRecordID 97370 
   
     Correlation 
   
    - Execution 
  
     [ ProcessID]  824 
     [ ThreadID]  29864 
   
     Channel System 
   
     Computer 123
   
     Security 
   
  
  - EventData 
  
    param1 Windows Search 
    param2 57 
     57005300650061007200630068000000