Skip to main content

MyGeotab API - Invalid object name 'OServiceTracking'.

EGarw-2073
Original Poster

This is on a fresh install, following instructions correctly repeatedly. This is with V2

 Microsoft.Data.SqlClient.SqlException (0x80131904): Invalid object name 'OServiceTracking'.

 

Join the conversation

You need to be logged in to reply to this post and participate in the Geotab Community discussions.

6 Replies

Hey @EGarw-2073​,

 

Can you provide some more context please? Is this happening on an API request you're making or are you trying to set up something like the API Adapter?

 

Thanks,

Tucker

EGarw-2073
Original Poster

I'm receiving the error when running the API adapter for the first time. https://docs.google.com/document/d/1Y_9FnHPldeX4_aPViUUOi_8y2UJU1lKcfb1SBnu-lj8/edit?tab=t.0#heading=h.7x3naiv0bkx8

EGarw-2073
Original Poster

That's the first error before it crashes and terminates.

I don't have a ton of experience with DM2. @SteveD-1097​ might be able to help you more with this though if he's available.

EGarw-2073
Original Poster

I found the issue- in the app settings.json - the default setting is for database model 1 instead of 2. I changed it to true and I'm up and running.

 

"DatabaseSettings": {

  "UseDataModel2": true,

 

Hi @EGarw-2073​ ,

This is the correct solution. For anyone else running into similar error messages indicating that tables are missing or columns are missing from tables, there are two possibilities:

  1. The UseDataModel2 setting is not configured to match the data model that was used when setting-up the adapter database (as shown and resolved in the above example).
  2. A newer (upgrade) version of the API Adapter application is being used, but the associated database upgrade scripts have not been run. This is a potential issue with the original data model. With DM2, the application has logic to validate the database version and the error message will explicitly indicate a database version mismatch in this scenario.
Still have questions?