UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
> Office Update Can Cause Issues With Access Queries    
 
   
DougY
post Nov 13 2019, 12:50 PM
Post#1


Utterly Abby-Normal
Posts: 15,792
Joined: 30-June 04
From: Seattle, WA [USA]


The November Patch Tuesday Office release introduce an issue with Access queries. A change to fix a security vulnerability causes some legitimate queries to be reported as corrupt. The update is 1328.20468; it was released Nov 12, but hasn’t rolled out to everyone all at once.

Because the change was a security fix, it impacts ALL builds of Office, including 2010, 2013, 2016, 2019, and O365.

The bug has been fixed in all channels, but the timing of delivery will depend on what channel you are on.

- For 2010, 2013, and 2016 MSI, and 2019 Volume License builds, and the O365 Semi-annual channel, the fix will be in the December Patch Tuesday build, Dec 10.
- For O365, Monthly Channel, and Insiders, this will be fixed when the October fork is released, currently planned for Nov 24.

If you can, you might want to hold off on updating until Dec 10.

The issue occurs for update queries against a single table with a criteria specified (so other types of queries shouldn’t be impacted, nor any query that updates all rows of a table, nor a query that updates the result set of another query).

Information and workaround can be found here: Access error: "Query is corrupt"

--------------------
- Doug

When I said the program was fool proof, I hadn’t realized there were so many fools.
Go to the top of the page
 
Start new topic
Replies
isladogs
post Nov 13 2019, 01:42 PM
Post#2


UtterAccess VIP
Posts: 2,111
Joined: 4-June 18
From: Somerset, UK


I'm one of the 'lucky ones' affected by this update.

I've just done some further testing.
If done using code, the same SQL fails with same error - 3340. That's a bigger issue at least for me

The suggested workround is to create a query based on the table then run an update query based on that.
It also seems to work fine if you just join another table or query to the one you want to update or even just use a cartesian join with something unrelated.

The update that caused this cockup was released on 12 Nov to 'fix a security vulnerability'. This link describes the patch https://support.microsoft.com/en-gb/help/44...ovember-12-2019.
As its unclear how serious a vulnerability was patched, it MAY be better to block the update if you don't have it as Doug suggests.
Or if you do, you can uninstall it! Its KB448127 for A2010. I've just done so and the error has gone

The MS article makes no mention of updating A2007 or earlier. Is that because they aren't affected or just because they are past end of support period?
If the latter, I may be forced to move away from A2010 in the near future as its approaching end of support also.

--------------------
Colin (Mendip Data Systems)
Website, email
Go to the top of the page
 
jleach
post Nov 13 2019, 02:08 PM
Post#3


UtterAccess Administrator
Posts: 10,402
Joined: 7-December 09
From: St. Augustine, FL


Colin - my guess that there's no mention of '07 because it's past end of life (the article states that this effects all supported versions, and '07 doesn't get security patches anymore)

--------------------
Jack D. Leach
Founder & CEO
Dymeng Services Inc.
Business Software Solutions
Go to the top of the page
 
cheekybuddha
post Nov 13 2019, 02:12 PM
Post#4


UtterAccess Moderator
Posts: 12,127
Joined: 6-December 03
From: Telegraph Hill


Colin,

Do you still get the error if you change your code to:
CODE
  strSQL = "UPDATE (SELECT * FROM YourTable) SET Fld1 = 1 WHERE Field1 IS NULL;"

?

--------------------


Regards,

David Marten
Go to the top of the page
 
isladogs
post Nov 14 2019, 10:50 AM
Post#5


UtterAccess VIP
Posts: 2,111
Joined: 4-June 18
From: Somerset, UK


Hi David
Sorry. I've uninstalled the Office update so unable to test your suggestion

--------------------
Colin (Mendip Data Systems)
Website, email
Go to the top of the page
 
Wedge
post Nov 14 2019, 11:38 AM
Post#6



Posts: 177
Joined: 29-March 05
From: Yorkshire Dales, England


I am not sure if this KB is even really broken as such. It looks like someone has decided that update queries that directly effect tables are 'insecure' so has simply turned them off. I wouldn't mind but if MS are going to do this could you please give us a head-up so we can change our code? Wasted many hours yesterday morning with this one. As you can probably guess - I am not happy. mad.gif

--------------------
Sam
Go to the top of the page
 
FrankRuperto
post Nov 14 2019, 02:11 PM
Post#7



Posts: 542
Joined: 21-September 14
From: (MilitaryBrat) Tampa Bay, Florida, USA


@Wedge

Agreed, disabling win update service has its downside, plus not all users can disable it because their boxes are managed by IT dept's via group policy settings.
MS is progressively getting worse at publishing updates without thoroughly testing them to make sure it doesn't impact users.

