none
Latest Office 2007/2010/2013/2016/2019 update breaks Access query: Query '' is corrupt. RRS feed

  • Question

  • Just wanted to inform doing simple Select/Update.. query from Visual Studio C# with Office 2007/2010/2013 started not to work after installing 2019-11-12 updates:

    KB4484160
    KB4484127
    KB4484164

    I'm getting this error, also my clients with Office 2007/2010/2013 have same issue. Other office versions not affected.

    Query '' is corrupt.    at System.Data.OleDb.OleDbCommand.ExecuteCommandTextErrorHandling(OleDbHResult hr)
       at System.Data.OleDb.OleDbCommand.ExecuteCommandTextForSingleResult(tagDBPARAMS dbParams, Object& executeResult)
       at System.Data.OleDb.OleDbCommand.ExecuteCommandText(Object& executeResult)
       at System.Data.OleDb.OleDbCommand.ExecuteCommand(CommandBehavior behavior, Object& executeResult)
       at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method)
       at System.Data.OleDb.OleDbCommand.ExecuteNonQuery()

    Temporary solve: Uninstalling these 3 KB448.. updates makes everything back work. Need help ASAP :)


    [Edited]
    Temporary fix, remove there KB:

    Office 2007/2010 – KB4484127
    Office 2013 – KB4484119
    Office 2016 – KB4484113

    If you have Office 2016/2019 ClickToRun then open cmd:

    cd %programfiles%\Common Files\Microsoft Shared\ClickToRun
    officec2rclient.exe /update user updatetoversion=16.0.xxxxx.yyyyy


    If you have Office 2013 ClickToRun open cmd:

    Windows 32-bit:
    cd %programfiles%\Microsoft Office 15\ClientX86 officec2rclient.exe /update user updatetoversion=15.0.xxxx.yyyy 
    Windows 64-bit:
    cd %programfiles%\Microsoft Office 15\ClientX64 officec2rclient.exe /update user updatetoversion=15.0.xxxx.yyyy



    • Edited by Vytautas A Thursday, November 14, 2019 12:28 PM
    Wednesday, November 13, 2019 7:25 AM

