This message was deleted.

wow, still having this issue. what happens when FSL stops? does the user's session crash or something?

The indexing should stop for all search functions turning it into pure sh!t.

I often wonder if Azure is having these issues or if they run a special build?

Yea same thing happens to me. But im two versions behind. My Verison, which Tim was on as well in post weeks ago. Was when it was pointed out. We have a Citrix discussion on it as well. The fix was in the latest release or supposed to be. Anyways, any outlook, onenote searches. Stop windows search, then disables it. I have control up catching it and re-enabling it. Then starting it. However, i dont know if it screws up the search db during a session that is in use. I have yet to actually look.

not me, tim is on that thread though

Sorry man, i meant on slack.

It's the search service which stops - sorry for the confusion. @Nick Casagrande is correct - it doesn't stop the user from working, and it is REALLY annoying.

ah ok, so only search stops.

Correct

New update to the Windows Search Service being stopped and disabled. If I do not open OneNote, it stays running. As soon as I open OneNote, it becomes disabled (the Windows Search Service, that is). We separate Outlook data and profile data, and have the OneNote data included in the ODFC.

Same deal here. Same exact issue.

I rolled back 2 versions, zero issues.

I'm still 2 version behind as well. Once Tim said something about onenote. I was like, yep same deal.

Don’t upgrade!

Ok, still issues on the latest build?

Yes for me, search service and the ost kept saying the mailbox moved.

If we go back 2 versions, that breaks Cloud Cache (locking), which is a BIG DEAL (tm). As OneNote isn't officially rolled out, and only minimally used, I can head this off until MS gets their act together (again).

Might have same issue, is there a DL for all builds, or at least an overview so I know what is 2 versions behind ;-)

I think we settled in 7117 the rest are crap.

Not sure 7117 stops the issue. I've come across a RDS 2016 server this morning with the service disabled and it's running 2.9.7117.27413. I'll be reviewing the event log shortly.

@Eric two versions back is the 2.9.7117 version, which has problems with locking with Cloud Cache. I believe we also experienced the Search service being disabled with that version. I can't figure out how to get a Premier support case (no SA) for FSLogix, though. Anyone want to open one and keep us posted?

All done via email, although I have spoken to an engineer before via Teams call.

Same issue, but WSSearch is not stopped in our case. Policy «Store search database in Office 365 Container» is enable and Search & ODFC logs looks clean. T/S is PITA

Eric: are you also running OneNote in the environment? We find that causes problems...

Yes OneNote 2016 is #1 suspect, These issues start around that time frame when it was installed, but Search service doesn’t stop like yours. Problem is CFO wants both ;-)

I might have to log a case been fighting ramdom bsod on 2016 vda. Setup a memory dump, only thing we see minidump is frx.sys file freaking out. Them server crashes. As why i asked earlier if any problems on the new hotfix.

@Eric - no, not normal. Those are not grayed out in our environment. However, my search index constantly keeps rebuilding. Hurray!