--------------------
Currently supporting pawnbrokers that use my store management system developed with Access 2010 on Windows7. Experienced with Informix and Oracle DB's.
Go to the top of the page
 
jleach
post Nov 14 2019, 07:22 PM
Post#8


UtterAccess Administrator
Posts: 10,402
Joined: 7-December 09
From: St. Augustine, FL


Luke Chung of FMS has a comprehensive writeup on this here, including step by step fixes w/ visuals:

http://fmsinc.com/MicrosoftAccess/Errors/q...rrupt/index.htm

--------------------
Jack D. Leach
Founder & CEO
Dymeng Services Inc.
Business Software Solutions
Go to the top of the page
 
Wedge
post Nov 15 2019, 03:39 PM
Post#9



Posts: 177
Joined: 29-March 05
From: Yorkshire Dales, England


Luke is a hero. thanks.gif

I love FMS thumbup.gif

I have read the utterly amazingly woeful response on the FMS page from MS. In the name of sanity MS - even if you:

1). released an horrific security 'patch' that kills update queries
2). without testing
3). and will take a month (!) to fix it

will you...

*PLEASE STOP PUSHING IT OUT ON WINDOWS UPDATE*

I am hoping you at least have the ability to speak with someone who runs that part of the business and can maybe take it down? Or is that just too complicated?

This is comically bad MS.

--------------------
Sam
Go to the top of the page
 
DaveH
post Nov 16 2019, 10:16 AM
Post#10



Posts: 30
Joined: 1-May 18



Hardly a monthly update from Microsoft for Win 10/7 has passed without incident this year, surely some of the millions of Office users must have tested these updates before they were released but apparently not - else the fault would have been discovered.

KB4484127, KB4484119, and KB4484113 along with KB890830 (malicious removal tool) can’t possibly have been tested properly or at all.

Then to add insult to injury they won’t fix it until Decembers updates and even worse they have not pulled it.

I can only suggest that all the “script kiddies” fresh from University start their careers at MS implementing Windows updates and they’ve laid off all the old hands to try and save money, this is the result.
Go to the top of the page
 
DanielPineault
post Nov 18 2019, 02:31 PM
Post#11


UtterAccess VIP
Posts: 7,077
Joined: 30-June 11



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

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

--------------------
Daniel Pineault (2010-2019 Microsoft MVP, UA VIP, EE Distinguished Expert 2018)
Professional Help: https://www.cardaconsultants.com
Free MS Access Code, Tips, Tricks and Samples: https://www.devhut.net

* Design should never say "Look at me". It should always say "Look at this". -- David Craib
* A user interface is like a joke, if you have to explain it, it's not that good! -- Martin LeBlanc


All code samples, demonstration databases, links,... are provided 'AS IS' and are to be used at your own risk! Take the necessary steps to check, validate ...(you are responsible for your choices and actions)
Go to the top of the page
 
FrankRuperto
post Nov 18 2019, 06:38 PM
Post#12



Posts: 542
Joined: 21-September 14
From: (MilitaryBrat) Tampa Bay, Florida, USA


Lets hope MS thoroughly tested the patch, and not fix one thing that breaks other(s). These repeated blunders are putting a big dent in MS' credibility.

--------------------
Currently supporting pawnbrokers that use my store management system developed with Access 2010 on Windows7. Experienced with Informix and Oracle DB's.
Go to the top of the page
 
tina t
post Nov 18 2019, 09:06 PM
Post#13



Posts: 6,305
Joined: 11-November 10
From: SoCal, USA


QUOTE
These repeated blunders are putting a big dent in MS' credibility.

they have credibility left to dent? i hadn't noticed.

the (SELECT * FROM MyTable) workaround does work, at least so far, for me. since i am still working on my IT dept's conversion-from-A97-to-A2016-64bit project, i'm only going to fix the queries that err as i'm continuing to test my converted dbs. hopefully the 11/24 fix will take care of the issue without making a bigger mess.

