A centralized view of error events for diagnostics and maintenance
A centralized view of error events for diagnostics and maintenance
Memory allocation error
There is not enough physical memory in the computer to analyze the study area.
Cannot solve KW equations for Link xxx
The internal solver for Kinematic Wave routing failed to converge for the specified link at some stage of the simulation.
Cannot open ODE solver
The system could not open its Ordinary Differential Equation solver.
Cannot compute a valid time step
A valid time step for runoff or flow routing calculations (i.e., a number greater than 0) could not be computed at some stage of the simulation.
Ambiguous outlet ID name for Subcatchment xxx
The name of the element identified as the outlet of a subcatchment belongs to both a node and a subcatchment in the project's data base.
Invalid parameter values for Aquifer xxx
The properties entered for an aquifer object were either invalid numbers or were inconsistent with one another (e.g., the soil field capacity was higher than the porosity).
Ground elevation is below water table for Subcatchment xxx
The ground elevation assigned to a Subcatchment's groundwater parameters cannot be below the initial water table elevation of the aquifer object used by the Subcatchment.
Invalid length for Conduit xxx
Conduits cannot have zero or negative lengths.
Invalid roughness for Conduit xxx
Conduits cannot have zero or negative roughness values.
Invalid number of barrels for Conduit xxx
Conduits must consist of one or more barrels.
Adverse slope for Conduit xxx
Under Steady or Kinematic Wave routing, all conduits must have positive slopes. This can usually be corrected by reversing the inlet and outlet nodes of the conduit (i.e., right click on the conduit and select Reverse from the popup menu that appears). Adverse slopes are permitted under Dynamic Wave routing.
No cross section defined for Link xxx
Cross section geometry was never defined for the specified link.
Invalid cross section for Link xxx
Either an invalid shape or invalid set of dimensions was specified for a link's cross section.
Missing or invalid pump curve assigned to Pump xxx
Either no pump curve or an invalid type of curve was specified for a pump.
The following links form cyclic loops in the drainage system
The Steady and Kinematic Wave flow routing methods cannot be applied to systems where a cyclic loop exists (i.e., a directed path along a set of links that begins and ends at the same node). Most often the cyclic nature of the loop can be eliminated by reversing the direction of one of its links (i.e., switching the inlet and outlet nodes of the link). The names of the links that form the loop will be listed following this message.
Node xxx has more than one outlet link
Under Steady and Kinematic Wave flow routing, a junction node can have only a single outlet link.
Node xxx has illegal DUMMY link connections
Only a single conduit with a DUMMY cross-section or Ideal-type pump can be directed out of a node; a node with an outgoing Dummy conduit or Ideal pump cannot have all of its incoming links be Dummy conduits and Ideal pumps; a Dummy conduit cannot have its upstream end connected to a storage node.
Divider xxx does not have two outlet links
Flow divider nodes must have two outlet links connected to them.
Divider xxx has invalid diversion link
The link specified as being the one carrying the diverted flow from a flow divider node was defined with a different inlet node.
Weir Divider xxx has invalid parameters
The parameters of a Weir-type divider node either are non-positive numbers or are inconsistent (i.e., the value of the discharge coefficient times the weir height raised to the 3/2 power must be greater than the minimum flow parameter).
Node xxx has initial depth greater than maximum depth
Self-explanatory.
Regulator xxx is the outlet of a non-storage node
Under Steady or Kinematic Wave flow routing, orifices, weirs, and outlet links can only be used as outflow links from storage nodes.
Outfall xxx has more than 1 inlet link or an outlet link
An outfall node is only permitted to have one link attached to it.
Regulator xxx has invalid cross-section shape
An orifice must have either a CIRCULAR or RECT_CLOSED shape, while a weir must have either a RECT_OPEN, TRAPEZOIDAL, or TRIANGULAR shape.
Drainage system has no acceptable outlet nodes
Under Dynamic Wave flow routing, there must be at least one node designated as an outfall.
A Unit Hydrograph in set xxx has invalid time base
The time base of a Unit Hydrograph cannot be negative and if positive, must not be less than the recording interval for its rain gage.
A Unit Hydrograph in set xxx has invalid response ratios
The response ratios for a set of Unit Hydrographs (the short-, medium-, and longterm response hydrographs) must be between 0 and 1.0 and cannot add up to a value greater than 1.0
Invalid sewer area for RDII at Node xxx
The sewer area contributing RDII inflow to a node cannot be a negative number.
Inconsistent data file name for Rain Gage xxx
If two Rain Gages use files for their data sources and have the same Station IDs then they must also use the same data files.
Inconsistent rainfall format for Rain Gage xxx
If two or more rain gages use the same Time Series for their rainfall data then they must all use the same data format (intensity, volume, or cumulative volume).
Time series for Rain Gage xxx is also used by another object
A rainfall Time Series associated with a Rain Gage cannot be used by another object that is not also a Rain Gage.
Recording interval greater than time series interval for Rain Gage xxx
The recording time interval specified for the rain gage is greater than the smallest time interval between values in the Time Series used by the gage.
Cyclic dependency in treatment functions at Node xxx
An example would be where the removal of pollutant 1 is defined as a function of the removal of pollutant 2 while the removal of pollutant 2 is defined as a function of the removal of pollutant 1.
Curve xxx has invalid or out of sequence data
The X-values of a curve object must be entered in increasing order.
Time Series xxx has its data out of sequence
The time (or date/time) values of a time series must be entered in sequential order.
Invalid Snow Melt Climatology parameters
The ATI Weight or Negative Melt Ratio parameters are not between 0 and 1 or the site latitude is not between -60 and +60 degrees.
Invalid parameters for Snow Pack xxx
A snow pack's minimum melt coefficient is greater than its maximum coefficient; the fractions of free water capacity or impervious plowable area are not between 0 and 1; or the snow removal fractions sum to more than 1.0.
No type specified for LID xxx
A named LID control has layers defined for it but its LID type was never specified.
Missing layer for LID xxx
A required design layer is missing for the specified LID control.
Invalid parameter value for LID xxx
An invalid value was supplied for an LID control's design parameter.
LID area exceeds total area for Subcatchment xxx
The area of the LID controls placed within the Subcatchment is greater than that of the Subcatchment itself.
LID capture area exceeds total impervious area for Subcatchment xxx
The amount of impervious area assigned to be treated by LID controls in the Subcatchment exceeds the total amount of impervious area available.
Simulation start date comes after ending date
Self-explanatory.
Report start date comes after ending date
Self-explanatory.
Reporting time step is less than routing time step
Self-explanatory.
One or more errors in input file
This message appears when one or more input file parsing errors (the 200-series errors) occur.
Too many characters in input line
A line in the input file cannot exceed 1024 characters.
Too many characters in input line
A line in the input file cannot exceed 1024 characters.
Too few items at line n of input file
Not enough data items were supplied on a line of the input file.
Invalid keyword at line n of input file
An unrecognized keyword was encountered when parsing a line of the input file.
Duplicate ID name at line n of input file
An ID name used for an object was already assigned to an object of the same category.
Undefined object xxx at line n of input file
A reference was made to an object that was never defined. An example would be if node 123 were designated as the outlet point of a Subcatchment, yet no such node was ever defined in the study area.
Invalid number xxx at line n of input file
Either a string value was encountered where a numerical value was expected or an invalid number (e.g., a negative value) was supplied.
Invalid date/time xxx at line n of input file
An invalid format for a date or time was encountered. Dates must be entered as month/day/year and times as either decimal hours or as hour:minute:second.
Control rule clause out of sequence at line n of input file
Errors of this nature can occur when the format for writing control rules is not followed correctly (see Section C.3).
Data provided for unidentified transect at line n of input file
A GR line with Station-Elevation data was encountered in the [TRANSECTS] section of the input file after an NC line but before any X1 line that contains the transect's ID name.
Transect station out of sequence at line n of input file
The station distances specified for the transect of an irregular cross section must be in increasing numerical order starting from the left bank.
Transect xxx has too few stations
A transect for an irregular cross section must have at least 2 stations defined for it.
Transect xxx has too many stations
A transect cannot have more than 1500 stations defined for it.
Transect xxx has no Manning's N
No Manning's N was specified for a transect (i.e., there was no NC line in the [TRANSECTS] section of the input file.
Transect xxx has invalid overbank locations
The distance values specified for either the left or right overbank locations of a transect do not match any of the distances listed for the transect's stations.
Transect xxx has no depth
All of the stations for a transect were assigned the same elevation.
Invalid treatment function expression at line n of input file
A treatment function supplied for a pollutant at a specific node is either not a correctly formed mathematical expression or refers to unknown pollutants, process variables, or math functions.
Files share same names
The input, report, and binary output files specified on the command line cannot have the same names.
Cannot open input file
The input file either does not exist or cannot be opened (e.g., it might be in use by another program).
Cannot open report file
The report file cannot be opened (e.g., it might reside in a directory to which the user does not have write privileges).
Cannot open binary results file
The binary output file cannot be opened (e.g., it might reside in a directory to which the user does not have write privileges).
Error writing to binary results file
There was an error in trying to write results to the binary output file (e.g., the disk might be full or the file size exceeds the limit imposed by the operating system).
Error reading from binary results file
The command line version of SWMM could not read results saved to the binary output file when writing results to the report file.
Cannot open scratch rainfall interface file
SWMM could not open the temporary file it uses to collate data together from external rainfall files.
Cannot open rainfall interface file xxx
SWMM could not open the specified rainfall interface file, possibly because it does not exist or because the user does not have write privileges to its directory.
Cannot open rainfall data file xxx
An external rainfall data file could not be opened, most likely because it does not exist.
Date out of sequence in rainfall data file xxx
An external user-prepared rainfall data file must have its entries appear in chronological order. The first out-of-order entry will be listed.
Unknown format for rainfall data file
SWMM could not recognize the format used for a designated rainfall data file.
Invalid format for rainfall interface file
SWMM was trying to read data from a designated rainfall interface file with the wrong format (i.e., it may have been created for some other project or actually be some other type of file).
No data in rainfall interface file for gage xxx
This message occurs when a project wants to use a previously saved rainfall interface file, but cannot find any data for one of its rain gages in the interface file. It can also occur if the gage uses data from a user-prepared rainfall file and the station id entered for the gage cannot be found in the file.
Cannot open runoff interface file xxx
A runoff interface file could not be opened, possibly because it does not exist or because the user does not have write privileges to its directory.
Incompatible data found in runoff interface file
SWMM was trying to read data from a designated runoff interface file with the wrong format (i.e., it may have been created for some other project or actually be some other type of file).
Attempting to read beyond end of runoff interface file
This error can occur when a previously saved runoff interface file is being used in a simulation with a longer duration than the one that created the interface file.
Error in reading from runoff interface file
A format error was encountered while trying to read data from a previously saved runoff interface file.
Cannot open hot start interface file xxx
A hot start interface file could not be opened, possibly because it does not exist or because the user does not have write privileges to its directory.
Incompatible data found in hot start interface file
SWMM was trying to read data from a designated hot start interface file with the wrong format (i.e., it may have been created for some other project or actually be some other type of file).
Error in reading from hot start interface file
A format error was encountered while trying to read data from a previously saved hot start interface file.
No climate file specified for evaporation and/or wind speed
This error occurs when the user specifies that evaporation or wind speed data will be read from an external climate file, but no name is supplied for the file.
Cannot open climate file xxx
An external climate data file could not be opened, most likely because it does not exist.
Error in reading from climate file xxx
SWMM was trying to read data from an external climate file with the wrong format.
Attempt to read beyond end of climate file xxx
The specified external climate does not include data for the period of time being simulated.
Cannot open scratch RDII interface file
SWMM could not open the temporary file it uses to store RDII flow data.
Cannot open RDII interface file xxx
An RDII interface file could not be opened, possibly because it does not exist or because the user does not have write privileges to its directory.
Invalid format for RDII interface file
SWMM was trying to read data from a designated RDII interface file with the wrong format (i.e., it may have been created for some other project or actually be some other type of file).
Cannot open routing interface file xxx
A routing interface file could not be opened, possibly because it does not exist or because the user does not have write privileges to its directory.
Invalid format for routing interface file xxx
SWMM was trying to read data from a designated routing interface file with the wrong format (i.e., it may have been created for some other project or actually be some other type of file).
Mismatched names in routing interface file xxx
The names of pollutants found in a designated routing interface file do not match the names used in the current project.
Inflows and outflows interface files have same name
In cases where a run uses one routing interface file to provide inflows for a set of locations and another to save outflow results, the two files cannot both have the same name.