Printable Version of Topic

Click here to view this topic in its original format

UtterAccess Forums _ Access Modules _ 2019-08 Windows Updates May Cause Invalid Procedure Call Error In Vba

Posted by: PhilS Aug 16 2019, 06:03 AM

Hi Everybody!

This is an FYI post. The issue mentioned here cost me a couple of hours yesterday. So, I think it might be worth posting to save you the time diagnosing this issue on your own.

The most recent 2019-08 Windows Updates may cause an "invalid procedure call error" in VBA code. This is not limited to Microsoft Access but affects all VBA-enabled applications.
The problem was acknowledged as a known issue by Microsoft already. Here is a link to one of the KB articles regarding the update. https://support.microsoft.com/en-ph/help/4512508/windows-10-update-kb4512508

This affects all current versions of Office/VBA on both Windows 10 and Windows 8.1. – I did not investigate if Windows 7 is affected as well.
I just published a more extensive text on the https://codekabinett.com/rdumps.php?Lang=2&targetDoc=invalid-procedure-call-error-windows-update-2019-08-august. That text also includes sample code to reproduce the error in two scenarios.

Best regards,
Philipp

Posted by: DanielPineault Aug 16 2019, 07:08 AM

The impact is quite wide spread from certain reports. Someone just reported it impacted "Access 2003 developer extension". Dismal quality control, nothing new, it is the norm with Microsoft - Release ASAP and update again and again and again... crazy.gif

