New
#31
yeah is a strange one lol.
Eventlog warnings ; ESENT id=642
-
-
New #32
Thanks Pietcorus2.
I had an event viewer command. Since you mentioned it, I thought that you should share your solution.
If I were other users, I would most likely say, ''What's his solution ?''
My batch file does essentially the same thing.
Thanks
-
New #33
I've discovered that if I make Media Player the default app instead of Groove music I no longer get the ESENT ID 642 warnings referencing Music. UI on boot or when launching Edge. They only appear if you physically launch Groove Music. Media Player does not throw up the warning. Simple answer don't use Groove. Something to go on anyway.
Have not resolved the 2 Catalog Database Event 642 entries on boot yet.
-
New #34
" 2 Catalog Database Event 642 "..........still searching .......seems to be a "tough nut " to fix !!
If we knew WHAT (?) is triggering this id=642 , then we could find a solution............?!Last edited by pietcorus2; 02 Jun 2020 at 08:26.
-
New #35
It seems related to databases overriding others as mentioned by Garrett. The other issue is with Zune which involves video processing. There again, if you change your default player you might get rid of another ESENT message but what is the central link to all these messages has to do with the Jet database which seems to be damaged or is missing either code or files.
This is over my pay grade. I can apply a fix if I know the problem. But in this case, I don't have any idea.
-
New #36
-
New #37
Should stop installing new versions of windows. Last version i installed was 1903 and had vss errors that was fixed with my bat solution that pietcorus2 uses. Now I am getting esent 642 and 643 warnings. I think I will try ignoring them if I can as Microsoft says to ignore them.
-
New #38
Hi Shane, FWIW, the first couple of days I had version 2004, I was getting about 20/30 of this Warnings an hour. The last few days, they gone down to 2 at boot, and no more than that. They almost totally have gone away on their own.
Regarding the VSS Errors. I never did any workaround. But I am glad to tell you that it appears that finally they have been fixed. Since the upgrade to 2004, I haven't seen any VSS Errors. They are gone, the update must of fixed them.
Bo
-
-
-
New #40
After restarting, along with the two ESENT logs, I got VSS ID 13:
Volume Shadow Copy Service information: The COM Server with CLSID {4e14fba2-2e22-11d1-9964-00c04fbbb345} and name CEventSystem cannot be started. [0x8007045b, A system shutdown is in progress.
]
Quote
Related Discussions
