Microsoft Access Query is Corrupt Error 3340

The best way to fix the problem is to uninstall the Security Update for Office which is the source of the problem. The solution is different based on whether your Access installation is from a traditional perpetual license, ACE, or Office 365 subscription.


Perpetual License and Disk Installations of Office/Access, and ACE Distribution Installations

If you installed Access/Office directly on your machine through a perpetual license, local setup program/disk, or distributed the Access Database Engine (ACE), the Security Updates were installed on the machine outside of the Office 365 subscription service. Follow the steps below to find and uninstall the updates:

  1. Press the Windows key and R to bring up the Run prompt.
  2. Type "appwiz.cpl" and press [OK] to launch the Control Panel's Program and Features program.
    Run command
  3. Click [Viewed installed updates].
    View installed updates
  4. In the Search bar, search for the following KB's.
    • Office 2010: KB4484127
    • Office 2013: KB4484119
    • Office 2016: KB4484113
  5. On this system, KB4484127 is present.
  6. Right-click the program, and select [Uninstall].
  7. Click [Yes] to start the uninstall process.
  8. The prompt will ask if you're ready to uninstall. Click the [Uninstall] button to proceed.
  9. Click [OK] when the uninstall of the update was successful.

In our experience, if this uninstalls all the offending security updates, the problem is resolved without a need to reboot.

We will have additional information for Office 365 installations shortly.


Microsoft Office 365Office 365 Subscription (Click to Run) Installations

For Office 365 Users, follow these steps:

  1. Open Office and under “Account” choose the option to disable updates.
  2. Use this link to look up the version of Office that you want to revert to: Update history for Office 365 ProPlus (listed by date)
    For instance, "16.0.12130.20272"
  3. Download the Office Deployment tool (Download)
    Follow the prompts to unzip the files to a folder that’s easily accessible.
  4. In that folder, use Notepad to create a new file named “config.xml” containing:
    <Configuration>
    <Updates Enabled="TRUE" TargetVersion="16.0.12130.20272" />
    </Configuration>			
    
  5. In an elevated command prompt, change directories to the folder where you unzipped the files. Then run the following command:
    setup.exe /configure config.xml
    
  6. Open an Office program and go to the Account page, and “get updates now”.  This reverts back to update 16.0.12130.20272.

Microsoft resource: How to revert to an earlier version of Office 2016 Click-to-Run

How to Remote PowerShell to Office 365 with MFA enabled

Since MFA has become more popular and it's being enabled on more and more tenant account it has presented a problem when connecting to Office 365 via PowerShell in the usual way we've done it for years.

Now, you must download the ExchangeOnline PowerShell Module. This can be done by logging into your Exchange Online GUI, and then from the Hybrid section, click 'Configure' under the MFA section. 

Once you've install the module, you can launch it and then conenct to any tenant by using only your email address in the Connect-EXOPSSession command like this:

Connect-EXOPSSession -UserPrincipalName [email protected]

You will be required to approve your MFA request. Once approved, the PowerShell session conencts as normal. 

Configuring mailbox permissions on a hybrid setup

Really useful stuff here: https://cloudrun.co.uk/exchange-online/configure-exchange-hybrid-mailbox-permissions-during-migration-to-exchange-online/  

 

Run this In powershell/exchange :

 Enable-MailUser stephen.d –ExternalEmailAddress [email protected]

 run following in normal powershell or update via adsiedit.

 

Set-ADUser stephen.d –Replace @{msExchRecipientDisplayType = “-2147483642”}    (default was 6)

Set-ADUser stephen.d –Replace @{msExchRecipientTypeDetails = “2147483648”}   (default was 128)

Set-ADUser stephen.d –Replace @{msExchRemoteRecipientType = “4”}    (default was not set)

Grant Send on Behalf permissions via powershell

Grant Send on Behalf Permissions using Powershell

 
 
We can set or grant send on behalf permission for a exchange mailbox user using the powershell cmdlet Set-Mailbox with the parameter GrantSendOnBehalfTo. Use the below command to set send on behalf permission.
Set-Mailbox "[Identity]" -GrantSendOnBehalfTo @{add="[User]"}
[Identity] - The name of the mailbox user on which the send on behalf permission to be added.
[User] - The user to be granted the send on behalf permission.

The following command grants "Morgan" send on behalf permission to Kevin’s mailbox.
Set-Mailbox "Kevin" -GrantSendOnBehalfTo @{add="Morgan"}
You can also grant permission for multiple users by giving user names as comma separated values.
Set-Mailbox "Kevin" -GrantSendOnBehalfTo @{add="User1","User2"}
The above commands add permission with existing send on behalf permissions and it does not overwrite the existing permissions (this is required for most cases). You can check the applied permissions by using below command.
Get-Mailbox "Kevin" | Select -ExpandProperty GrantSendOnBehalfTo | Select Name,Parent

Grant Send-on-Behalf permission for multiple user mailboxes

We can use the exchange management powershell cmdlet Get-Mailbox to get specific set of user mailboxes and pipe the results to Set-Mailbox cmdlet. The following command grants send on behalf permission for "Morgan" to all the mailboxes.
Get-Mailbox | Set-Mailbox -GrantSendOnBehalfTo @{add="Morgan"}
You can also apply filters in Get-Mailbox cmdlet to select particular set of users. The following command select mailbox users from TestOU and pipe the results to Set-Mailbox cmdlet to set send on behalf rights.
Get-Mailbox | Where {$_.DistinguishedName -like "*OU=TestOU,DC=TestDomain,DC=com*"} |
Set-Mailbox -GrantSendOnBehalfTo @{add="User1","User2"}

VMware Workstation Pro can't run on Windows

This issue occurred around June 2019 for older versions of VMWare Player and Workstation Pro. The reason for the issue is that Microsoft blocked the older versions. Well done Mr Gates.

Fortunatly, there is a way around this. 

Download the Microsoft ADK from here:

Download the Windows ADK for Windows 10, version 1903

Install, and ensure you check the first tool in the installer "Compatibility Tools".

Once installed, launch the "Compatibility Administrator".

Under System Database > Applications > VMWare Workstation Pro

Right-click the .exe entries and disable them.

You're Welcome!