It's blunder after blunder (Windows, Office, ...). Worse is that they (i) don't immediately stop the rollout of the update when initially reported, (ii) are extremely slow to release fixes (see: https://support.office.com/en-us/article/access-reports-that-databases-are-in-an-inconsistent-state-%ef%bb%bf-7ec975da-f7a9-4414-a306-d3a7c422dc1d?ui=en-US&rs=en-US&ad=US - More than a year waiting!). They don't need competitors, they are their own worse enemy!



If you rollback/revert the update everything works properly again. Until which time Microsoft makes an update for the update to address this latest of bugs.

Posted by: GroverParkGeorge Aug 16 2019, 07:35 AM

I think we need to put a link to this post on the front page. I'll check with the admin team.

Posted by: DanielPineault Aug 16 2019, 07:46 AM

Since we're at it, here's yet more links on the subject:


According to one person, the issue is due to https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1182 and thus the update/bug would possibly impact Windows 7 through 10 and Server 2008 through 2019.


This is even now hit mainstream media, see:

Posted by: LeeAnn Aug 16 2019, 08:01 AM

Thanks for the update. I work for a company that is always on top of getting updates to us as soon as they can. I have not heard of any problems so far but I am going to keep my eyes open.

I want to take a few moments and say I apricate all I have learned from here. I don't post too much here but the ones I have posted I know have been some interesting ones (especially the last one pertaining an issue with jpgs being displayed on Dot Net Nuke, it has been solved but it was a crazy way to do it and I would have not been able to figure out without the help here, even though the solution was not given but it made me look at things in a way I would have not looked without getting the wonderful assistance here).

Thanks again and I wish all of you a wonderful day. grinhalo.gif

Leeann Christine Davidson

Posted by: DanielPineault Aug 16 2019, 07:00 PM

Apparently Microsoft released a fix (KB4512494) today to address the issue, see: https://support.microsoft.com/en-us/help/4512494/windows-10-update-kb4512494

Posted by: PhilS Aug 17 2019, 05:03 AM

QUOTE
Apparently Microsoft released a fix (KB4512494) today to address the issue ...

That's a start!
However, this fix seems to apply to Windows 10, Version 1709 only. There is no similar update for newer versions of Windows 10, let alone Windows 7 and 8, yet.

The oldest version of Windows 10 I've got still installed is version 1803 and there I get this message already:
QUOTE
You're currently running a version of Windows that's nearing the end of support. We recommend you update to the most recent version of Windows 10 now to get the latest features and security improvements.

In the light of the fix to this issue being only available for an even older version of Windows 10 this feels somewhat like mockery.
On the other hand, maybe they are just pushing a canary into the coal mine with this most recent update...

Well, criticism aside, it is very good news that Microsoft is actively working on this. Let's hope there will be similar fixes for other versions of Windows next week.

Posted by: DanielPineault Aug 17 2019, 06:24 AM

There's also this one for Windows 8.1 and Windows Server 2012 R2

https://support.microsoft.com/en-us/help/4517298/windows-8-1-update-kb4517298

and there's this one for Windows 7 SP1 and Windows Server 2008 R2 SP1

https://support.microsoft.com/en-us/help/4517297/windows-7-update-kb4517297


it's a nightmare to try and find them all, but for Windows 10, you seem to be right that only 1709 appears to have an update available to resolve the issue currently. very odd.

Posted by: PhilS Aug 17 2019, 08:14 AM

QUOTE
and there's this one for Windows 7 SP1 and Windows Server 2008 R2 SP1

Great! - I didn't find that.
But they seem to have been in such a hurry, that they put a wrong link to the download into that article. Here is the correct one: http://www.catalog.update.microsoft.com/Search.aspx?q=kb4517297

Edit:
I just installed the Windows 8.1 patch and it fixes all known incarnations of the issue.

Posted by: wrmosca Aug 20 2019, 09:18 AM

This is why I don't develop in Access anymore. I can't count on it to work. I've moved on to Epic healthcare systems. Bugs reported are corrected in days.

Posted by: DanielPineault Aug 20 2019, 05:49 PM

Hey Bill, what do you do about Windows 10?! shrug.gif


QUOTE
This is why I don't develop in Access anymore. I can't count on it to work.

I've lost one of my biggest clients due to continual issue with A2016-O365 and just finish migrating another client to a PHP based system to get away from the continual issues/downtime. I find myself pulled more and more towards anything other than Access because of all the issues whether it be Windows 10 or O365, there always seems to be something. I also find MS slow to even acknowledge issues, little alone fix them (with the exception of this current one). Where I waas doing 95% Access development, I now find myself doing maybe 35% in Access these days. It's sad and entirely Microsoft's own fault.

Posted by: wrmosca Aug 21 2019, 12:08 PM

Daniel - The only thing I use Windows for is to run PuTTY sessions to the Linux servers. And my employer and I are still on Windows 7.

Posted by: SemiAuto40 Oct 8 2019, 09:02 AM

What may I ask is the other 65% development in?

Posted by: Lewis-H Nov 7 2019, 03:27 AM

I encountered two different, although related, scenarios were the “Invalid procedure call or argument” error occurs due to the installed update. Both are related to empty arrays. can anyone tell me what are they?

Regards,
Lewis

Posted by: PhilS Nov 7 2019, 04:16 AM

QUOTE
I encountered two different, although related, scenarios were the “Invalid procedure call or argument” error occurs due to the installed update. Both are related to empty arrays. can anyone tell me what are they?

The first two sentences are a quote from https://codekabinett.com/rdumps.php?Lang=2&targetDoc=invalid-procedure-call-error-windows-update-2019-08-august. The explanation what those scenarios are follows immediately after those sentences.


Posted by: RCollard Nov 13 2019, 12:14 PM

And Windows update strikes again! We have gotten a half dozen reports of "query is corrupted" errors in the last two hours. See

https://www.computerworld.com/article/3453322/patch-tuesday-arrives-with-access-error-1909-in-tow-and-a-promise-of-no-more-optional-patches-this.html and

https://borncity.com/win/2019/11/13/office-november-2019-updates-are-causing-access-error-3340/

Posted by: RCollard Nov 13 2019, 12:31 PM

Official fix is a month away?

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

Posted by: isladogs Nov 13 2019, 12:31 PM

I'm having problems with both links in post #16.
They appear briefly and disappear again followed by a message 'This page is having trouble loading.
Do the links work OK for other people?

Posted by: GroverParkGeorge Nov 13 2019, 01:10 PM

Yes, they both loaded for me.

Maybe you are a victim of the bug? (just kidding)

Posted by: theDBguy Nov 13 2019, 01:15 PM

Hi. The links worked for me too. Cheers!

Posted by: PhilS Nov 13 2019, 01:29 PM

Here's my https://codekabinett.com/rdumps.php?Lang=2&targetDoc=query-corrupt-error-access-update-november-2019-11.