:(
tina

--------------------
"the wheel never stops turning"
Go to the top of the page
 
gemmathehusky
post Nov 25 2019, 08:00 AM
Post#14


UtterAccess VIP
Posts: 4,752
Joined: 5-June 07
From: UK


Personally, I think the cure suggested by MS is as bad as the problem.

I think as well as the query issue, it also affects recordset operations (maybe depending on the query), so opening a table, and the rs.addnew etc also failed, I believe.
Changing an testing everything in complex databases is hardly feasible.

Anyway, I have advised clients to unwind the update as the simplest fix

With regard to colin/isladogs issue about the version to revert to, I suspect the version you needed depended on the update stream you were using.

https://docs.microsoft.com/en-us/officeupda...proplus-by-date









--------------------
Dave (Male)

(Gemma was my dog)
Go to the top of the page
 
theDBguy
post Nov 25 2019, 12:10 PM
Post#15


UA Moderator
Posts: 77,341
Joined: 19-June 07
From: SunnySandyEggo


Hi Dave. Using the fix I suggested/recommend, I tested, last night, opening a recordset was not a problem. Now, I just tested adding a new record to the recordset is also not a problem. No errors.

--------------------
Just my 2 cents... "And if I claim to be a wise man, it surely means that I don't know" - Kansas
Access Website | Access Blog | Email
Go to the top of the page
 
JeffK
post Dec 3 2019, 09:13 AM
Post#16


UtterAccess VIP
Posts: 1,585
Joined: 19-December 02
From: Lansing, MI


ADODB recordset Update calls are breaking for me as well, with the same “Query ‘’ is corrupt” message. Access 2019, only on PCs with the security update applied. However, it’s only in cases where CursorLocation is set to adUseClient. Remove that solves the problem. With the client-side cursor setting, no changes to the source fix the problem ( such as selectig from a query or subquery).
Go to the top of the page
 
theDBguy
post Dec 3 2019, 07:44 PM
Post#17


UA Moderator
Posts: 77,341
Joined: 19-June 07
From: SunnySandyEggo


Hi. Do you know if you have a volume licensed version of 2019?

--------------------
Just my 2 cents... "And if I claim to be a wise man, it surely means that I don't know" - Kansas
Access Website | Access Blog | Email
Go to the top of the page
 
JeffK
post Dec 4 2019, 10:40 AM
Post#18


UtterAccess VIP
Posts: 1,585
Joined: 19-December 02
From: Lansing, MI


Yes, my Access 2019 is the perpetual license, not O365.
Go to the top of the page
 
theDBguy
post Dec 4 2019, 11:26 AM
Post#19


UA Moderator
Posts: 77,341
Joined: 19-June 07
From: SunnySandyEggo


Just curious because VL 2019 doesn't have a fix available yet.

--------------------
Just my 2 cents... "And if I claim to be a wise man, it surely means that I don't know" - Kansas
Access Website | Access Blog | Email
Go to the top of the page
 
rsindle
post Dec 4 2019, 02:58 PM
Post#20


UtterAccess VIP
Posts: 1,701
Joined: 25-June 04
From: Northern Virginia


This is a slightly different spin on this problem.
I have Office Pro 2010 and 2013 installed on my dev laptop.
2010 did NOT exhibit this problem. 2013 did.
Weird thing is if I go to "Installed Updates" all of my 2010 Security updates etc show up.
NONE for 2013.
My Access 2013 is (according to Microsoft) the latest version (15.0.5189.1000) 32-bit.
I went ahead and ran the 2010 patch (ace2010-kb2986256-fullfile-x86-glb.exe) and that ran.
The 2013 patch (ace2013-kb2965317-fullfile-x86-glb.exe) gave me the message:
"There are no products affected by this package installed on this system"
So I am dead-in-the-water on 2013, but 2010 runs fine.
****** UPDATE ON THIS ******
Apparently I DO have C2R for my 2013 (MSI for my 2010) as this link says:
Determine MSI or C2R

So will be waiting impatiently, for the 12/10/2019 fix for MY system.
UGH!
pullhair.gif
Rob

Go to the top of the page
 
fizzy1
post Dec 12 2019, 03:45 PM
Post#21



Posts: 551
Joined: 26-May 11



So, December 10 was 2 days ago. Is all of this mess behind us now?

--------------------

thanks,
fizzy1.
Go to the top of the page
 
theDBguy
post Dec 12 2019, 09:04 PM
Post#22


UA Moderator
Posts: 77,341
Joined: 19-June 07
From: SunnySandyEggo


For the most part, yes, but not entirely. It's possible subsequent updates could override the fix update and bring back the problem. If so, you would have to reinstall the fix.

--------------------
Just my 2 cents... "And if I claim to be a wise man, it surely means that I don't know" - Kansas
Access Website | Access Blog | Email
Go to the top of the page
 
FrankRuperto
post Dec 12 2019, 09:13 PM
Post#23



Posts: 542
Joined: 21-September 14
From: (MilitaryBrat) Tampa Bay, Florida, USA


QUOTE
It's possible subsequent updates could override the fix update and bring back the problem.


If that happens we would all be back to square one so I am hoping MS has enough sense to prevent that from happening.

--------------------
Currently supporting pawnbrokers that use my store management system developed with Access 2010 on Windows7. Experienced with Informix and Oracle DB's.
Go to the top of the page
 

Posts in this topic
- DougY   Office Update Can Cause Issues With Access Queries   Nov 13 2019, 12:50 PM
- - isladogs   I'm one of the 'lucky ones' affected b...   Nov 13 2019, 01:42 PM
|- - jleach   Colin - my guess that there's no mention of ...   Nov 13 2019, 02:08 PM
|- - cheekybuddha   Colin, Do you still get the error if you change ...   Nov 13 2019, 02:12 PM
|- - isladogs   Hi David Sorry. I've uninstalled the Office up...   Nov 14 2019, 10:50 AM
||- - Wedge   I am not sure if this KB is even really broken as ...   Nov 14 2019, 11:38 AM
||- - FrankRuperto   @Wedge Agreed, disabling win update service has i...   Nov 14 2019, 02:11 PM
||- - jleach   Luke Chung of FMS has a comprehensive writeup on t...   Nov 14 2019, 07:22 PM
||- - isladogs   Just realised that I still have the issue on Acces...   Nov 15 2019, 08:21 AM
|||- - isladogs   Further Update: I have now also successfully remov...   Nov 15 2019, 10:02 AM
|||- - fizzy1   I have a bunch of customers using one app. I have ...   Nov 15 2019, 01:43 PM
||- - Wedge   Luke is a hero. I love FMS I have read the...   Nov 15 2019, 03:39 PM
||- - DaveH   Hardly a monthly update from Microsoft for Win 10/...   Nov 16 2019, 10:16 AM
||- - DanielPineault   Microsoft has just released the first patch for Ac...   Nov 18 2019, 02:31 PM
||- - FrankRuperto   Lets hope MS thoroughly tested the patch, and not ...   Nov 18 2019, 06:38 PM
|||- - tina t   QUOTE These repeated blunders are putting a big de...   Nov 18 2019, 09:06 PM
|||- - youngb   Hi Guys, I just learned the hard way yesterday ab...   Nov 21 2019, 09:19 AM
|||- - gemmathehusky   Personally, I think the cure suggested by MS is as...   Nov 25 2019, 08:00 AM
|||- - theDBguy   Hi Dave. Using the fix I suggested/recommend, I te...   Nov 25 2019, 12:10 PM
|||- - JeffK   ADODB recordset Update calls are breaking for me a...   Dec 3 2019, 09:13 AM
|||- - theDBguy   Hi. Do you know if you have a volume licensed vers...   Dec 3 2019, 07:44 PM
|||- - JeffK   Yes, my Access 2019 is the perpetual license, not ...   Dec 4 2019, 10:40 AM
|||- - theDBguy   Just curious because VL 2019 doesn't have a fi...   Dec 4 2019, 11:26 AM
|||- - rsindle   This is a slightly different spin on this problem....   Dec 4 2019, 02:58 PM
|||- - fizzy1   So, December 10 was 2 days ago. Is all of this mes...   Dec 12 2019, 03:45 PM
|||- - theDBguy   For the most part, yes, but not entirely. It's...   Dec 12 2019, 09:04 PM
|||- - FrankRuperto   QUOTE It's possible subsequent updates could o...   Dec 12 2019, 09:13 PM
|||- - fizzy1   So is this all behind us, and can I revert the cob...   Jan 16 2020, 03:31 PM
|||- - theDBguy   Hi. Yes, you "should be" safe now. Just ...   Jan 16 2020, 03:50 PM
||- - Wedge   That's a start but the others (especially the ...   Nov 21 2019, 07:04 AM
|- - mike60smart   Hi David That worked for me Many thanks   Nov 19 2019, 04:22 PM
|- - FrankRuperto   Uninstalling the security update may temporarily f...   Nov 20 2019, 01:16 PM
|- - isladogs   True but do we know whether the fix includes the s...   Nov 20 2019, 02:10 PM
|- - FrankRuperto   At this point in time we don't know what MS pl...   Nov 20 2019, 05:43 PM
- - Wedge   You have to remove the KBs for each version of Acc...   Nov 13 2019, 04:10 PM
- - Wedge   Further update. Even though you can remove the KB ...   Nov 13 2019, 04:14 PM
|- - FrankRuperto   Disable the Windows Update service in Computer Man...   Nov 13 2019, 10:15 PM
|- - Wedge   Hi Frank. Thanks for the info but not really an op...   Nov 14 2019, 11:36 AM
- - alancossey   More information available at https://support.offi...   Nov 19 2019, 04:26 AM
- - DanielPineault   QUOTE It says that the update for "Access for...   Nov 20 2019, 04:28 PM
- - Wedge   QUOTE MS has pushed out a fix for O365 C2R Monthly...   Nov 21 2019, 03:48 PM
- - theDBguy   Hi All, For what it's worth, I created the at...   Nov 22 2019, 11:50 AM



Custom Search


RSSSearch   Top   Lo-Fi    29th January 2020 - 04:03 AM