Run-time Error 3340: Query " is Corrupt

[John Frazar]

We are still getting a flood of calls from people experiencing the Office Update bug from last week.  Many of you received the update, but probably didn't restart your computer until the weekend and are just now seeing the problem this Monday morning. 

Before calling technical support, please review the following instructions on how to disable automatic Office updates, and uninstall/rollback the Office update from last week;

https://stoneedge.com/kb/articles/query-is-corrupt-fix/

Thank you,

John Frazar

Stone Edge Technologies

[Carlos Chacon]

Under “Instructions for Office 365”, the command "exe /update user updatetoversion=16.0.12130.20272” is not a valid one.  

It is missing “officec2rclient.” from the beginning.  The correct command is:

officec2rclient.exe /update user updatetoversion=16.0.12130.20272

------------------------
Carlos Chacon

--
You received this message because you are subscribed to the Google Groups "Stone Edge User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to stoneedge+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/stoneedge/a6684266-9fee-42be-94c5-0fcaa27b0123%40googlegroups.com.

[John Frazar]

Fixed!  Thanks Carlos!

[Kevin Horowski]

It looks like Microsoft released a Hot Fix for Office 2016 yesterday.  Is there anyone on 2016 that wants to give it a try and report back on whether it works or not?

Also it looks like Microsoft moved up release dates for fixes.

Details about both are in the link below..

https://borncity.com/win/2019/11/19/fix-for-error-3340-in-access-2016-update-kb4484198/

[Henry, Angela]

Hi Kevin

Thanks I was able to follow the directions and resolve the issues.  

Angela Henry 

VP of Operations

Floor Covering Services & Consultants Inc. 

1877floorguy.com | floorconsult.com | hilway.com | kahrsstore.com
ang...@floorconsult.com

office: (302) 221-4138

Like us on Facebook

Follow us on Instagram

--

You received this message because you are subscribed to the Google Groups "Stone Edge User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to stoneedge+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/stoneedge/c81ad81d-88bf-4281-8ad8-a09c99d59d8b%40googlegroups.com.

[Elvis Baez]

Hello to all,

I uninstalled “KB4484127" since we are using Office 2010 but still no luck.

I am getting the Error = 3343: Unrecognized database format on all of my workstations. Please help

To view this discussion on the web visit https://groups.google.com/d/msgid/stoneedge/CAC6vPC0AKoBeQE%3DVBkBpjZyODmoOANr7sFO7XA0PeZr%2BPrPjbw%40mail.gmail.com.

--

Elvis Baez

System Support Specialist

Customer Service/ Shipping Department

 St. Vladimir's Orthodox Theological Seminary

 

e: eb...@svots.edu

w: www.svspress.com

a: 575 Scarsdale Road Tuckahoe New York 10707

 

[Alan Starrett]

We have another wrinkle with this bug.  We started cycling in Windows 10 Pro / Office 2016 machines to replace our Windows 7 Pro / Office 2010 machines given the impending EOL in 2020.  The Office 2016 install is a download direct from Microsoft for each machine.  Two machines were completed before the offending update and we were able to suspend automatic updates before it was installed.  Those machines are working fine.  We started setting up a third machine today and apparently the offending update is part of the current full Office 2016 download as we are getting the 3340 error.  Since it is a fresh install there are no updates to uninstall and the hotfix doesn't work because it says "There are no products affected by this package on this system."  

Alan

[John Frazar]

Alan,

Any chance you can look in the "Downloads" folder on the machines that you updated prior to the bug to see if you have that Office installer?  If not, I would suggest you stick with Windows 7/Office 2010 until after Friday when Microsoft publishes their official fix.   

John

[Kevin Horowski]

Alan,

For the Hotfix are you sure you download the 32 version and not the 64 bit one?  Below is the link to the 32 bit version just in case.

https://www.microsoft.com/en-us/download/details.aspx?id=100596

Also when doing the roll back, I believe it's actually going out to Microsoft to force download the old update/version.  So you should be able to roll it back.  With our instructions though, they were for Office 365, so the version information at the end of Step #6 might be different.

Instead of  16.0.12130.20272  try 16.0.12026.20320

We don't have Office 2016 internally so I can't be 100% certain that will work but that version I mentioned is the one from October 8th.  The only thing I'm not sure of is if it should be 16.0 or some other number.  If you look under Account in an Office application you should see the version info.  Just verify that the first numbers should be 16.0, if not also change them when pasting #6.  We've got the roll back to work for everyone so far, as long as they were running a Click To Run version of Office, but for some people it's just take us a little while to track down the version number that they should be entering.

[Alan Starrett]

Hey John,

Yes, we do have the Office installer from prior to the update.  My only concern using it though is it being a single machine license key and the possibility it won't give me the option to enter a fresh key and invalidate the license on the donor machine.

Alan 

[Alan Starrett]

Hey Kevin,

Yes, we downloaded the 32 bit version of the hotfix and it didn't work.  Fortunately your suggestion of using the Office 365 instructions for a rollback did work.  The version information didn't need to be changed, the 16.0.12130.20272 worked.  It matched the version information on the installer downloaded previous to the bad update.

Alan 

[Brenda Nishimoto]

I run Office365 and here is what I found there....sorry to have bugged you before. Just running the update on each machine (which took a lot of time) fixed the problem. The version causing the problem was 12130.20344 and the version Microsoft updated on 18 Nov 2130.20390 resolved the problem.

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

Thanks guys.

Brenda

[Lawrence Neibauer]

