Back

“Invalid object name ‘dbo.EXT01000’ or “An open operation on the table ‘EXT_Extender_Activity’ cannot find table data” when installing Extender in New Company

Published: Feb 05, 2025
Post Author Written by Amit Chaudhari

After configuring a new Microsoft Dynamics GP Company, the extender setup is triggered during the first login attempt, which opens the ‘Install Extender’ window automatically. This window displays a list of companies, including the new one, and allows you to select the new company for installing tables, loading from the cache, etc. However, for some reason, the extender table EXT01000 (EXT_Extender_Activity) is not created due to:

  1. The table is somehow damaged
  2. Logged into GP using an account other than ‘sa’
  3. Logged into GP while other users were already logged in

We would encounter the following errors every time after logging in.

  1. [Microsoft][SQL Server Native Client 11.0][SQL Server]Could not find stored procedure ‘TWO.dbo.zDP_EXT01000L_2’.
  2. [Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid object name ‘TWO.dbo.EXT01000’.
  3. An operation on table ‘EXT_Extender_Activity” cannot find table data.
  4. A remove range operation on table ‘EXT_Extender_Activity’ cannot find the table

If you’d like to watch a video explaining this, see below or click here.

Here’s the solution:

Ensure that everyone is logged out of Dynamics GP

  1. Verify you have a backup of your Dynamics and company databases.
  2. Log in to Dynamics GP as the ‘sa’ user in a company where the Extender Windows is functioning correctly.
  3. Go to Microsoft Dynamics GP – Maintenance – SQL. Change the product to Extender and select the database where the EXT01000 table is missing. Highlight ONLY the Extender Activity table, then check the boxes on the right for “Drop Table,” “Create Table,” “Drop Auto Procedure,” and “Create Auto Procedure.” Your window should appear like this but with your database shown instead of the TWO Database.
  4. Before clicking Process, make sure that only the correct table is highlighted. Then, click the Process button, which will drop (if needed) and recreate the table and stored procedures for the affected company. After that, try logging into the company in GP and the error should be resolved.
SQL Maintainance

Have a question? Please reach out to us at support@eonesolutions.com

Feeling stuck? Get the support and guidance you need to help you power through any data challenge

We're on your integration team. Connect with our people and let us know how we can help you.