Unrecognized database format after January 2019 update KB4480966

I have many sites using my VB6 app that uses MDBs.

Since Windows update KB 4480966 was rolled out yesterday they are all getting an "unrecognizable database format" error at various parts of my program. It can load the database for some parts of the program but not others presumably based on the different tables being accessed.

Uninstalling the update solves the problem but there must be something in the JET Engine update that breaks something in my database structure.

It's also happening with Win 7 PCs.

Any ideas anyone?

Peter

 

Question Info


Last updated November 17, 2019 Views 3,409 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Hello,

look if you have field name greater than 32 caracters in your database.

10 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi,

Same problem. When compacting database would end up with MsysCompactError table and a table had gotten deleted from database. When checking this table we realized that one of the  field names was 34 characters long. We modified a database on a computer that was not patched to reduce field name to less than 32 characters and tried again on patched computer. All was well. Documentation says that object name can be 64 characters long. Looks like they decided to reduce this...

This is major, a lot of people will lose data from this bad patch. Table is completely wiped from database :(

Hope they fix this really, really soon. 

Thanks,

Paul

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hello,

look if you have field name greater than 32 caracters in your database.

Thank you.

That sentence saved me an incredible amount of work and avoided a lot of irate clients.  I sure would like to know how you figured that out.  Large payroll program - had 1 field that was 36 characters long .  was able to add a shorter field name - copy the data over and delete the large field in VB code.  VB6 could deal with the long name, however ActiveReports v2 barfed with the "unrecognized database error".

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi,

make sure you don't try to compact database before your fix or you can say goodbye to your table and all data within it. This is what happened to us :(

Paul

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi,

make sure you don't try to compact database before your fix or you can say goodbye to your table and all data within it. This is what happened to us :(

Paul

Oddly that was one of the first things I tried via a generic VB routine that also resets the password after compacting.   It ran fine and there was no loss of data.    However, I just tried it from Access and yes - table is automatically removed.  Glass half full, at least that's an easy way of seeing if a database has any fields > 32 characters.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.


Good morning.   CASE: 1456322769   The problem is CRITICAL and very serious. It occurs after updating the Windows updates KB 4480966 (Windows 10 in version 1803) KB 44880116 (Windows 10 in version 1809) even in Windows 7 but I have not yet identified the patch number   Access to the MSAccess database via DAO3.6 is INHIBITED. The call that goes wrong is: => DB.Openrecordset (sql, dbopensnapshot)   Error provided by the system is: DATABASE FORMAT NOT KNOWN (UNKNOWN DATABASE FORMAT)   The problem is solved by installing the patches: KB 4480966 (Windows 10 in version: 1803) KB 44880116 (Windows 10 in version: 1809)   But unfortunately later they are reinserted by the system, automatically   HELP, HELP.   What to do? with regard RV

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

We have found out, that this error only occurs on .mdb's older than access 2000.

That happends on every current windows system with current patches.

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

You can find the solution at

Windows January 2019 Updates breaks access to Access DBs

He did an excellent job writing this up.  We have already tested the dll replacement workaround and it fixed the issue on both Windows 10 and 7.

4 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Also, Microsoft acknowledges the problem here:

https://support.microsoft.com/en-us/help/4480960/windows-server-2008-kb4480960

Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if the database has column names greater than 32 characters. The database will fail to open with the error, “Unrecognized Database Format”.

Microsoft is working on a resolution and estimates a solution will be available early February.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Same issue with KB448960 and KB448970 on WIndows Server 2008 R2 Standard.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.