New
#11
" had to reinstall.".............are the ESENT id=642 gone after the reinstall , or are they coming back still..........??
Eventlog warnings ; ESENT id=642
-
-
New #12
The ESENT event id can be quite varied.
They typically are log entries without any noticeable performance changes.
So they can be ignored.
https://docs.microsoft.com/en-us/win...storage-engine
https://docs.microsoft.com/en-us/win...storage-engine
https://docs.microsoft.com/en-us/win...gine-reference
https://docs.microsoft.com/en-us/win...log-parameters
https://support.microsoft.com/en-us/...-and-326-occur
-
New #13
-
New #14
" 2004 upgrade resets some stuff ".............had to install my Logitech-webcam again and my Canon camera was not "recognised " anymore . Had to uninstall some software also ............not an easy upgrade this time !
Only the eventlog has not been solved yet.
I remember the upgrade to 1909 , with the VSS-errors in eventlog , after a few weeks a solution came from one of the forum-members ! With some luck this will happen again for "ESENT id=642 ".............
-
New #15
Let's hope so for a solution...
I still have the VSS errors but not always, can you post a link to the solution please?
Also when I use in cmd: Dism /Online /Cleanup-Image /RestoreHealth it gives The restore operation completed successfully, but at 84.9% stops. Do you get this too? Seems as an OS bug.
-
New #16
For the VSS-solution you have to look in the forum ( VSS-error forum ) .
Its been some time ago , but I do know I could find the solution in the VSS-forum.
Just search , you will find............
-
New #17
i get them as well many many look at my event viewer i think they can be safely ignored i have not seen any issues.
-
New #18
Still searching for solution............seems to be a very difficult problem !
Im using my "selfmade" event-task , made for this id=642 item.
Works fine , when the warning appears it will be deleted at once , so I dont see them anymore.
Will use this "fix" untill a better solution appears !
-
-
-
New #20
" Can you share your temp fix so others can use it please ?"
Here you go ;
Logboek wissen.batApplication_ESENT_642.txt
Attach this task to the id=642 .
Place the batch-file in C:\
In the txt-file ; change my name to yours and convert from txt to XML , try to import the task into your eventviewer .
If this wont work , make your own task from the id=642 , after you placed the cleaning-batch into C:\
Its an event-id task specified to delete the bloated, crappy "ESENT id=642 "
The batch-file will clean all eventlogs , when its been triggered by ; id=642 .
Maybe someone in this forum can change this batch-file to clean only the 642 ids , all other events will remain .
My batch-file will be triggered only by id=642 event.
good luck !
Last edited by pietcorus2; 01 Jun 2020 at 08:44.
Quote
Related Discussions
