You encountered the error “A get/change operation on table ‘EXT_Extender_Windows’ failed accessing SQL data.” when upgrading Extender.
If you’d like to watch the video that goes with this, see below or click here.

The More Info button shows the following:

[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name ‘Extender_Field_IDs_16’.
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name ‘Extender_Field_IDs_17’.
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name ‘Extender_Field_IDs_18’.
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name ‘Extender_Field_IDs_19’.
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name ‘Extender_Field_IDs_20’.
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name ‘Extender_Field_IDs_21’.
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name ‘Extender_Field_IDs_22’.
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name ‘Extender_Field_IDs_23’.
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name ‘Extender_Field_IDs_24’.
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name ‘Extender_Field_IDs_25’.
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name ‘Extender_Field_IDs_26’.
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name ‘Extender_Field_IDs_27’.
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name ‘Extender_Field_IDs_28’.
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name ‘Extender_Field_IDs_29’.
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name ‘Extender_Field_IDs_30’.
This error generally occurs when updating from Microsoft Dynamics GP and Extender 2016 or 2018 to 18.2 or newer.
With the release of Extender 18.2, 15 new fields were added to the Extender window tables. This means:
- Extender 2018 and earlier versions had only 15 fields
- Extender 18.2 and later versions now have 30 fields
So, the issue is likely one of the following:
The stored procedures weren’t updated and are still referencing the version with only 15 fields.
OR
The table (EXT20100) itself wasn’t updated to include the new fields.
Resolution
The first thing you need to do is verify if it is the table or the procedures that have an issue.
To do this run the following SQL Statement against your company database.
SELECT Extender_Field_IDs_16 from EXT20100
- If the query returns data and does not error, then the issue is likely with the stored procedures—the column exists in the table but not in the procedures.
To resolve this, run SQL Maintenance in Microsoft Dynamics GP by following these steps:
- Make a SQL backup of your company database that is erroring in the upgrade.
- Log in to Microsoft Dynamics GP as the ‘sa’ user.
- Navigate to Microsoft Dynamics GP > Maintenance > SQL.
- Change the Product to Extender, and select the database where you’re encountering the error.
- Press Ctrl + A to highlight all tables.
- Check only the boxes for “Drop Auto Procedure” and “Create Auto Procedure”.
- Do not select any tables—we only want to update the procedures.
- Click the Process button.

Once the SQL Maintenance completes, check to see if the error has been resolved.
——————————————————————————
- If the column doesn’t exist in the table at all, you’ll need to run the Extender upgrade for that company. To do this:
- Log in as the ‘sa’ user.
- Navigate to Tools > Extender > Maintenance > Upgrade Extender.
- Run the upgrade process in the company where the error is occurring.
——————————————————————————
If the Extender upgrade error message persists, we may need to review the EXT20100 backup table, then recreate it through maintenance and restore it using a SQL script. If this is the case, please contact us at support@eonesolutions.com for assistance.
Check out more help articles for information on how to troubleshoot other issues.