Share via

Multiple ESENT Warnings Event ID 642 post 2004 Upgrade

Anonymous
2020-06-09T20:13:53+00:00

Today 6/9/20 I got the update for Win 2004 along with several other updates. I installed the patch Tuesday updates before installing the Win 2004 update with no problems. I then installed Win 2004 update and I had no problems with it and after testing things on my computer everything seems to be ok but  I have run across in my Applications Event Viewer multiple ESENT Warnings Event 642. I do not seem to have any performance problems but who is to say that this will eventually cause some. The same thing happened when I upgraded to 1903 which was fixed by creating a TileDatabase folder by doing the below:

  • C:\WINDOWS\system32\config\systemprofile\AppData\Local\
  • (You may have to click on “Continue” when prompted.)
  • Once you are in the above mentioned location, right click and create a new folder and rename it as TileDataLayer
  • Double click on the TileDataLayer folder and inside the folder create a folder and name it as Database

I restarted my computer and they are still there. It would seem MS should have learned from it previous mistakes and fixed this before sending out another upgrade. I am not the only one experiencing this flood of warnings  as there as many others who have upgraded the computers to this bug infested updated. MS needs to be aware of this and just take a look at it and realize this is a bug and it needs to be fixed. People are losing faith in MS and their products and this should have been caught and fixed while in testing.   THIS is a MS bug and MS needs to address it and  come up with a fix either in an update or instructions to users on how to fix it..

Log Name:      Application

Source:        ESENT

Date:          6/9/2020 4:00:00 PM

Event ID:      642

Task Category: General

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      DESKTOP-

Description:

svchost (4828,D,22) SRUJet: The database format feature version 9120 (0x23a0) 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="2020-06-09T20:00:00.0226589Z" />

    <EventRecordID>438</EventRecordID>

    <Correlation />

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

    <Channel>Application</Channel>

    <Computer>DESKTOP- </Computer>

    <Security />

  </System>

  <EventData>

    <Data>svchost</Data>

    <Data>4828,D,22</Data>

    <Data>SRUJet: </Data>

    <Data>0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat)</Data>

    <Data>9120 (0x23a0)</Data>

    <Data>1568.20.0</Data>

  </EventData>

</Event>

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

