| E0001
|
Alert definition ID defined in Action is not present in Alert definition list
|
|
| E2000
|
No default run present
|
Info
|
Run
|
|
Cause
|
No Default run has been specified.
|
|
Advice
|
Add a run to the Default Run droptarget of the
Setup page.
|
|
|
|
E2001
|
%1: time fields should be in the form <n><u> where <n> is an integer and <u> is a unit specifier (d, h or m) (and %1 is the name of the invalid field in the schedule)
|
Info
|
Run schedule
|
|
Cause
|
The format of the data entered to specify time field is incorrect in the
Setup page.
|
|
Advice
|
Enter the data using the <n><u> terminology.
|
|
|
|
E2002
|
Invalid alert definition list
|
Info
|
Alert definition list
|
|
Cause
|
The alert definition list has not been successfully
validated.
|
|
Advice
|
Validate the offending alert definition list.
|
|
|
|
E2003
|
No archive folder present
|
Info
|
Archive folder
|
|
Cause
|
No Archive folder has been specified in the Archive section in the
Maintenance page.
|
|
Advice
|
In the Archive section, select a
Live Group to be the Archive folder.
|
|
|
|
E2004
|
Archive after days: The minimum value is 1 day
|
Info
|
Run maintenance
|
|
Cause
|
The value entered in the Archive after days field is invalid in the
Maintenance page.
|
|
Advice
|
This field can only contain a positive integer (zero [0] and alphanumeric characters are not allowed).
|
|
|
|
E2005
|
Delete TVD results after days: cannot delete TVD results until they are archived
|
Info
|
Run maintenance
|
|
Cause
|
InfoWorks ICM has been instructed to delete TVD results before they are archived (Value entered in the Delete TVD results after days field is equal to or less than the value entered in the Archive after days field).
|
|
Advice
|
Review the value entered in the Delete TVD results after days field in the
Maintenance page.
|
|
|
|
E2006
|
The archive is already in use
|
Info
|
Archive folder
|
|
Cause
|
The
Live Group specified in the Archive section of the
Maintenance page is already used as an Archive folder by another manifest.
|
|
Advice
|
Change the Live Group specified in the Archive section. It is advised to use a different archive folder for each manifest.
|
|
|
|
E2007
|
The archive cannot be used because it is a descendant of another archive
|
Info
|
Archive folder
|
|
Cause
|
The
Live Group specified in the Archive section of the
Maintenance page is a child of a Live Group used as an Archive folder by another manifest.
|
|
Advice
|
Change the Live Group specified in the Archive section so it is not a child or a parent of a Live Group already used as an archive folder by another manifest.
|
|
|
|
E2008
|
The archive cannot be used because it is an ancestor of another archive
|
Info
|
Archive folder
|
|
Cause
|
The
Live Group specified in the Archive section of the
Maintenance page is a parent of a Live Group used as an Archive folder by another manifest.
|
|
Advice
|
Change the Live Group specified in the Archive section so it is not a child or a parent of a Live Group already used as an archive folder by another manifest.
|
|
|
| E2009
|
Invalid action list
|
|
|
E2010
|
Invalid path specified for CSV export
|
Info
|
Result export
|
|
Cause
|
The Enable export option has been checked in the
Result CSV export page but no path to the export directory has been specified, or a path that does not exist has been specified.
|
|
Advice
|
Type in or select a path for the export directory in the Target box in the
Result CSV export page.
Tip: The export directory specified in the Target field is used by the following export processes - export of results to
CSV and export graphs and maps to
PNG.
|
|
|
|
E2011
|
Invalid path specified for Graph and Map export
|
Info
|
Result export
|
|
Cause
|
The Enable map export option has been checked in the
Map export page and/or the Enable graph export option has been checked on the
Graph export page, but no path to the export directory has been specified, or a path that does not exist has been specified in the
Map export or
Graph export pages or in the
Result CSV export page.
|
|
Advice
|
Check, and if necessary correct, the path specified in the:
|
|
|
|
E2012
|
Custom graphs on the '<tab name>' tab should be based on the default sim
|
Info
|
Custom Graph
|
|
Cause
|
This error may be caused by:
- A Custom graph, selected in the
Display page, uses a sim that is not the same as the sim specified in the
Setup page.
- The Enable graph export option has been checked in the in
Graph export page, and a Custom graph has been selected that uses a sim that is not the same as the sim specified in the
Setup page.
|
|
Advice
|
Review the Custom graph selected on the tab identified.
Review the simulations specified in the Custom graph.
|
|
|
|
E2013
|
No graphs selected for post event report
|
Info
|
Event report
|
|
Cause
|
The Enable post event report option in the
Post event report page is checked, but no custom graphs have been specified.
|
|
Advice
|
Select a custom graph in the Post event report page.
|
|
|
|
E2014
|
Exported graph size too small
|
Info
|
Event report
|
|
Cause
|
Size X and/or Y values in the
Post event report page have not been specified.
|
|
Advice
|
Review the specified size values on thePost event report page.
|
|
|
|
E2015
|
Time window for run origins too narrow
|
Info
|
Event report
|
|
Cause
|
Run origin fields in the
Post event reportpage are set to the same value.
|
|
Advice
|
Review the specified run origin values on the
Post event report page.
|
|
|
|
E2016
|
Custom graphs on the 'Post event report' tab should be based on the default sim
|
Info
|
Event report
|
|
Cause
|
The Enable post event reportoption has been checked on the
Post event report page, and a Custom graph has been selected that uses a sim that is not the same as the sim specified in the
Setup page.
|
|
Advice
|
Review the Custom graph selected on the
Post event report page.
Review the simulations specified in the Custom graph.
|
|
|
|
E2017
|
No database TSD
|
|
|
E2018
|
Data source not found
|
Info
|
Database export
|
|
Cause
|
A data source specified in the Data source field of the grid in the
Database export page does not exist in the
Scalar time series data object that has been associated with the manifest.
|
|
Advice
|
Ensure that the data source(s) specified in the
Database export page exists in the Data Sources tab of the Scalar TSD object.
|
|
|
|
E2019
|
Database connection failed
|
Info
|
Database export
|
|
Cause
|
There is a connection issue with the database results are to be exported to.
|
|
Advice
|
Check that both the database name and location specified in the Filename / Foldername field of the
Scalar time series data object match the actual name and location of the database results are being exported to.
|
|
|
|
E2020
|
Database table not found
|
Info
|
Database export
|
|
Cause
|
A database table specified in the Table name field of the grid in the
Database export page does not exist in the
Scalar time series data object that has been associated with the manifest.
|
|
Advice
|
Ensure that the database table(s) specified in the
Database export page exist(s) in the database the results are to be exported to.
|
|
|
|
E2021
|
External field [External Field] not found in Table [Table name] in data source [Data Source Name ] for internal field [Internal Field].
|
Info
|
Database export
|
|
Cause
|
A database column (external field) that has been mapped to a
InfoWorks ICM field in the
Database Export Field Mapping Dialog does not exist in the database results are to be exported to.
|
|
Advice
|
Ensure that the database column(s) mapped in the
Database Export Field Mapping Dialog exist(s) in the database the results are to be exported to.
|
|
|
|
E2022
|
Database is read-only
|
Info
|
Database export
|
|
Cause
|
The database results are to be exported to is of the wrong type.
|
|
Advice
|
Check that the database format is a supported type (PI, iHistorian and ClearSCADA types are not supported).
|
|
|
|
E2023
|
No baseline sim selected
|
Info
|
Run
|
|
Cause
|
A baseline simulation has not been selected in the
Setup page.
|
|
Advice
|
Select a simulation in the baseline sim dropdown.
|
|
|
|
E2025
|
Delete full results after days: cannot delete full results until they are archived
|
Info
|
Run maintenance
|
|
Cause
|
InfoWorks ICM has been instructed to delete full results before they are archived. (Value entered in the Delete full results after days field is equal to or less than the value entered in the Archive after days field.)
|
|
Advice
|
Review the value entered in the Delete full results after days field in the
Maintenance page.
|
|
|
|
E2026
|
Delete full results after days: cannot delete full results until TVD results are deleted
|
Info
|
Run maintenance
|
|
Cause
|
InfoWorks ICM has been instructed to delete full results before TVD results are deleted. (Value entered in the Delete full results after days field is equal to or less than the value entered in the Delete TVD results after days field.)
|
|
Advice
|
Review the value entered in the Delete full results after days field in the
Maintenance page.
|
|
|
|
E2027
|
Delete run object after days: cannot delete run objects until they are archived
|
Info
|
Run maintenance
|
|
Cause
|
InfoWorks ICM has been instructed to delete run objects before they are archived. (Value entered in the Delete run objects after days field is equal to or less than the value entered in the Archive after days field.)
|
|
Advice
|
Review the value entered in the Delete run objects after days field in the
Maintenance page.
|
|
|
|
E2028
|
Delete run object after days: cannot delete run objects until TVD results are deleted
|
Info
|
Run maintenance
|
|
Cause
|
InfoWorks ICM has been instructed to delete run objects before TVD results are deleted. (Value entered in the Delete run objects after days field is equal to less than the value entered in the Delete TVD results after days field.)
|
|
Advice
|
Review the value entered in the Delete run objects after days field in the
Maintenance page.
|
|
|
|
E2029
|
Delete run object after days: cannot delete run objects until full results are deleted
|
Info
|
Run maintenance
|
|
Cause
|
InfoWorks ICM has been instructed to delete run objects before full results are deleted. (Value entered in the Delete run objects after days field is equal to less than the value entered in the Delete full results after days field.)
|
|
Advice
|
Review the value entered in the Delete run objects after days field in the
Maintenance page.
|
|
|
|
E2030
|
Parent manifest is invalid. Please validate the parent manifest
|
Info
|
Manifest
|
|
Cause
|
The Parent manifest specified on the
Setup page has not been successfully validated.
|
|
Advice
|
Validate the manifest specified in the Parent manifest field of the
Setup page.
|
|
|
|
E2031
|
Cannot use the current manifest as a parent in the same manifest
|
Info
|
Manifest
|
|
Cause
|
The Parent manifest specified on the
Setup page is the same as the current manifest.
|
|
Advice
|
Select a different manifest in the Parent manifest field in the
Setup page.
|
|
|
| E2032
|
Full run trigger: alert trigger does not exist as a category in the alert definition list
|
Info
|
Run schedule
|
|
Cause
|
The Full run trigger specified in the Run schedule on the
Setup page does not match a category in the
Alert definition list specified.
|
|
Advice
|
Set the Full run trigger to match one of the
Alert definition list categories.
|
|
|
| E2034
|
Variant run trigger: alert trigger does not exist as a category in the alert definition list
|
Info
|
Run schedule
|
|
Cause
|
The Variant run trigger specified in the Run schedule on the
Setup page does not match a category in the
Alert definition list specified.
|
|
Advice
|
Set the Variant run trigger to match one of the
Alert definition list categories.
|
|
|
| E2035
|
Full run trigger: an alert trigger has been specified without an alert definition list
|
|
| E2037
|
Variant run trigger: an alert trigger has been specified without an alert definition list
|
|
| E2038
|
Run variants: Cannot choose to run variants when there is only one simulation contained in the default run
|
Info
|
Run schedule
|
|
Cause
|
The Default run specified on the
Setup page contains one simulation and Run variants has been set to Always or Variant trigger.
|
|
Advice
|
Set Run variants to Never.
|
|
|
| E2044
|
Ground model is required to export flood depths
|
Info
|
Export of flood depths to shape (shp) or image (png) files
|
|
Cause
|
A ground model grid has not been specified.
|
|
Advice
|
Add a
ground model grid to the Ground model grid droptarget on the
Map export page.
|
|
|
| E2045
|
No theme for flood depth export
|
Info
|
Export of flood depths to shape (shp) or image (png) files
|
|
Cause
|
A theme has not been specified.
|
|
Advice
|
Add a theme for the
flood object layer to the Theme droptarget on the
Map export page.
|
|
|
| E2046
|
Verification frequency has been specified without an alert definition list for verification
|
Info
|
Manifest
|
|
Cause
|
A verification frequency has been specified without an alert definition list for verification
|
|
Advice
|
|
|
|
| E2047
|
Triggered verification frequency set without any alerts
|
Info
|
Manifest
|
|
Cause
|
A triggered verification frequency set without any alerts
|
|
Advice
|
.
|
|
|
| E2048
|
The user defined run on device is not allowed because it uses a restricted device name
|
Info
|
Manifest
|
|
Cause
|
The user defined run on device is not allowed because it uses a restricted device name
|
|
Advice
|
|
|
|
| E2049
|
Exports to PI should map timestep, and object id and only 1 attribute
|
Info
|
Database export field mapping
|
|
Cause
|
The required Date/time field, Object ID field and/or an attribute/internal field have not been specified.
|
|
Advice
|
Check that the Date/time field and the Object ID.(on the Info tab), and any internal field/attribute (on any other tab) have been specified. Note that the Date/time field must be set to Timestamp, and the internal field/attribute must be set to Value.
|
|
|
| E2050
|
Exports to PI need a selection list
|
Info
|
Database export
|
|
Cause
|
The export of results to a PI WebAPI database requires a selection list. However, a selection list has not been included in the Selection List box on the
Database export page.
|
|
Advice
|
Add a selection list and ensure that it contains the network objects whose time varying results are to be exported.
|
|
|
| E2051
|
Internal field 'Date/Time' should map to the PI field 'timestamp'
|
Info
|
Database export field mapping
|
|
Cause
|
The Date/time field is not currently set to Timestamp.
|
|
Advice
|
Change the setting of the Date/time field (on the Info tab) to Timestamp.
|
|
|
|
W2000
|
No alert theme present, no alerts will be displayed
|
Info
|
Default theme
|
|
Cause
|
No default theme has been specified.
|
|
Advice
|
Add an alerts theme to the Default theme droptarget in the
Display page.
|
|
|
|
W2001
|
No alert definition list present, no alerts will be displayed
|
Info
|
Alert definition list
|
|
Cause
|
No alert definition list has been specified.
|
|
Advice
|
Add an alert definition list to the Alert definition list drop target in the
Setup page.
|
|
|
|
W2002
|
No areas of interest present, a default will be used
|
Info
|
Selection list
|
|
Cause
|
No area of interest selection list has been specified
|
|
Advice
|
Add an area of interest selection list to the Selection list drop target in the
Display page.
|
|
|
|
W2003
|
An area of interest polygon does not exist in the network of the default sim
|
Info
|
Selection list
|
|
Cause
|
A selection list containing polygons from another network or another version of the network has been specified in the he Selection list droptarget in the
Display page.
|
|
Advice
|
Ensure that the selection list corresponds to the correct network and to the same version of the network used in the associated simulation (Sim droptarget in the
Setup page.
|
|
|
|
W2004
|
No library folder present
|
Info
|
Library folder
|
|
Cause
|
No Library folder has been specified in the Run Library section in the
Maintenance page.
|
|
Advice
|
In the Run Library section, select a
Live Group to be the Library folder.
|
|
|
|
W2007
|
Export is enabled for graphs and maps but none have been selected
|
Info
|
Map export / Graph export
|
|
Cause
|
No Custom Graphs in the
Graph export page, or Maps in the
Map export page, have been selected for export.
|
|
Advice
|
Ensure that at least one custom graph is selected for export in the
Graph export page or one map is selected for export in the
Map export page.
|
|
|
| W2008
|
Run variants: Chosen to run variants with 'Variant trigger' but no variant run trigger has been specified
|
Info
|
Run schedule
|
|
Cause
|
Run variants in the Run schedule grid in the
Setup page has been set to Variant trigger, but a Variant run trigger has not been specified.
|
|
Advice
|
Specify a Variant run trigger, or select another Run variants option in the
Setup page.
|
|
|
| W2009
|
Parent run trigger: A parent manifest has been specified without a parent run trigger
|
Info
|
Run schedule
|
|
Cause
|
A Parent manifest has been selected in the in the
Setup page, but a Parent run trigger has not been specified in the Run schedule grid.
The parent manifest will never trigger the current manifest run schedule.
|
|
Advice
|
In the in the
Setup page, set a Parent run trigger.
|
|
|
