Next: About this document ... Up: GREAT-ER Messages Previous: Warnings

## Errors

Errors indicate that something fundamental has gone wrong. An error may cause serious consequences, especially loss of data. But usually an error message indicates that something previous has failed or was deleted. Hence a GREAT-ER error message is caused by an earlier error.

1.
  `Banner file xxx/graphics/greater.gif not found!`
  This is usually caused by an impossible setting for the system variable %GHOME%. Check if %GHOME% is pointing to your GREAT-ER installation (by using the system settings); if not, set it correctly.

2.
  `The scenario directory named by GSCENARIOS (xxx) does not exist!`
  `Please create the directory and restart GREAT-ER.`
  Create the directory pointed to by %GSCENARIOS% (as indicated in the system settings) and restart GREAT-ER.

3.
  `Cannot get file xxx!`
  Without this file the execution of GREAT-ER is not possible. The problem may in some cases be solved by changing access restrictions. Otherwise the file can be read from the CD by extracting it from the file `greater.zip` on the CD into the directory `%GHOME%\ave`. This message also arises when the set-up has been performed manually using an old version of ZIP that cuts the filenames to the old 8.3 convention. In this case, use the set-up program (recommended) or a newer version of ZIP.

4.
  `Cannot get script load procedure! This makes it impossible to launch GREAT-ER.`
  This indicates that the script `ReloadScript.ave` is not loadable. The problem may in some cases be solved by changing access restrictions. Otherwise `ReloadScript.ave` can be read from the CD by extracting it from the file `greater.zip` on the CD into the directory `%GHOME%\ave`. This message also arises when the set-up has been performed manually using an old version of ZIP that cuts the filenames to the old 8.3 convention. In this case, use the set-up program (recommended) or a newer version of ZIP.

5.
  `Cannot compile load procedure! This makes it impossible to launch GREAT-ER.`
  This indicates that the script has errors, i.e. it has somehow been modified. It needs to be reinstalled by either reinstalling the whole GREAT-ER software or by installing, i.e. extracting, only the scripts that contain errors from the file `greater.zip` on the CD into the directory `%GHOME%\ave`.

6.
  `Error occurred opening script file xxx!`
  The script could not be opened. The problem may in some cases be solved by changing access restrictions. Otherwise `ReloadScript.ave` can be read from the CD by extracting it from the file `greater.zip` on the CD into the directory `%GHOME%\ave`. This message also arises when the set-up has been performed manually using an old version of ZIP that cuts the filenames to the old 8.3 convention. In this case, use the set-up program (recommended) or a newer version of ZIP.

7.
  `Error occurred compiling script xxx!`
  This indicates that the script has errors, i.e. it has somehow been modified. It needs to be reinstalled by either reinstalling the whole GREAT-ER software or by installing, i.e. extracting, only the scripts that contain errors from the file `greater.zip` on the CD into the directory `%GHOME%\ave`.

8.
  `No catchment database found!`
  The essential file `catchments.dbf` is missing. You have to reinstall GREAT-ER or only the file by extracting it from the file `greater.zip`, stored on the CD, to the directory `%GHOME%\catchments`.

9.
  `Internal Error: StretchID field missing!`
  The field to identify river stretches in the simulation result table is missing. Either the field name has been changed manually (it has to be 'stretchid') or the data is seriously corrupt. You should start a new simulation using the same parameters.

10.
  `Catchment CCC can not be opened!`
  The basic catchment data or parts of it are missing. There are three possibilities for this:
  (a)
    You imported a scenario for a catchment you do not have the data for. Check your installation and contact the party from which you obtained the scenario to update your catchment database.
  (b)
    Your catchmant database (under your GREAT-ER installation in the directory 'catchments' and its subdirectories) has the wrong read access restrictions. Change these settings by yourself if possible or ask your system administrator.
  (c)
    Your catchment database is seriously corrupt. Try to restore the catchment data by reinstalling GREAT-ER over your existing installation.
  The essential basic catchment coverages are: catchbound, disch_river, rivernet, discharges.

11.
  `Not able to get information about scenario!`
  The communication between this dialog and the GREAT-ER core application has failed. ARCVIEW has run into an unstable mode. It is recommended to leave GREAT-ER immediately without saving and to restart it.

12.
  `Substance not found! Database seems to be corrupt!`
  Although the substance you have selected is listed in the database there seems to be no data for it. This suggests that the substance's data set, or more generally the substance database itself, is damaged.

13.
  `The result theme data structure seems to be corrupt!`
  The result theme data structure seems to be corrupted. You should try to recreate the scenario and restart the same simulation. If the problem should occur again, one of the needed idfields are missing ...

14.
  `Can not open 'scenario.odb'!`
  The basic scenario settings are not accessible. This may be caused by the wrong access restrictions, which can be fixed by changing them to read/write permission, or by a loss of data. In the latter case you need to reconstruct the scenario and save it again.

15.
  `Wrong number of items in 'scenario.odb'!`
  The basic scenario settings seem to be damaged. This may imply a loss of data. You need to reconstruct the scenario and save it again, preferably using a different name.

16.
  `No view for active scenario!`
  This problem should not normally occur. It indicates that the system has become unstable. You should therefore leave GREAT-ER without saving.

17.
  `Active scenario not found!`
  This problem should not normally occur. It indicates that the system has become unstable. You should therefore leave GREAT-ER without saving. Simulation results are stored under your scenario directory in the files 'pec.dbf' and 'pecstp.dbf'.

18.
  `Scenario data seems to be corrupt!`
  The scenario data structure seems to be seriously corrupt. Saving is no longer possible. Simulation results which you might want to keep are stored under your scenario directory in the files 'pec.dbf' and 'pecstp.dbf'. Exit the scenario without saving.

