Windows Server Forum
»
Windows Server
»
Event Log
»
The database format feature version 9180 (0x23dc) could not be used due to the current database
Rank: Advanced Member
Groups: Registered
Joined: 26/08/2020(UTC) Posts: 55  Thanks: 9 times Was thanked: 2 time(s) in 2 post(s)
|
This error is occurring on my Windows 10 box which I use as a NAS
What does it mean?
Log Name: Application Source: ESENT Date: 03/09/2020 13:28:50 Event ID: 642 Task Category: General Level: Warning Keywords: Classic User: N/A Computer: PC.domain.local Description: Catalog Database (3784,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). 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-09-03T12:28:50.9594394Z" /> <EventRecordID>7007</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>PC.domain.local</Computer> <Security /> </System> <EventData> <Data>Catalog Database</Data> <Data>3784,D,50</Data> <Data>Catalog Database: </Data> <Data>0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat)</Data> <Data>9180 (0x23dc)</Data> <Data>1568.20.0</Data> </EventData> </Event>
|
|
|
|
|
If you ever wanted to thank us, you can send us Bitcoins using:12G4A52Znm5s35buKDEmKU2p2vQY69Nsyo
All opinions expressed within these pages are sent in by members of the public or by our staff in their spare time, and as such do not represent any opinion held by sircles.net Ltd or their partners.
|
|
Rank: Advanced Member
Groups: Registered
Joined: 26/08/2020(UTC) Posts: 55  Thanks: 9 times Was thanked: 2 time(s) in 2 post(s)
|
It is some kind of Jet Database error and will probably be replaced by a different error at next update |:
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 08/01/2017(UTC) Posts: 672  Location: London Thanks: 17 times Was thanked: 6 time(s) in 6 post(s)
|
I have been receiving the errors for: Catalog Database (13848,D,35) 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). Catalog Database (13848,D,35) Catalog Database: 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). Catalog Database (13848,D,40) 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). In that order It appears that the databases here: C:\Windows\System32\catroot2 are the ones being referenced I have two databases in there:  Containing:  An excerpt from my DB error log from there reads: CatalogDB: 10:33:15 AM 10/23/2020: DONE Adding Catalog File (32ms): Microsoft-Windows-Internet-Browser-Package~31bf3856ad364e35~amd64~~10.0.19041.608.cat CatalogDB: 10:33:15 AM 10/23/2020: DONE Adding Catalog File (15ms): Microsoft-Windows-SenseClient-Package~31bf3856ad364e35~amd64~~10.0.19041.608.cat CatalogDB: 10:33:16 AM 10/23/2020: DONE Adding Catalog File (47ms): Microsoft-Windows-Client-Desktop-Required-Package~31bf3856ad364e35~amd64~~10.0.19041.608.cat CatalogDB: 10:33:16 AM 10/23/2020: DONE Adding Catalog File (62ms): Microsoft-Windows-Client-Desktop-Required- Stopping the Cryptographic Services and deleting the two folders has reduced the number of errors.Edited by user 09 November 2020 12:58:30(UTC)
| Reason: Not specified |
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 08/01/2017(UTC) Posts: 672  Location: London Thanks: 17 times Was thanked: 6 time(s) in 6 post(s)
|
Following on from the above, after taking that action (I just stopped the Cryptographic Services and moved both DB folders into a new folder I had created called Old and restarted the service.) After restarting the Cryptographic Services service, the proper EDB files appeared as can be seen here:  So presumably there was a serious problem compared to before as these files were not present. Edited by user 09 November 2020 12:59:48(UTC)
| Reason: Not specified |
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 08/01/2017(UTC) Posts: 672  Location: London Thanks: 17 times Was thanked: 6 time(s) in 6 post(s)
|
They disappeared again!! The log files disappear when you restart the Cryptographic service again - so they will presumably disappear at restart.  Stop the service, remove the DB folders and the log file, then restart and we see these files created:  What the heck? Still get the errors when restarting the Cryptographic services:  Each reads: Starting session 2 - 2020-11-09T13:06:19.695531100Z. Ending session 2 started 2020-11-09T13:06:19.695531100Z. Catalog Database (16064,D,35) 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). Catalog Database (16064,D,35) Catalog Database: 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). Catalog Database (16064,D,40) 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 (16064,D,35) 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). Catalog Database (16064,D,35) Catalog Database: 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). Catalog Database (16064,D,40) 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). Edited by user 09 November 2020 13:16:42(UTC)
| Reason: Not specified |
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 08/01/2017(UTC) Posts: 672  Location: London Thanks: 17 times Was thanked: 6 time(s) in 6 post(s)
|
How does Windows 10 reliably track the following?
Provides three management services: Catalog Database Service, which confirms the signatures of Windows files and allows new programs to be installed; Protected Root Service, which adds and removes Trusted Root Certification Authority certificates from this computer; and Automatic Root Certificate Update Service, which retrieves root certificates from Windows Update and enable scenarios such as SSL. If this service is stopped, these management services will not function properly. If this service is disabled, any services that explicitly depend on it will fail to start. |
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 26/08/2020(UTC) Posts: 55  Thanks: 9 times Was thanked: 2 time(s) in 2 post(s)
|
Yes it is definitely a jet db looking at those log files, but why it is never happy with the files it creates I am not sure. As for deleting the files but not recreating them, it seems as though the log file versions never match the edb files or something like that. I’m wondering if the cryptographic service works at all or if I should just disable it. It could always be restarted when an update containing root certificates is required. Edited by user 12 November 2020 23:01:01(UTC)
| Reason: Not specified
|
|
|
|
Rank: Administration
Groups: Administrators
Joined: 03/10/2016(UTC) Posts: 169
Was thanked: 16 time(s) in 15 post(s)
|
Just as an aside, when I look at my own Windows 10 Ent addition, I can see that this folder is populated with EDB files indicating that the Jet database is running correctly, but I have not had to restart the cryptographic services today to achieve this.  The PC has been powered up for some time though. I see the 642 ESENT errors on the same minutes past the hour, but the number of hours seems to vary???  Edited by user 16 November 2020 17:46:09(UTC)
| Reason: Not specified |
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 08/01/2017(UTC) Posts: 672  Location: London Thanks: 17 times Was thanked: 6 time(s) in 6 post(s)
|
This is a troubling error - my catroot2 folder is populated by those files today also??? Here is a happy picture to help:  Edited by user 19 November 2020 17:05:08(UTC)
| Reason: Not specified |
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 08/01/2017(UTC) Posts: 672  Location: London Thanks: 17 times Was thanked: 6 time(s) in 6 post(s)
|
Can everyone please report exact edition and build numbers please? This should be resolved simply enough. |
|
|
|
|
Rank: Administration
Groups: Administrators
Joined: 03/10/2016(UTC) Posts: 169
Was thanked: 16 time(s) in 15 post(s)
|
My version that appears to work well, but does seem to switch between populating the catroot2 folder and not (and which currently looks so)  Is this version:  |
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 26/08/2020(UTC) Posts: 55  Thanks: 9 times Was thanked: 2 time(s) in 2 post(s)
|
Unfortunately I am seeing the same in the Catroot2 folder:  And my version is as thus:  Edited by user 08 December 2020 15:09:38(UTC)
| Reason: Not specified
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 08/01/2017(UTC) Posts: 672  Location: London Thanks: 17 times Was thanked: 6 time(s) in 6 post(s)
|
Well they seem to be under the same condition as mine, which has a third different version number. How often are you seeing the event IDs?  I seem to get a spate of them and then they subside for 90 mins when I see:  Edited by user 08 December 2020 17:30:20(UTC)
| Reason: Not specified |
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 08/01/2017(UTC) Posts: 672  Location: London Thanks: 17 times Was thanked: 6 time(s) in 6 post(s)
|
I think we need to admit it comes and goes with the lack of jet database files. Looking at me dberr file in there - which doesn't give a lot of activity recently and in no way seems to account for the presence or absence of files here: CatalogDB: 4:20:39 AM 12/9/2020: DONE Adding Catalog File (0ms): Microsoft-Media-Foundation-Package~31bf3856ad364e35~amd64~~10.0.19041.685.cat CatalogDB: 4:20:39 AM 12/9/2020: DONE Adding Catalog File (0ms): Microsoft-Windows-Multimedia-MF-Package~31bf3856ad364e35~amd64~~10.0.19041.685.cat CatalogDB: 4:20:39 AM 12/9/2020: DONE Adding Catalog File (15ms): Multimedia-MFCore-Package~31bf3856ad364e35~amd64~~10.0.19041.685.cat CatalogDB: 4:20:39 AM 12/9/2020: DONE Adding Catalog File (16ms): Multimedia-MFCore-WCOSHeadless-Package~31bf3856ad364e35~amd64~~10.0.19041.685.cat CatalogDB: 4:20:39 AM 12/9/2020: DONE Adding Catalog File (0ms): Multimedia-MFCore-WCOSMinusHeadless-Package~31bf3856ad364e35~amd64~~10.0.19041.685.cat CatalogDB: 4:20:39 AM 12/9/2020: DONE Adding Catalog File (0ms): Microsoft-Windows-Media-Streaming-Package~31bf3856ad364e35~amd64~~10.0.19041.685.cat CatalogDB: 4:20:39 AM 12/9/2020: DONE Adding Catalog File (0ms): Microsoft-OneCore-Multimedia-CastingReceiver-Media-Package~31bf3856ad364e35~amd64~~10.0.19041.685.cat CatalogDB: 4:20:39 AM 12/9/2020: DONE Adding Catalog File (0ms): Microsoft-Windows-Holographic-Desktop-Merged-Package~31bf3856ad364e35~amd64~~10.0.19041.685.cat CatalogDB: 4:20:39 AM 12/9/2020: DONE Adding Catalog File (16ms): Microsoft-Windows-Holographic-Desktop-Analog-Package~31bf3856ad364e35~amd64~~10.0.19041.685.cat CatalogDB: 6:08:11 AM 12/16/2020: DONE Adding Catalog File (125ms): Microsoft-Office-ClickToRun-0DF537F297D220C26FD19F95D58BDF4E-i640.cab.cat CatalogDB: 6:08:13 AM 12/16/2020: DONE Adding Catalog File (63ms): Microsoft-Office-ClickToRun-6D7811AD-A68C-4956-B0F5-A9DB0E1B5D0D-stream.x86.en-us.dat.cat CatalogDB: 6:08:13 AM 12/16/2020: DONE Adding Catalog File (219ms): Microsoft-Office-ClickToRun-6D7811AD-A68C-4956-B0F5-A9DB0E1B5D0D-stream.x86.x-none.dat.cat It does have an entire week without any activity at all and then shows that MS Office made a few changes yesterday. Currently the folder is empty of files though:  Edited by user 17 December 2020 11:00:49(UTC)
| Reason: Add log files and dberr data |
|
|
|
|
Rank: Newbie
Groups: Registered
Joined: 17/08/2020(UTC) Posts: 5  Location: Fat land Was thanked: 1 time(s) in 1 post(s)
|
So what happens if you restart the cryptogrphic services now?
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 08/01/2017(UTC) Posts: 672  Location: London Thanks: 17 times Was thanked: 6 time(s) in 6 post(s)
|
|
|
|
|
|
Rank: Newbie
Groups: Registered
Joined: 17/08/2020(UTC) Posts: 5  Location: Fat land Was thanked: 1 time(s) in 1 post(s)
|
Most enlighteining. So does this mean that the cryptographic services really cannot create the database anymore? Catalog Database (18160,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).There is no database now, so surely it could create one? Edited by user 17 December 2020 11:10:06(UTC)
| Reason: Not specified
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 08/01/2017(UTC) Posts: 672  Location: London Thanks: 17 times Was thanked: 6 time(s) in 6 post(s)
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 08/01/2017(UTC) Posts: 672  Location: London Thanks: 17 times Was thanked: 6 time(s) in 6 post(s)
|
on build 19042.764 Of Win X I am only seeing these at restart now - or unless I restart cryptographic services - but no EDB files anywhere in CatRoot2 now... |
|
|
|
|
Windows Server Forum
»
Windows Server
»
Event Log
»
The database format feature version 9180 (0x23dc) could not be used due to the current database
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
Important Information:
The Windows Server Forum uses cookies. By continuing to browse this site, you are agreeing to our use of cookies.
More Details
Close