Showing results for 
Search instead for 
Do you mean 

MGE data server connection results in 'Unable to connect to the database: a table is empty' error

by Technical Evangelist on ‎04-01-2016 01:30 PM - edited on ‎04-07-2016 05:50 AM by Moderator (321 Views)

Symptoms

When using GeoMedia to make a New Warehouse Connection via the MGE data server an error message is displayed stating:

 

Unable to connect to the database: a table is empty

 

Diagnosis

 

This occurs when attempting to connect to an MGE project when:

  1. none of the design files listed in the MAPS table can be found in the project dgn directory or the directory where DGN PATH is defined.
  2. none of the design files listed in the MAPS table of the MGE project exist.
  3. none of the design files listed in the MAPS table have a category assigned to them (i.e. category field is NULL for all maps.)

Solution

To solve the problem:

  1. Set the DGN PATH: variable in the MGE DATA SERVER .ini file to point to the directory where the design files are stored for the project (in the instance where they are not in the default project directory.)
  2. If the DGN PATH: variable is already in use ensure that it is entered correctly with no extra spaces or other typos. Also ensure that the DGN PATH variable points to all of the directory paths which contain design files including the default project dgn directory if is in use. (Once the DGN PATH variable is defined the software will only look for design files within the listed directory paths.)
  3. Correct the MAPS table by using the MGE Basic Nucleus Tools command called Map Loader to populate the MAPS table with valid entries.
  4. Ensure that at least one of the design files in the MAPS table has the category populated. The MGE Basic Nucleus Tools command Map Manager can be used to populate the category for design files listed in the  MAPS  table.

When none of the design files listed in the 'MAPS' table have a valid type 56 element (i.e. coordinate system), a default coordinate system is assigned on the fly by GeoMedia. This would occur for instance when a design file existed in the maps table (with a valid category) and could be found in the dgn directory, but it did not have a coordinate system (type 56) defined.

Contributors