56 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-11-12T03:30:13+00:00

    This is exactly correct. The Video.UI, Music.UI both use this database and the versions are being held back from updating due to an application parameter setting of 0x410022D8 (8920 | JET_efxAllowHigherPersistedFormat). The current default engine version is 9180, but the apps are being held back to version 8920 from updating to 9180. Rebuilding the indexes by hand should do the trick. Below are the events from my log showing the extra debugging messages:

    Music.UI (30008,P,98) {ABADF8F5-8FA8-423F-A0DF-3F3E0A09050F}: The database engine

    (10.00.19042.0000) is starting a new instance (0).

    Music.UI (30008,R,98) {ABADF8F5-8FA8-423F-A0DF-3F3E0A09050F}: The database engine is initiating recovery steps.

    Music.UI (30008,R,98) {ABADF8F5-8FA8-423F-A0DF-3F3E0A09050F}: Replay of a Create for database "C:\Users\rx8dr\AppData\Local\Packages\Microsoft.ZuneMusic_8wekyb3d8bbwe\LocalState\Database\923b3a4aedf121c5\EntClientDb.edb" at log position (00000001,0001,0268) was deferred due to AttachFuture.  Additional information: 

    **Then here is the first actual Warning**

    Music.UI (30008,R,98) {ABADF8F5-8FA8-423F-A0DF-3F3E0A09050F}: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

    Music.UI (30008,R,98) {ABADF8F5-8FA8-423F-A0DF-3F3E0A09050F}: The database [C:\Users\rx8dr\AppData\Local\Packages\Microsoft.ZuneMusic_8wekyb3d8bbwe\LocalState\Database\923b3a4aedf121c5\EntClientDb.edb] format version is being held back to 8920 (0x22d8) due to application parameter setting of 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat). Current default engine version: 9180 (0x23dc).

    Music.UI (30008,R,98) {ABADF8F5-8FA8-423F-A0DF-3F3E0A09050F}: The database engine has finished replaying logfile C:\Users\rx8dr\AppData\Local\Packages\Microsoft.ZuneMusic_8wekyb3d8bbwe\LocalState\Database\923b3a4aedf121c5\edb.log.

    Processing Stats:

    [1] 0.023146 -0.000331 (4) WT +J(CM:0, PgRf:0, Rd:0/0, Dy:0/0, Lg:1211637/10122) +M(C:0K, Fs:3056, WS:4704K # 4704K, PF:1972K # 1980K, P:1972K).

    Log record of type 'Insert   ' was seen most frequently (3680 times)

    Music.UI (30008,U,98) {ABADF8F5-8FA8-423F-A0DF-3F3E0A09050F}: The database engine has successfully completed recovery steps.

    Music.UI (30008,D,0) {ABADF8F5-8FA8-423F-A0DF-3F3E0A09050F}: The database engine started a new instance (0). (Time=0 seconds)

    Additional Data:

     lgposV2[] = 00000001:0001:0000 - 00000001:012C:03AD - 00000001:012D:0000 - 00000001:012D:0000 (00000000:0000:0000)

    cReInits = 28

    Internal Timing Sequence:

    [1] 0.002945 +J(0) +M(C:0K, Fs:570, WS:1912K # 1232K, PF:3596K # 3480K, P:3596K)

    [2] 0.000330 +J(0) +M(C:0K, Fs:143, WS:572K # 572K, PF:424K # 424K, P:424K)

    [3] 0.000015 +J(0) +M(C:0K, Fs:4, WS:16K # 16K, PF:64K # 64K, P:64K)

    [4] 0.000141 +J(0) +M(C:0K, Fs:64, WS:256K # 256K, PF:180K # 180K, P:180K)

    [5] 0.001468 +J(0) +M(C:0K, Fs:172, WS:680K # 680K, PF:260K # 260K, P:260K)

    [6] 0.004265 +J(0) +M(C:0K, Fs:162, WS:608K # 608K, PF:180K # 180K, P:180K)

    [7] 0.025941 -0.000002 (2) WT +J(0) +M(C:0K, Fs:1430, WS:5676K # 5676K, PF:8936K # 8936K, P:8936K)

    [8] 0.024402 -0.000331 (4) WT +J(CM:0, PgRf:0, Rd:0/0, Dy:0/0, Lg:1211637/10122) +M(C:0K, Fs:3175, WS:5172K # 5172K, PF:2352K # 2360K, P:2352K)

    [9] 0.000324 +J(0) +M(C:0K, Fs:51, WS:196K # 196K, PF:152K # 144K, P:152K)

    [10] 0.000769 +J(0) +M(C:0K, Fs:76, WS:-1740K # 84K, PF:-1384K # 532K, P:-1384K)

    [11] 0.000015 +J(CM:0, PgRf:0, Rd:0/0, Dy:0/0, Lg:49/1) +M(C:0K, Fs:2, WS:8K # 0K, PF:0K # 0K, P:0K)

    [12] 0.014102 -0.014063 (2) WT +J(0) +M(C:0K, Fs:470, WS:1796K # 0K, PF:268K # 0K, P:268K)

    [13] 0.019656 -0.000233 (2) CM -0.015259 (19) WT +J(CM:2, PgRf:2, Rd:0/2, Dy:0/0, Lg:8759/5) +M(C:0K, Fs:1030, WS:1948K # 3976K, PF:424K # 828K, P:424K)

    [14] 0.000020 +J(0) +M(C:0K, Fs:1, WS:4K # 0K, PF:4K # 0K, P:4K)

    [15] 0.000008 +J(0)

    [16] 0.000100 +J(0) +M(C:0K, Fs:4, WS:8K # 0K, PF:8K # 0K, P:8K).

    Music.UI (30008,D,50) {ABADF8F5-8FA8-423F-A0DF-3F3E0A09050F}: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

    Music.UI (30008,D,50) {ABADF8F5-8FA8-423F-A0DF-3F3E0A09050F}: The database [C:\Users\rx8dr\AppData\Local\Packages\Microsoft.ZuneMusic_8wekyb3d8bbwe\LocalState\Database\923b3a4aedf121c5\EntClientDb.edb] format version is being held back to 8920 (0x22d8) due to application parameter setting of 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat). Current default engine version: 9180 (0x23dc).

    Music.UI (30008,D,50) {ABADF8F5-8FA8-423F-A0DF-3F3E0A09050F}: The log format feature version 8940 (0x22ec - 8.6.20) could not be used due to the current log format 8.5.16, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

    Music.UI (30008,D,50) {ABADF8F5-8FA8-423F-A0DF-3F3E0A09050F}: The database engine attached a database (1, C:\Users\rx8dr\AppData\Local\Packages\Microsoft.ZuneMusic_8wekyb3d8bbwe\LocalState\Database\923b3a4aedf121c5\EntClientDb.edb). (Time=0 seconds)

    Saved Cache: 0 0

    Additional Data: lgposAttach = 00000001:012F:0268,

    dbv = 1568.20.0

    Internal Timing Sequence:

    [1] 0.000001 +J(0)

    [2] 0.000258 +J(0) +M(C:0K, Fs:19, WS:12K # 0K, PF:8K # 0K, P:8K)

    [3] 0.002330 -0.000292 (5) WT +J(CM:0, PgRf:0, Rd:0/0, Dy:0/0, Lg:3480/2) +M(C:0K, Fs:105, WS:412K # 0K, PF:24K # 0K, P:24K)

    [4] 0.000126 +J(0) +M(C:0K, Fs:2, WS:8K # 0K, PF:0K # 0K, P:0K)

    [5] -

    [6] -

    [7] -

    [8] 0.000882 -0.000182 (2) CM +J(CM:2, PgRf:2, Rd:14/2, Dy:0/0, Lg:0/0) +M(C:0K, Fs:30, WS:104K # 0K, PF:120K # 0K, P:120K)

    [9] 0.008459 -0.000495 (5) CM -0.007734 (1) WT +J(CM:5, PgRf:23, Rd:0/5, Dy:0/0, Lg:0/0) +M(C:0K, Fs:295, WS:1164K # 0K, PF:288K # 0K, P:288K)

    [10] 0.000111 -0.000003 (2) CM +J(CM:2, PgRf:40, Rd:0/2, Dy:0/0, Lg:0/0) +M(C:0K, Fs:7, WS:12K # 0K, PF:68K # 0K, P:68K)

    [11] 0.000021 -0.000001 (1) CM +J(CM:1, PgRf:1, Rd:0/1, Dy:0/0, Lg:0/0) +M(C:0K, Fs:3, WS:4K # 0K, PF:0K # 0K, P:0K)

    [12] 0.000037 -0.000001 (1) CM +J(CM:1, PgRf:42, Rd:0/1, Dy:0/0, Lg:0/0) +M(C:0K, Fs:5, WS:12K # 0K, PF:0K # 0K, P:0K)

    [13] 0.0 +J(0)

    [14] 0.0 +J(0)

    [15] 0.000020 -0.000001 (1) CM +J(CM:1, PgRf:1, Rd:0/1, Dy:0/0, Lg:0/0) +M(C:0K, Fs:2, WS:0K # 0K, PF:0K # 0K, P:0K).

    Music.UI (30008,D,12) {ABADF8F5-8FA8-423F-A0DF-3F3E0A09050F}: 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).

    Music.UI (30008,D,2) {ABADF8F5-8FA8-423F-A0DF-3F3E0A09050F}: The database [C:\Users\rx8dr\AppData\Local\Packages\Microsoft.ZuneMusic_8wekyb3d8bbwe\LocalState\Database\923b3a4aedf121c5\tmp.edb] format version is being held back to 8920 (0x22d8) due to application parameter setting of 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat). Current default engine version: 9180 (0x23dc).

    Music.UI (30008,D,2) {ABADF8F5-8FA8-423F-A0DF-3F3E0A09050F}: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

    Music.UI (30008,D,2) {ABADF8F5-8FA8-423F-A0DF-3F3E0A09050F}: 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).

    ........These 16 informational messages and warnings are exactly dulicated in the Event Log, again, for Video.UI....I won't bother to copy/paste them all, as the issue is identical. After the Video.UI entries the next significant messages in the log are 3 lines for Catalog Database, see below:

    Catalog Database (6220,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).

    ...this Warning is repeated in triplet each time it occurs, indicating the call is being made 3 times before failing. Fast Forward several seconds and there is SearchIndexer entries, showing it's using version 1568.110.240 (8920), see below:

    SearchIndexer (12168,D,50) Windows: The database engine attached a database (1, C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb). (Time=0 seconds)

    Saved Cache: 0 0

    Additional Data: lgposAttach = 00000640:00B3:0268,

    dbv = 1568.110.240

    Internal Timing Sequence:

    [1] 0.000003 +J(0) +M(C:0K, Fs:1, WS:4K # 0K, PF:0K # 0K, P:0K)

    [2] 0.001477 -0.000139 (1) WT +J(0) +M(C:0K, Fs:24, WS:32K # 0K, PF:32K # 0K, P:32K)

    [3] 0.002919 -0.000741 (6) WT +J(CM:0, PgRf:0, Rd:0/0, Dy:0/0, Lg:3480/2) +M(C:0K, Fs:38, WS:120K # 0K, PF:136K # 0K, P:136K)

    [4] 0.000104 +J(0) +M(C:0K, Fs:1, WS:4K # 0K, PF:0K # 0K, P:0K)

    [5] -

    [6] -

    [7] -

    [8] 0.000880 -0.000656 (2) CM +J(CM:2, PgRf:2, Rd:14/2, Dy:0/0, Lg:54/1) +M(C:0K, Fs:56, WS:220K # 0K, PF:720K # 0K, P:720K)

    [9] 0.017637 -0.000173 (5) CM -0.017308 (1) WT +J(CM:5, PgRf:23, Rd:0/5, Dy:0/0, Lg:0/0) +M(C:0K, Fs:72, WS:288K # 0K, PF:288K # 220K, P:288K)

    [10] 0.000100 -0.000047 (1) CM +J(CM:1, PgRf:40, Rd:0/1, Dy:0/0, Lg:0/0) +M(C:0K, Fs:11, WS:44K # 40K, PF:96K # 96K, P:96K)

    [11] 0.000005 +J(CM:0, PgRf:1, Rd:0/0, Dy:0/0, Lg:0/0) +M(C:0K, Fs:1, WS:4K # 4K, PF:0K # 0K, P:0K)

    [12] 0.000022 +J(CM:0, PgRf:42, Rd:0/0, Dy:0/0, Lg:0/0) +M(C:0K, Fs:3, WS:12K # 12K, PF:0K # 0K, P:0K)

    [13] 0.0 +J(0)

    [14] 0.0 +J(0)

    [15] 0.000002 +J(CM:0, PgRf:1, Rd:0/0, Dy:0/0, Lg:0/0).

    ....above you can see the version referenced on line 3: dbv = 1568.110.240; I then get 9 subsequent Warnings about Catalog Database making calls for both database format versions 9080 and 9180.

    There are some other messages, as often they are duplicated, but I've included the relevant ones. I have not tried manually rebuilding yet, but I will update with more details once I do.

    For a frame of reference, this is happening on a clean install of version 2004 that is then updated to:

    Edition    Windows 10 Pro

    Version    20H2

    Installed on    ‎9/‎11/‎2020

    OS build    19042.610

    Experience    Windows Feature Experience Pack 120.2212.31.0

    My best guess is that this happens when Microsoft's OS builds update the database version faster than the app maintainers keep up with database versions. Clearly this isn't only happening on Insider Builds, so there's really no excuse for it to happen on "Stable" releases. I am, at this moment, rebooting to finish installation of Cummulative Update (KB4586781) and I'll take a glance at the event log and see if things have improved any...

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments
  2. Anonymous
    2020-12-03T17:27:01+00:00

    So how does one go about rebuilding the indices?

    ... Rebuilding the indexes by hand should do the trick. 

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  3. Anonymous
    2020-07-11T18:41:21+00:00

    I saw your post on my thread but thought I'd post my findings here just in case some only sees this one:

    It's now 10 days since 2004 updated and the Windows.old folder was automatically deleted. My ESENT 642 warnings in event viewer have STOPPED. I cannot answer as to crashing apps and slowdowns but as far as the ESENT warning goes, I think this was the solution.

    I'm a consultant to several dental offices and have upgraded them to 2004 and the latest Edge.  Every one is now getting a ton of the ESENT 642 errors with their main dental program crashing a couple of times a day.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-06-22T17:19:19+00:00

    I saw your post on my thread but thought I'd post my findings here just in case some only sees this one:

    It's now 10 days since 2004 updated and the Windows.old folder was automatically deleted. My ESENT 642 warnings in event viewer have STOPPED. I cannot answer as to crashing apps and slowdowns but as far as the ESENT warning goes, I think this was the solution.

    Thank you so much for responding. I can see where they might be a problem with the Windows.old folder and the new install. I will certainly keep an eyes out for the expiration time and let you know what I see. I have thoroughly tested my computers and the installed Apps and I have not encountered any problems but I did get a message about my account and all I did was click on Fix It and re-entered my password and it fixed. I did get two more updates after installing 2004. One was for .Net Framework and the the other was for Adobe Flash. All in all it went smoother than what I anticipated with all the problems I have read about. I will keep a close eyes over the next few days and if I see anything weird I will let you know.  Thanks a lot KenMel.

    Respectfully,

    Don

    Hello,

    My Windows.old file is now gone and I have noticed a considerable drop of the ESENT errors 642. I did a Disk Clean up but I am seeing only "one group"  of 6 ESENT errors containing these two below in that one group and they appear right after a restart. Does anyone have any idea what these could be or how to get rid of them? 

    Catalog Database (2460,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).

    Catalog Database (2460,D,50) Catalog Database: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

    Thanks

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  5. Anonymous
    2020-09-15T03:56:32+00:00

    In general 642 are not new to this release.  Essentially you need to figure out which database needs to be updated.  The one I had this happen for was the main searhindex database.  Simple fix for that one is go to in to search indexing, advance

    options and select rebuild index.  I think the Video.ui may use that one as well, but not sure.  Depending on size and speed of your system this can take hours or even days.

    Periodically some of these databases appear to do a rebuild which is when the error goes away for most people.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments