Next: Errors Up: GREAT-ER Messages Previous: Hints

## Warnings

Warnings are given if something has gone wrong. These are different to errors in the sense that they do not cause a loss of data and may be resolved with the use of the technical documentation.

1.
  `Environment variable <GHOME> not set.`
  Although this environment variable needed by GREAT-ER (specifying the GREAT-ER home directory) is set by the set-up program, it is now missing (maybe deleted manually). A following dialog enables you to specify the home directory for the current GREAT-ER session but it is recommended to set the variable permanently with the system settings.

2.
  `Environment variable <GSCENARIOS> not set.`
  Although this environment variable needed by GREAT-ER (specifying the GREAT-ER sceanrio directory) is set by the set-up program, it is now missing (maybe deleted manually). A following dialog enables you to specify the home directory for the current GREAT-ER session but it is recommended to set the variable permanently with the system settings.

3.
  `No unit information available. Unit is set to [mg/L]. Please check your system / scenario parameters!`
  For some reason the automatic unit conversion has failed. The simulator output is [mg/L] so it is assumed that the loaded data is in this unit. Please check this assumption. This message also appears when no release of the substance has been specified (e.g. a catchment with only industrial discharges and no site-specific release).

4.
  `GREAT-ER menu not found.`
  The GREAT-ER menu structure seems to be corrupt. This can happen by modifying the structure in the Expert Mode. A rough solution is to leave GREAT-ER without saving anything. If you want to save your scenario data you have to restore the menu structure: See the ARCVIEW manual for customising a project. Check the menus for the View Doc. Rename the one which contains the usual GREAT-ER commands back to "`&GREAT-ER`".

5.
  `Exit item not found.`
  The GREAT-ER menu structure seems to be corrupted. This could happen by modifying the structure in the Expert Mode. A rough solution is to leave GREAT-ER. You may save your scenarios before leaving. An alternative is to restore the menu structure: See the ArcView manual for customising a project. Look for the GREAT-ER menu for the View Doc. Scan through the menu items and find the item with the click script ExitGREAT-ER.ave Rename it to "`E&xit`".

6.
  `Not able to fully delete the scenario. The scenario may now be invalid.`
  `Possible reason is access violation.`
  Because of some file access limitations GREAT-ER was not able to delete the scenario data completely. Probably one of the files in the directory is still opended by another program. Please close the file and remove remaining scenario data by deleting the scenario directory manually.

7.
  `Creation of export file xxx failed.`
  Because of some access limitiations the automatic generation of the export file is not possible. You might try to change the access restrictions and export again or to export the scenario manually: as all scenario data are stored in the related directory under the GREAT-ER scenario directory the export file is a zip archive of this subdirectory. You can create this archive with you favorite zip tool.

8.
  `Importing of file xxx failed.`
  Because of some access limitiations the automatic unpacking of the export file is not possible. You might try to change the access restrictions and import again or to import the scenario manually: as all scenario data are stored in the related directory under the GREAT-ER scenario directory the export file is a zip archive of this subdirectory. You can unpack this archive with you favorite unzip tool to the scenario directory.

9.
  `Neither CAS nor Name specified.`
  The last edits have been lost because the data set has no CAS or name, which are the minimum requirements to identify a substance data set.

10.
  `Not able to open database - keeping previous.`
  Two reasons are possible here: Either, due to access limitations, the database is not accessible or the database has somehow been deleted, which should not be the case.

11.
  `River network theme missing. Function not available.`
  The river network theme can not be found, which means it is no longer a theme of the active view or it has been renamed. The easy-to-use way to fix both is to save and close the scenario and reopen it. When using the expert mode the problem can be solved by adding the river network theme to the active view or by renaming it to "River Net" in the Theme/Properties window.

12.
  `Discharge sites theme missing. Function not available.`
  The discharge site theme can not found, which means it is no longer a theme of the active view or it was renamed. The easy-to-use mode way to fix both is to save and close the scenario and reopen it. When using the expert mode the problem can be solved by adding the rivernet theme to the active view or by renaming it again to "River Net" in the Theme/Properties window.

13.
  `Discharge table is not editable.`
  This is due to access restrictions. To enable the discharge table to become editable the access rights need to be changed.

14.
  `xxx : can not be opened for writing.`
  This is due to access restrictions and can be solved by changing them. This "warning" involves no loss of data.

15.
  `The table of simulation results is not editable. Calculation of background concentration xxx aborted.`
  This is due to access restrictions and can be solved by changing them.

16.
  `Csim theme feature table has errors.`

  One of the fields QMean, Reallength, VMean or PECintMean is missing in the theme's feature table, probably due to the fields having been renamed manually. This edit need to be undone. A second possibility may be that the field is hidden. This can be fixed by unhiding the field within the Expert mode.

17.
  `The table of simulation results is not editable. Calculation of xxx-percentile aborted.`
  This is due to access restrictions and can be solved by changing them.

18.
  `The theme's legend is not as required for PEC's. Profile plotting aborted.`
  The current legend classification is based on more than one field. This is not possible for profile plotting. Switch to the one field which should be used for plotting the profile.

19.
  `Background data table not found.`
  The table that contains information about additional background data can not be found. This indicates that the catchment installation routine did not work correctly or the table has been deleted or renamed manually. The file `backgroundlst.dbf` needs to be in the directory `%GHOME%\catchments\<CATCHMENT>`.

20.
  `Background data list could not be created.`
  This is an internal AVENUE error which should not normally occur. Nothing has to be done and no data can get lost. Just try to reload the background data.

21.
  `DCW coverage can not be opened.`
  One or more of the coverages pppoly, pppoint, rdline, rrline can not be opened. Check whether the coverages are in the directory `%GHOME%\overview\<COUNTRY>`. This may be the case if a scenario with a catchment from a new country has been included. In this case the DCW data need to be included in the directory `%GHOME%\overview\<COUNTRY>`.

22.
  `Your scenario data is incomplete: no model parameters.`
  You have to edit the model parameters to specify all necessary ones, This warning is caused by cancelling the model parameter dialog during the creation of a new scenario.

23.
  `Picture of xxx (yyy) not found.`
  The image file of the picture can not be found. It may be deleted or renamed. Go into the expert mode and check the database by loading the attribute table of the Site Pictures theme ( via Themes/Table...) and then looking whether the image file name corresponds to a file in the directory `%GHOME%\graphics\sitepics`. If there are some inconsistencies, eliminate them.

24.
  `Not able to save scenario in xxx - directory already exists.`
  As saving is not possible to a directory of another scenario, go back to the "Save As" dialog and specify a nonexisting directory. It will be created automatically.

25.
  `Not able to create directory`
  This is due to access restrictions and can be solved by changing them.

Next: Errors Up: GREAT-ER Messages Previous: Hints