19.
  `No catchment database found!`
  The essential file `catchments.dbf` is missing. You have to reinstall GREAT-ER or only the file by extracting it from the file `greater.zip`, stored on the CD, to the directory `%GHOME%\catchments`.

20.
  `xxx table fields missing! Function not available.`
  The table seems to be corrupt or has been edited manually. You have to reinstall it by extracting it (a *.dbf file) from the file `greater.zip`, stored on the CD, to the appropriate location in your installation (see Table/Properties for the correct location).

21.
  `QueryString for xxx table has errors!`
  A wrong query string suggests impossible field names and therefore a corrupt table. You have to reinstall the table by extracting it (a *.dbf file) from the file `greater.zip`, stored on the CD, to the appropriate location in your installation (see Table/Properties for the correct location).

22.
  `More than one entry for WWTP! WWTP data table seems to be corrupt.`
  The query to obtain the wwtp data from the database resulted in more than one data record for one wwtp. It may be fixed by manually deleting one of the entries, i.e. by editing the table WWTP data in the Expert mode.

23.
  `Can not find field fff in xxx table! Simulation aborted.`
  The table seems to be corrupt or has been edited manually. You have to reinstall it by extracting it (a *.dbf file) from the file `greater.zip`, stored on the CD, to the appropriate location in your installation (see Table/Properties for the correct location).

24.
  `Required parameter ppp not found in xxx dataset! Simulation aborted.`
  The dataset seems to be corrupt or has been edited manually. You have to reinstall it by extracting it from the file `greater.zip`, stored on the CD, to the appropriate location in your installation.

25.
  `Simulation results: the Csim xxx field was not found!`
  This error should never occur. It suggests that the simulation table has an incorrect structure. If this happens, just delete these simulation results, save the scenario and restart GREAT-ER to repeat your simulation.

26.
  `Csim theme feature table not found!`
  This error should never occur. It suggests that the simulation table has an incorrect structure. If this happens, just delete these simulation results, save the scenario and restart GREAT-ER to repeat your simulation.

27.
  `Can not find table with STP Csims!`
  The scenario data structure seems to be corrupt. This might have been caused by a loss of data or by renaming the result tables. You can check this by looking to see whether the file `CsimSTP.dbf` is in the scenario's directory. The easiest way to fix this is to repeat the simulation.

28.
  `Discharge record not found!`
  The database seems to be corrupt or has been changed manually. You have to reinstall it by extracting it from the file `greater.zip`, stored on the CD, to the appropriate location in your installation.

29.
  `Background data table seems to be corrupt!`
  One of the essential fields "Name", "MapName", "Type", "Legend" has not been found. This means the installation is either corrupt or was changed manually. A reinstallation from the CD is necessary.

30.
  `Necessary script for data set xxx not found!`
  The background data table indicates a special script to be used for displaying the selected data. The script is not loadable, i.e the selected background data can not be displayed. The necessary script is given in the file `backgroundlst.dbf` in the catchment-specific subdirectory of the `overview` directory. The table can be added in the Expert mode to look (and then search for) the script.

31.
  `Error occurred compiling display script xxx!`
  The background data table indicates a special script to be used for displaying the selected data. The script seems to have some errors hence compiling (which is previous to executing) has failed. This makes it impossible to visualise the selected background data automatically. The file must be edited by an AVENUE programmer to fix the error.

32.
  `Background data information not complete!`
  The background information table `backgroundlst.dbf` is not complete. Refer to the technical manual for the required structure, and then look to see whether this is the same for the table which is stored in the catchment-specific subdirectory of the `overview` directory.

33.
  `Unsupported background data format!`
  The background data is of a type not considered in the current implementation. The data can therefore not be displayed. Supported types are point, arc, polygon, shape, grid and image.

34.
  `Cannot make xxx theme!`
  The background theme could not be loaded. Check whether the name and the path given in the background information table `backgroundlst.dbf` are valid. If not, change them (in the Expert-mode) or, more easily, make a complete reinstallation. First, check whether you have read access to the data.

35.
  `Background data not loadable!`
  ODB: either access problems, or a file is missing or corrupt.
  Parts of the background data you selected are missing or unreadable. First check if data is available and change access restrictions if necessary. If the data is missing, try to reinstall GREAT-ER over your existing installation to restore the data. If the data is not part of the original GREAT-ER package, contact the party you received the data from.

36.
  `xxx table not editable! Analysis aborted.`
  This is usually due to access restrictions. You require write access in the directory named by your <TEMP> system variable.

37.
  `Picture theme missing! Function not available.`
  The picture theme is not in the scenario dictionary structure. This implies a corrupt scenario. Create a new scenario using the same catchment. If the error persists, you need to reinstall GREAT-ER over your old installation.

38.
  `Picture theme seems to be corrupt! Function not available.`
  Essential fields are missing, due to corrupt or manually changed data. If the catchment was part of the CD, reinstall GREAT-ER over your old installation. If not, contact the catchment's data provider to enquire how to proceed.

39.
  `Not able to save scenario.odb`

  This is caused by a missing write access in your scenario directory, i.e. a subdirectory under the directory named by your <GSCENARIOS> system variable.

40.
  `Not able to write xxx. Scenario may be corrupt now!`

  This is caused by a missing write access. It may have caused a loss of data.

41.
  `No subcatchment selected in the active scenario.`

  Although the flags report a subcatchment for the active scenario the required information can not be found in the data structures. This suggests the scenario data are damaged. Try to recreate the scenario using a new name.

Next: About this document ... Up: GREAT-ER Messages Previous: Warnings