All replies

  • Removing KB4484127, fixxed our query errors on customers(msaccess 2010 rt program). We have hundreds installations. ASAP situation.

    Wednesday, November 13, 2019 8:04 AM
  • Seems Office 2007 + 2010 + 2013 also affected. Edited post.
    Wednesday, November 13, 2019 10:04 AM
  • Seems Office 2007 + 2010 + 2013 also affected. Edited post.

    Our Office 2016 clients are also affected.

    I believe the relevant KB articles/updates are:

    Access 2010  KB4484127
    Access 2013  KB4484119
    Access 2016  KB4484113

    • Edited by Grant Gardiner Wednesday, November 13, 2019 10:17 AM
    • Proposed as answer by Tracy Tam Thursday, November 14, 2019 5:21 AM
    Wednesday, November 13, 2019 10:15 AM
  • See https://borncity.com/win/2019/11/13/office-november-2019-updates-are-causing-access-error-3340/

    There is now a support article from Microsoft dealing with that – a fix is in progress and they propose a workaround.


    Gruß/greetings G. Born - Blogs: http://www.borncity.com/blog (Ger) - http://www.borncity.com/win (EN)

    Wednesday, November 13, 2019 3:21 PM
  • System Restore worked for me.  Rolling back O365 ProPlus from 16.0.12228.20120 to 16.0.12130.20272
    Wednesday, November 13, 2019 4:03 PM
  • Thanks for the information provided here!  I too have over 300 commercial customers and require a fix asap.  I've had 3 calls in the first hour this morning.  Uninstalling the update fixed each one.  These users obviously had their PCs set to update automatically.  I'm now concerned if Windows will automatically install the update again.  Any thoughts? 
    Wednesday, November 13, 2019 4:16 PM
  • Microsoft is aware of the issue, refer to https://support.office.com/en-us/article/access-error-query-is-corrupt-fad205a5-9fd4-49f1-be83-f21636caedec

    Daniel Pineault, 2010-2019 Microsoft MVP
    Professional Support: http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net


    Wednesday, November 13, 2019 4:25 PM
  • You may also find https://www.devhut.net/2019/11/14/access-bug-error-3340-query-is-corrupt/ useful.

    Daniel Pineault, 2010-2019 Microsoft MVP
    Professional Support: http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net


    Wednesday, November 13, 2019 4:37 PM
  • Can someone point to the instructions on how to uninstall the Office update?  I have Access 2013 running on Windows 10.  After installing the update, started getting "Query '' is corrupt" errors.  When I go to installed updates, however, I only see installed updates for Access database engine 2010 (Not 2013).  I do see "Security Update for Microsoft Office 2010 (KB4484127)" installed, but removing it does not solve the issue.  Any idea on how to uninstall the offending update to 2013?  Thanks in advance!
    Wednesday, November 13, 2019 11:31 PM
  • Just got a called from users...same thing about query. Not again.

    Just for info....this one is running on 2007 BE. Users are running Runtime 2007 and Full version of 2007, 2013 or 2016.

    I have not yet received any from 2000 users.

    Thursday, November 14, 2019 1:14 AM
  • Ok...

    What I found is that one user has 2 Runtime installed. 2010 & 2013. Default is 2013.

    1. RT2013
    2. Found 2 KB4484119 installed. (13-Nov-2019)
    3. Step 1 - removed one KB4484119 (lower in list)
    4. Nothing else is uninstall yet.
    5. Test Run MS Access - Success.
    1. RT2010.
    2. Removed KB4484160 & KB4484127
    3. No test required.

    So, the problem for 2013 is KB4484119 having double update. Just by removing one of them solved the problem.

    Thursday, November 14, 2019 3:29 AM
  • see "solution" at:

    https://support.office.com/en-us/article/access-error-query-is-corrupt-fad205a5-9fd4-49f1-be83-f21636caedec

    Thursday, November 14, 2019 12:22 PM
  • Temporary fix, remove there KB:

    Office 2007/2010 – KB4484127
    Office 2013 – KB4484119
    Office 2016 – KB4484113

    If you have Office 2016/2019 ClickToRun then open cmd:

    cd %programfiles%\Common Files\Microsoft Shared\ClickToRun
    officec2rclient.exe /update user updatetoversion=16.0.xxxxx.yyyyy


    If you have Office 2013 ClickToRun open cmd:

    Windows 32-bit: 
    cd %programfiles%\Microsoft Office 15\ClientX86

    officec2rclient.exe /update user updatetoversion=15.0.xxxx.yyyy

    Windows 64-bit: 
    cd %programfiles%\Microsoft Office 15\ClientX64

    officec2rclient.exe /update user updatetoversion=15.0.xxxx.yyyy

     
    Thursday, November 14, 2019 12:29 PM
  • we did Microsoft office unistall then install again  , problem was solve , but now we will try to uninstall    KB4484127 in windows update
    Thursday, November 14, 2019 1:13 PM
  • This is a huge problem.  all my programs are halted as a result.  Error is being trapped at a simple Update query.  3340

    I don't have KB4484127 in my list of installed updates.  there are two that were installed on 13-Nov-19

    KB4512578

    KB4523204

    I tried uninstalling the update and it's still there after a reboot.  

    Do you have anything more you can add to help?

    Steve


    Thursday, November 14, 2019 1:46 PM
  • You should start your own thread.

    What version of Access are you running?

        Access 2010 – Uninstall update KB4484127
        Access 2013 – Uninstall update KB4484119
        Access 2016 – Uninstall update KB4484113

    You can read all the available info at http://www.devhut.net/2019/11/14/access-bug-error-3340-query-is-corrupt/


    Daniel Pineault, 2010-2019 Microsoft MVP
    Professional Support: http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net

    Thursday, November 14, 2019 2:28 PM
  • If systems are set to update automatically they will update the uninstalled updates again.  I learned that the hard way.  I had to do all mine again today.
    Thursday, November 14, 2019 2:36 PM
  • I already tried everything and my solution was to stop the automatic installations directly from the service control to prevent these updates from being installed again.
    Thursday, November 14, 2019 2:53 PM
  • I had the same problem!  I already tried everything and my solution was to uninstall the bad updates and then stop the automatic installations directly from the services control to prevent these updates from being installed again and again.

    Go to Services an then search Windows Update, Right clik to go to properties an then stop the service.

    Thursday, November 14, 2019 3:16 PM
  • I wrote this code snippet (you may have to adjust it to match the tables in your database), and within a minute the whole program worked again. Hope this helps someone else, too:

    Public Sub RenameAllTables()
        Dim dbs As Database
        Dim tdf As TableDef
        Set dbs = CurrentDb
        For Each tdf In dbs.TableDefs
            If InStr(1, tdf.Name, "tbl_") > 0 Then ' this way we don't change system tables
                tdfName = tdf.Name
                tdfNewName = Replace(tdfName, tdfName, "dbo_" & tdf.Name)
                DoCmd.Rename tdfNewName, acTable, tdfName

                strSQL = "SELECT * FROM " & tdfNewName
                Set qdf = CurrentDb.CreateQueryDef(tdfName, strSQL)
            End If
        Next
    End Sub

    This uses the workaround suggested by Microsoft - to update a query instead of updating a table.

    The code will rename tbl_Customers to dbo_tbl_Customers, then create a query: SELECT * FROM dbo_tbl_Customers. The query is named tbl_Customers 

    Now anytime your code runs an update to tbl_Customers, it will be updating the query (that selects from the table)!!

    • Edited by developer1421 Thursday, November 14, 2019 6:24 PM
    • Proposed as answer by developer142 Thursday, November 14, 2019 7:33 PM
    Thursday, November 14, 2019 4:32 PM
  • Seems Office 2007 + 2010 + 2013 also affected. Edited post.

    Our Office 2016 clients are also affected.

    I believe the relevant KB articles/updates are:

    Access 2010  KB4484127
    Access 2013  KB4484119
    Access 2016  KB4484113

    It happened to several machines at work, after uninstall these KB all starting to go I also Approved for Removal on WSUS, but after several hours the issues start to appearing again. I checked again on installed updates but none of them where present. 

    Any other update involved?

    Any link where to tell Microsoft that this is not a issue but an Apocalyptic DISASTER!!!! ????

    Thursday, November 14, 2019 6:06 PM
  • Agreed, this is Apocalyptic.  The software work-around does solve the problem (I modified one application by changing all the update queries and SQL statements) but that means that we have to install updates to dozens of sites.  Unacceptable to wait till December 10 for a real fix.

    Thursday, November 14, 2019 7:22 PM
  • Use the Feedback button within the application, use access.uservoice.com, but it's not going to change anything.

    Daniel Pineault, 2010-2019 Microsoft MVP
    Professional Support: http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net

    Thursday, November 14, 2019 7:45 PM
  • Why not uninstall the faulty update, stop automatic updates and wait until the 12th to resume automatic updates.

    Not ideal by far, but better than spending hours modifying each database and then having to deploy them...  just a thought.


    Daniel Pineault, 2010-2019 Microsoft MVP
    Professional Support: http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net

    Thursday, November 14, 2019 7:47 PM
  • Assuming that you had a software product and you had such a stupid bug that created such a mayhem what would be your reactions ?...

    Just a thought on the "loose" response from MS.....

    Thursday, November 14, 2019 8:46 PM
  • John,

    Not sure who the comment was destined for, but I totally get all the frustration!!!  All of us are stuck with dealing, yet again, with MS' inability to release properly tested software/update/...  The whole thing is completely ridiculous!  but now the new norm with Win 10 and Office 2016+ / O365.  This has become the new Microsoft reality, sad, but true.

    As I understand it, these were security updates.  The reality we all face now, as it would appear, is that MS values security over functionality at this point in time, or they would have rolled it back by now.  They also probably deem the fact that a workaround exists (whoever poor it is) that to them it has been temporarily addressed. 

    And as per everything else in life, the squeaky wheel gets the grease.  If people want this dealt with, make some noise, especially those enterprise customers.  Call, send feedback, post in the access.uservoice.com, ... make MS understand your pain, lost time/$$$, ...

    That all said, I do know they are working to try and push an update out.  Let's just hope it doesn't turn into another "Unrecognized Database" bug where we're 16+ months and still waiting for a proper fix?!


    Daniel Pineault, 2010-2019 Microsoft MVP
    Professional Support: http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net

    Thursday, November 14, 2019 9:28 PM
  • Daniel my comment is destined to nobody and to all.

    You are a recognized developer...suppose you have made a similar mistake...i am pretty sure that probably you would sleep in the office till you have resolved it...instead we get a tap in the back....a workaround that is a bit hilarious and a promise about a fix some time in the future....

    Thursday, November 14, 2019 9:55 PM
  • Has anybody established whether this affects any rst.Update code when the recordset is based on a table?
    Thursday, November 14, 2019 10:50 PM

  • i am pretty sure that probably you would sleep in the office till you have resolved it...

    Oh yes, that has been the case.  My clients come first.  I've worked through the night more than once.  I've given up my summer vacation to deal with client problems (my wife is a very patient lady!).

    Double standards for sure!  The problem is MS knows people have little choice (in the grand scheme of things), so they can do as they please and they do.


    Daniel Pineault, 2010-2019 Microsoft MVP
    Professional Support: http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net

    Friday, November 15, 2019 12:28 AM
  • In your code you have, for example: updatetoversion=16.0.xxxxx.yyyyy Do you enter the x’s and y’s literally?
    Friday, November 15, 2019 2:15 AM
  • Try these:

     "C:\Program Files\Microsoft Office 15\ClientX86\OfficeC2RClient.exe" /update user updatetoversion=15.0.5179.1000


    "C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe" /update user updatetoversion=16.0.12130.20272

    Friday, November 15, 2019 4:15 AM
  • In your code you have, for example: updatetoversion=16.0.xxxxx.yyyyy Do you enter the x’s and y’s literally?
    No, they represent the build no you wish to switch to.

    Daniel Pineault, 2010-2019 Microsoft MVP
    Professional Support: http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net

    Friday, November 15, 2019 10:39 AM
  • Heads up, KB3085368 (Office 2016 released Nov 12th) also presents this bug, so be sure to uninstall it as well if it is present on your system!

    Daniel Pineault, 2010-2019 Microsoft MVP
    Professional Support: http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net

    Friday, November 15, 2019 2:27 PM
  • Ran the code, and it works.  Thank you

    So do we leave the rename permanent?  or do we rename back to the actual file names, should MS actually publish a fix to error bug 3340.  

    Friday, November 15, 2019 4:22 PM
  • Just an FYI, Microsoft has just released the first patch for Access 2016 MSI

    You can download the patch from https://support.microsoft.com/en-us/help/44...-2016-kb4484198

    *** This is a manual patch, so it will not automatically be installed by Windows Update and you must download and install it yourself! ***

    As for the other versions/editions … patches should be coming soon.


    Daniel Pineault, 2010-2019 Microsoft MVP
    Professional Support: http://www.cardaconsultants.com
    MS Access Tips and Code Samples: http://www.devhut.net

    Monday, November 18, 2019 8:14 PM
  • Thanks for the heads-up.  I do see their updated schedule as of today.  Much better.

    Monday, November 18, 2019 10:22 PM
  • Another work-around option that has worked for me is to turn off "other Microsoft software" updates and install an older run-time version of Access which was downloaded before this update. This assumes that the database works with the older version of course. Just another option.

    It really makes you wonder about QC at Microsoft - this affects every version of Access and any basic query which updates a table is rendered completely non functional as a result. Does Microsoft do ANY testing on these updates? If so, how could they miss this?


    Tuesday, November 19, 2019 5:06 AM
  • Hey Guys,

    Ms support just updated their release date for the fix.

    Access 2010 November 22, 2019 (estimated)

    Access 2013 November 22, 2019 (estimated)

    Access 2016 MSI November 18, 2019KB4484198

    Access 2019 Volume License December 10, 2019

    Access for Office 365 Monthly Channel/Access 2016 C2R/Access 2019 (Version 1910) November 18, 2019

    Access for Office 365 Semi-Annual(Version 1902)November 25, 2019 (estimated)

    I guess they noticed the urgency of the issue.


    Wednesday, November 20, 2019 9:18 AM
  • Did anyone get it or Office 2007? on the page only has for office 2010 up

    Wednesday, December 4, 2019 2:51 PM