Eventlog warnings ; ESENT id=642

csmdew · 04 Jun 2020

How can u clear/repair/block the event involved with SRUJet ID 642.

OK got this one stopped but now have: Unistore: The database format feature version 9120 (0x23a0) could not be used due to the current database format 1568.20.0, controlled by the parameter, and Catalog Database: The database format feature version 9080 (0x2378) could not be used due to the current database format 1568.20.0, controlled by the parameter, same 642 events.

Well SRUJet event is back, had stopped for 1 day but now that's the only one to show up in last 24 hrs.

Zardoc · 06 Jun 2020

Shanedh65 said:

Update Microsoft edge has resulted in only having 2 warnings at startup.

The double warnings on startup have always been there. Multiple ESENT errors add on as you either use music or video apps. 😏

csmdew · 06 Jun 2020

Never there before update 2004 and rolling back is to much problem. But I do have log cleaner bat set up in the scheduler to run after log on so maybe change it to run more times daily.

Zardoc · 06 Jun 2020

csmdew said:

Never there before update 2004 and rolling back is to much problem. But I do have log cleaner bat set up in the scheduler to run after log on so maybe change it to run more times daily.

You can also set it to run each time a 642 event is logged.

csmdew · 06 Jun 2020

Don't know how to make it run just for that logging, how would i do it.

pietcorus2 · 06 Jun 2020

" You can also set it to run each time a 642 event is logged. "............yes, i did so , works fine .
Will use it untill a better fix appears !
" how to make it run just for that logging "..............I described my method a few days ago in this forum , just read it well !
You can add a task on each specific id-item , in this case ; a task for id=642 , this task wll activate the cleaner-batch , placed in C:\
Each ID=642 will trigger the cleaner-batch , in this way your eventlog will not be " overcrowded" with useless nonsense..............

Zardoc · 09 Jun 2020

Update 19041.329 still no ESENT fix.

NickosD · 10 Jun 2020

Try to delete windows old folder. It seems to be working so far. If you cant delete it via the explorer, go via the settings -> storage

- - - Updated - - -

NickosD said:

Try to delete windows old folder. It seems to be working so far. If you cant delete it via the explorer, go via the settings -> storage

Nvm, I'm still getting them

csmdew · 10 Jun 2020

Deleted it but still getting 2 esent warnings at log on and couple more during course of use, mostly Catalog Database ESENT.

pietcorus2 · 10 Jun 2020

Yes, noticed also ...............so , I keep on using my task for removing this s***** crap from my eventlog !
Untill finally ( !!!) fixed by MS ..........or a smarter person then I am ..........