so it looks like we are running MS office 365 Semi-Annual (Version 1902) 11328.20468 and the patch for our version will not be out until the the 25th of November (Hopefully). So far I have lost 2 machines, including my own fortunately I have an old laptop that has been turned off for a while and It didn't get the office updates like some of the other machines so I can run from that for a few days

On Tuesday, November 19, 2019 at 10:32:56 AM UTC-5, Kevin Horowski wrote:

[Lawrence Neibauer]

Update: so the mighty, all knowing and powerful Kevin Horowski gave me a fix for our issue. If you are running a Semi Annual Version 1902 like we were I used these commands to fix the issue

Type or copy & paste:
cd %programfiles%\common files\microsoft shared\clicktorun 

Press Enter 

Then type or copy & paste:

officec2rclient.exe /update user updatetoversion=16.0.11328.20438 (please note the different version number)

Press Enter 

Open up Stone Edge.

Good luck all and thanks Kevin!

[Jerome Hansen]

We are using Access 2013

I turned off automatic updates on one machine when I started getting
these posts. Unfortunately I didn't get to 3 other machines in time.
They started getting the Error 3340: Query...

I wasn't able to roll back the updates using the methods on the
StoneEdge website
https://stoneedge.com/kb/articles/query-is-corrupt-fix/

But, using the info and doing more research, I found the following
method successful. Two of workstations are Windows 7 and the other is
a Windows 10 PC.

------------------
Using - Command Prompt - Run as Administrator

go to directory
C:\Program Files\Microsoft Office 15\ClientX64
.. Note: \Clientx86 on a Windows 10 pc

Then type or copy & paste:

officec2rclient.exe /update user updatetoversion=15.0.5127.1000
--------------------------------------

version 15.0.5127.1000 was the version on the PC that did not get
updated so I used it.

Sincerely,
Jerome Hansen
AlternativeWireless.com, Inc.

> --
> You received this message because you are subscribed to the Google Groups "Stone Edge User Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to stoneedge+...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/stoneedge/eed125dc-aa18-46f8-8131-f98e446e1873%40googlegroups.com.

[Chris Allen]

Thank you Lawrence. We are also on the Semiannual version.

If you know (or if Kevin H is reading along...)  once we run this patch step, can we turn on automatic updates again for Office?

[Chris Allen]

Also, I tried to take this step (manual downgrade) on a (windows 10) test machine, and the Office update process failed, with error code "Something went wrong.  We're sorry, we ran into a problem while looking for updates.  Please check your network connection and try again later.  30125-27 (400)"

Our internet is working fine, so clearly this is something else.

[Chris Allen]

I read that article, and it mentions a fix for Access 2016 via ClickToRun.  I just checked updates on ours, and the latest Access 2016 available (here in US) is still the problematic 20468 build.

On Tuesday, November 19, 2019 at 7:32:56 AM UTC-8, Kevin Horowski wrote:

[Chris Allen]

What worked for us:

I spent much of today dealing with this issue, and have some learnings. Hope it's helpful.

We are using MS Office 2016 365 on Win 7 and 10 machines.  We had turned off automatic updates, but missed a few PCs and they upgraded to the problematic versions today and broke SEOM. Boo. 

We tried the manual downgrade recommended in the Stone Edge KB article, but it did not reliably work for us.  What did work was uninstalling MS Office completely, then reinstalling with the Office Deployment Tool and a custom xml configuration to specify which (working) version of Office we wanted to have installed, and also to turn off automatic updating.  Here are a couple of key articles on how to do that:

https://docs.microsoft.com/en-us/deployoffice/overview-of-the-office-2016-deployment-tool

https://config.office.com/

When running uninstalls and reinstalls, it's important you run with full admin rights and run cmd,exe as administrator.

HTH. -C

[Cathy Wise]

If you use Office 365, which is deployed online (ie, downloaded from office.com) and automatically updates you have to follow the instructions for Click- to -run versions.

 

I’ve successfully rolled back all the PC’s to the version suggested and haven’t had any issues.

 

If you run Office via installation disk – that’s a separate process.

--

You received this message because you are subscribed to the Google Groups "Stone Edge User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to stoneedge+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/stoneedge/38e90c9c-9572-47d9-a2fc-d444b2416f0a%40googlegroups.com.

[Chris Allen]

If I'm reading correctly, Microsoft claims this issue is fixed on all Office versions.

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

Has anyone been brave enough to try this updated version w/ SEOM?

[Alan N. Starrett]

I just installed a fresh download of Office 2016 Pro and so far (fingers crossed) it has been working fine with SEOM.  I don’t remember the build number but I recall it being a higher number than the previously stable version and the problem version.

 

Alan

 

From: ston...@googlegroups.com [mailto:ston...@googlegroups.com] On Behalf Of Chris Allen

Sent: Wednesday, December 11, 2019 4:37 PM
To: Stone Edge User Group

--

You received this message because you are subscribed to the Google Groups "Stone Edge User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to stoneedge+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/stoneedge/13b22199-549c-446d-bfe3-19bcf2065f6d%40googlegroups.com.

[Chris Allen]

Cool, thanks. I'll probably do a test later this week also.

To unsubscribe from this group and stop receiving emails from it, send an email to ston...@googlegroups.com.

[Lawrence Neibauer]

I can confirm that I just upgraded to office 365 access Version 1902 (Build 11328.20492 click to Run) and on a test machine had no issues so far. I am going to put this on a production machine to see how it goes 

[Chris Allen]

I updated a couple of our machines yesterday with the new update, and all seems to be working properly again.  

FWIW, we're running Office 2016 version  1902 (Semi-annual Channel,) and the new build 11328.20492 is working for us.