How to fix Error 773 on Windows 11

by

Why This Error Happens

This error occurs when the OLE DB or ODBC data provider receives a column binding request during a “Getting Data” operation with accessor flags it doesn’t recognize or support (commonly surfaced as error 773 in Windows data connectivity logs). It typically stems from a mismatched or outdated data provider/driver version that doesn’t align with the schema or data types requested by the client application. Corrupted driver files, incompatible 32-bit/64-bit provider installations, or a damaged Microsoft Data Access Components (MDAC) / OLE DB provider cache are the most frequent root causes.

Step-by-Step Resolution Guide

  1. Identify the exact provider being used. Open the application’s connection settings (e.g., in Power BI, Excel Power Query, or an SSIS package) and note the OLE DB/ODBC provider name (e.g., SQLNCLI, MSOLEDBSQL, or a third-party driver).

  2. Update or reinstall the data provider:

  • Go to Control Panel > Programs and Features, locate the provider (e.g., “Microsoft OLE DB Driver for SQL Server”), and uninstall it.
  • Download the latest matching version from Microsoft’s official site and reinstall, ensuring you install both x86 and x64 versions if your applications run in mixed environments.

  1. Verify bitness compatibility. Confirm that the application (Excel, Power BI Desktop, Visual Studio, etc.) and the installed provider match in architecture. Check via C:\Windows\System32 (64-bit drivers) and C:\Windows\SysWOW64 (32-bit drivers) to ensure the correct driver files exist in the expected location.

  2. Clear the ODBC/OLE DB provider cache and re-register the DLL:

  • Open an elevated Command Prompt.
  • Run regsvr32 /u [providername].dll to unregister, then regsvr32 [providername].dll to re-register the provider component.
  1. Repair the Microsoft Data Access Components stack:
  • Run sfc /scannow in an elevated Command Prompt to repair corrupted system files.
  • If using Office-based tools (Excel/Power Query), run Control Panel > Programs > Microsoft Office > Change > Quick Repair, then escalate to Online Repair if the issue persists.

Alternative or Verification Steps

  • Verify the fix: Re-run the original “Getting Data” import/query. If successful without the error message, check the Windows Event Viewer (Applications and Services Logs) to confirm no related warnings were logged during the operation.
  • Alternative fix: If the error persists, switch to a different provider version (e.g., use MSOLEDBSQL instead of the legacy SQLNCLI or SQLOLEDB) in the connection string, as some legacy drivers do not support newer accessor binding flags used by modern applications.