Windows 10: ESENT Log Name: Application

Can you help me with this?



Log Name: Application

Source: ESENT

Date: 1/8/2021 2:01:49 AM

Event ID: 642

Task Category: General

Level: Warning

Keywords: Classic

User: N/A

Computer: DESKTOP-892H6FC

Description:

Catalog Database 3356,D,12 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 0x410022D8 8920 JET_efvAllowHigherPersistedFormat.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="ESENT" />

<EventID Qualifiers="0">642</EventID>

<Version>0</Version>

<Level>3</Level>

<Task>1</Task>

<Opcode>0</Opcode>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2021-01-08T08:01:49.2523170Z" />

<EventRecordID>1236</EventRecordID>

<Correlation />

<Execution ProcessID="0" ThreadID="0" />

<Channel>Application</Channel>

<Computer>DESKTOP-892H6FC</Computer>

<Security />

</System>

<EventData>

<Data>Catalog Database</Data>

<Data>3356,D,12</Data>

<Data>Catalog Database: </Data>

<Data>0x410022D8 8920 JET_efvAllowHigherPersistedFormat</Data>

<Data>9080 0x2378</Data>

<Data>1568.20.0</Data>

</EventData>

</Event>



Thanks,


richard.moore

:)

 

ESENT 916

Thank you for the updates. Can you give me the full details of the error using the Event Viewer? When the error happens or shows, do these steps:

1. Press Windows key on your keyboard, type Event Viewer and select the search result.
2. On the left hand pane, click Windows Logs, and select
   Application.
3. On the Source column, there should be an ESENT
   with an Event ID of 916. Click the item and on the bottom pane, copy the information on the General tab and paste it here.

For now, according to my research, this may be closely related to hard drives. Can you give me information on what is the make and model of your hard drive?

I'll be waiting for your reply.

 

Event log full of ESENT event id 916

I've seen this discussed several times but nothing lately and nothing saying what to do about it.

Multiple times per hour - anything from 1 to 5 (so far) I get the following event logged:
Log Name: Application
Source: ESENT
Date: 12/29/2017 10:27:21 AM
Event ID: 916
Task Category: General
Level: Information
Keywords: Classic
User: N/A
Computer: Puget-116877
Description:
svchost (3644,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="ESENT" />
<EventID Qualifiers="0">916</EventID>
<Level>4</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-12-29T18:27:21.128090100Z" />
<EventRecordID>1695</EventRecordID>
<Channel>Application</Channel>
<Computer>Puget-116877</Computer>
<Security />
</System>
<EventData>
<Data>svchost</Data>
<Data>3644,G,0</Data>
<Data>
</Data>
<Data>EseDiskFlushConsistency</Data>
<Data>ESENT</Data>
<Data>0x800000</Data>
</EventData>
</Event>

About 37% of Application event records s on my PC are this record.

I see no problems on my PC that I can relate to the events so I doubt they are indicating a major problem, but they certainly clutter up the log making it more difficult to find significant event records. So I've got a few questions.

1. Does everybody get these or are they specific to my hardware/software/whatever environment?
2. What is EseDiskFlushConsistency this function" Is it something that can be disabled?
3. Is there any way to block the recording of these records or to do a mass deletion of them?

 

Error ESENT Event ID 413 Logging/Recovery

I was getting over 50 ESENT errors in the event viewer after each reboot. I tried SFC /SCANNOW, DISM, CHKDSK /R. It did not work.........................

I then created a new profile, rebooted and logged in with the new profile. The ESENT errors are now gone. The system runs smooth. Many other errors that event viewer was listing are also gone now.
The old profile was corrupt. The new profile works great!!!!!!!!!!!!!!!!