Below are listed errors that may occur in SWMM when import, export or calculate
| Runtime Errors | |
|---|---|
| 101 | of memory allocation.
There is not enough physical memory on the computer to analyze the study area. |
| 103 | Cannot solve KW equations for Link xxx.
The internal solver for kinematic wave routing failed to converge to the specified link at some stage of the simulation. |
| 105 | cannot open ODE solver.
The system could not open your Ordinary Differential Equation solver. |
| 107 | cannot calculate a valid time step.
A valid time step for flow or flow routing calculations (that is, a number greater than 0) could not be calculated at some stage of the simulation. |
| Errors in Properties | |
| 108 | ambiguous outlet identification name for subcatchment xxx.
The name of the element identified as the output of a subcatchment belongs to both a node and a subcatchment in the project database. |
| 109 | Invalid parameter values for Aquifer xxx.
The properties entered for an aquifer object were invalid numbers or inconsistent with each other (for example, soil field capacity was greater than porosity). |
| 110 | ground elevation is below the water table for Subcatchment xxx.
The ground elevation attributed to the groundwater parameters of a subcatchment cannot be below the initial water table elevation of the aquifer object used by the subcatchment. |
| 111 | Invalid length for Conduit xxx.
Conduits cannot have zero or negative lengths. |
| 112 | Elevation drop exceeds Conduit xxx length.
The elevation drop at the ends of a conduit cannot be greater than the length of the conduit. Check for errors in the length and elevations and reversed offsets at the upstream and downstream nodes of the conduit. |
| 113 | Invalid roughness for Conduit xxx.
Conduits cannot have zero or negative roughness values. |
| 114 | Invalid number of barrels for Conduit xxx.
Ducts must consist of one or more barrels. |
| 115 | adverse slope for Conduit xxx.
In Steady Wave or Kinematic routing, all conduits must have positive slopes. This can usually be fixed by reversing the conduit's entry and exit nodes (ie, right-clicking the conduit and selecting Flip from the pop-up menu that appears). Adverse slopes are allowed in dynamic wave routing. |
| 117 | No cross section defined for Link xxx.
A cross section geometry has never been defined for the specified link. |
| 119 | Invalid cross section for Link xxx.
An invalid shape or invalid set of dimensions was specified for a link cross section. |
| 121 | Missing or invalid pump curve assigned to Pump xxx.
No pump curve or an invalid curve type was specified for a pump. |
| 131 | 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 (that is, a directed path along a set of links that starts and ends at the same node) exists. Most of the time, the cyclic nature of the loop can be eliminated by reversing the direction of one of its links (that is, switching the link's input and output nodes). The names of the links that form the loop will be listed after this message. |
| 133 | Node xxx has more than one outgoing link.
In constant-wave and kinematic flow routing, a junction node can have only a single output link. |
| 134 | Node xxx has illegal DUMMY link connections.
Only a single conduit with a DUMMY cross section or Ideal type pump can be routed out of a node; a node with an output dummy conduit or ideal pump cannot have all of its input links be dummy conduits and ideal pumps; a dummy conduit cannot have its upstream end connected to a storage node. |
| 135 | The xxx Divider is missing two outgoing links.
Flow Divider nodes must have two outgoing links connected to them. |
| 136 | Divider xxx has an invalid branch link.
The link specified as the one carrying flow diverted from a flow Divider node was defined with a different input node. |
| 137 | Weir Divider xxx has invalid parameters.
The parameters of a Weir-type Divider node are non-positive numbers or are inconsistent (ie, the value of the discharge coefficient times the weir height raised to the power of 3/2 must be greater than the minimum flow parameter). |
| 138 | Node xxx has initial depth greater than maximum depth.
Self explanatory. |
| 139 | The regulator xxx is the output of a node without storage.
In streaming or kinematic wave routing, orifices, weirs, and outbound links can only be used as outbound links from storage nodes. |
| 140 | Storage node xxx has negative volume at full depth.
This can occur when the surface area curve of a storage node slopes downward at its highest depth, which is below the total depth of the node. |
| 141 | Outfall xxx has more than 1 inbound link or 1 outbound link.
An output node can only have one link attached to it. |
| 143 | The regulator xxx has an invalid cross-sectional shape.
An orifice must have a CIRCULAR or RECT_CLOSED shape, while a weir must have a RECT_OPEN, TRAPEZOID, or TRIANGULAR shape. |
| 145 | The drainage system does not have acceptable outlet nodes.
In Dynamic Wave flow routing, there must be at least one node designated do as an outfall. |
| 151 | a Unit Hydrograph in set xxx has an invalid time base.
The time base of a Unit Hydrograph cannot be negative and, if positive, it must not be less than the recording interval of your pluviometer. |
| 153 | a Unit Hydrograph in set xxx has invalid response rates.
The response ratios for a set of unit hydrographs (the short-, medium-, and long-term response hydrographs) must be between 0 and 1.0 and cannot add up to a value greater than 1.0 |
| 155 | Invalid sewer area for ISDN on Node xxx.
The sewer area that contributes the inflow of ISDN to a node cannot be a negative number. |
| 156 | Inconsistent data file name for Rain Gage xxx.
If two Rain Gages use files for their data sources and have the same station IDs, they must also use the same data files. |
| 157 | inconsistent rain format for Rain Gage xxx.
If two or more Rain Gages use the same Time Series for their rainfall data, they must all use the same data format (intensity, volume, or cumulative volume). |
| 158 | The time series for Rain Gage xxx is also used by another object.
A rain time series associated with a rain gage cannot be used by an object other than a rain gage. |
| 159 | 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 the Time Series values used by the rain gage. |
| 161 | Cyclic dependency on handling 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. |
| 171 | Curve xxx has its data out of sequence.
The X values of a curve object must be entered in ascending order. |
| 173 | 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. |
| 181 | Invalid Snow Melt Climatology parameters.
The ATI Weight or Negative Melt Ratio parameters are not between 0 and 1, or the location's latitude is not between -60 and +60 degrees. |
| 182 | Invalid parameters for Snow Pack xxx.
The minimum melting coefficient of a snowpack is greater than its maximum coefficient; fractions of free water capacity or impermeable washable area are not between 0 and 1; or snow removal fractions add up to more than 1.0. |
| 183 | no type specified for LID xxx.
A named LID control has layers defined for it, but its LID type has never been specified. |
| 184 | layer missing for LID xxx.
A required design layer is missing for the specified LID control. |
| 185 | Invalid parameter value for LID xxx.
An invalid value was provided for the design parameter of a LID control. |
| 187 | The LID area exceeds the total area for Subcatchment xxx.
The area of the LID controls placed within the subcatchment is larger than that of the subcatchment itself. |
| 188 | The catchment area of the LID exceeds the total impermeable area for Subcatchment xxx.
The amount of impermeable area designated to be treated by LID controls in the subcatchment exceeds the total amount of impermeable area available. |
| 191 | The simulation start date comes after the end date.
Self explanatory. |
| 193 | The start date of the report comes after the end date.
Self explanatory. |
| 195 | The reporting time interval is less than the routing time interval.
Self explanatory. |
| File format errors | |
| 200 | one or more errors in the input file.
This message appears when one or more input file parsing errors (the 200 series errors) occur. |
| 201 | Too many characters on input line.
A line in the input file cannot exceed 1024 characters. |
| 203 | Too few items on line n of the input file.
Not enough data items were provided on one line of the input file. |
| 205 | Invalid keyword on line n of input file.
An unrecognized keyword was encountered while parsing a line in the input file. |
| 207 | Duplicate ID name on line n of input file.
An ID name used for an object has already been assigned to an object of the same category. |
| 209 | undefined object xxx on line n of input file.
A reference was made to an object that was never defined. An example would be if node 123 is designated as the exit point of a subcatchment, but no such node is defined in the study area. |
| 211 | Invalid number xxx on line n of input file.
A string value was found where a numerical value was expected or an invalid number (for example, a negative value) was supplied. |
| 213 | Invalid timestamp xxx on 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 decimal hours or as hour:minute:second. |
| 217 | out-of-sequence control rule clause on line n of input file.
Errors of this nature can occur when the format for writing control rules is not followed correctly (see Control Rule Format). |
| 219 | data provided for unidentified transect on line n of input file.
A GR line with Station Elevation data was found in the [TRANSECTS] section of the input file after an NC line, but before any X1 lines containing the transect ID name. |
| 221 | cross station out of sequence on line n of input file.
The station distances specified for the transect of an irregular cross section must be in ascending numerical order from the left edge. |
| 223 | Transect xxx has few stations.
A transect for an irregular cross section must have at least 2 stations defined for it. |
| 225 | Transect xxx has many stations.
A transect cannot have more than 1500 stations defined for it. |
| 227 | Transect xxx has no Manning N.
No Manning N was specified for a transect (that is, there was no NC line in the [TRANSECTS] section of the input file. |
| 229 | Transect xxx has invalid overbank locations.
The distance values specified for the left or right edge locations of a transect do not match any of the distances listed for stations on the transect. |
| 231 | Transect xxx has no depth.
All stations for a transect were assigned the same elevation. |
| 233 | Invalid handler function expression at line n of input file.
A treatment function provided for a pollutant at a specific node is not a correctly formed mathematical expression or refers to unknown pollutants, process variables or mathematical functions. |
| File Errors | |
| 301 | the files share the same names.
The input, report, and binary output files specified on the command line cannot have the same names. |
| 303 | cannot open input file.
The input file does not exist or cannot be opened (for example, it may be in use by another program). |
| 305 | Cannot open report file.
The report file cannot be opened (for example, it may reside in a directory where the user does not have write privileges). |
| 307 | cannot open binary results file.
The binary output file cannot be opened (for example, it may reside in a directory where the user does not have write privileges). |
| 309 | when writing to binary results file.
An error occurred while trying to write the results to the binary output file (for example, the disk may be full or the file size exceeds the limit imposed by the operating system). |
| 311 | when reading the binary results file.
The command line version of SWMM was unable to read the results saved in the binary output file when writing the results to the report file. |
| 313 | cannot open zero rain interface file.
SWMM could not open the temp file it uses to gather data from external rain files. |
| 315 | cannot open xxx rain interface file.
SWMM could not open the specified rain interface file, possibly because it does not exist or because the user does not have write privileges on his directory. |
| 317 | cannot open rain data file xxx.
An external rainfall data file could not be opened, probably because it does not exist. |
| 318 | data out of sequence in rainfall data file xxx.
A rainfall data file prepared by the external user must have its entries displayed in chronological order. The first entry out of order will be listed. |
| 319 | unknown format for rain data file.
SWMM could not recognize the format used for a designated rainfall data file. |
| 320 | Invalid format for rain interface file.
SWMM was trying to read data from a designated rain interface file with the wrong format (ie it may have been created for some other project or actually be some other type of file). |
| 321 | no data in rain 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. |
| 323 | cannot open xxx flow interface file.
A runoff interface file could not be opened, possibly because it does not exist or because the user does not have write privileges on its directory. |
| 325 | Mismatched data found in flow interface file.
SWMM was trying to read data from a flow interface file designated with the wrong format (ie it may have been created for some other project or actually be some other type of file). |
| 327 | trying to read past the end of the flow interface file.
This error can occur when a previously saved flow interface file is being used in a simulation that lasts longer than the one that created the interface file. |
| 329 | on reading the flow interface file.
A format error was encountered when trying to read data from a previously saved flow interface file. |
| 331 | cannot open warm boot interface file xxx.
A hotstart interface file could not be opened, possibly because it does not exist or because the user does not have write privileges on its directory. |
| 333 | Mismatched data found in warm boot interface file.
SWMM was trying to read data from a designated hotstart interface file with the wrong format (ie it may have been created for some other project or actually be some other type of file). |
| 335 | in reading the warm boot interface file.
A format error was encountered when trying to read data from a previously saved hotstart interface file. |
| 336 | no Climate File specified for evaporation and/or wind speed.
This error occurs when the user specifies that evaporation data or wind speed will be read from an external Climate File, but no name is given for the file. |
| 337 | cannot open Climate File xxx.
An external weather data file could not be opened, probably because it does not exist. |
| 338 | when reading Climate File xxx.
SWMM was trying to read data from an external Climate File with the wrong format. |
| 339 | Attempt to read past end of Climate File xxx.
The specified outdoor weather does not include data for the time period being simulated. |
| 341 | Cannot open draft RDII interface file.
SWMM could not open the temporary file it uses to store RDII stream data. |
| 343 | 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 on its directory. |
| 345 | Invalid format for RDII interface file.
SWMM was trying to read data from a designated RDII interface file with the wrong format (ie it may have been created for some other project or actually be some other type of file). |
| 351 | 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 on its directory. |
| 353 | Invalid format for routing interface file xxx.
SWMM was trying to read data from a designated routing interface file with the wrong format (ie it may have been created for some other project or actually be some other type of file). |
| 355 | mismatched names in routing interface file xxx.
Pollutant names found in a designated routing interface file do not match the names used in the current project. |
| 357 | The input and output interface files have the same name.
In cases where an execution uses one routing interface file to provide input streams to a set of locations and another to save output stream results, the two files cannot have the same name. |
| 361 | Could not open external file used for Time Series xxx.
The external file used to provide data for the named time series could not be opened, probably because it does not exist. |
| 363 | Invalid data in external file used for Time Series xxx.
The external file used to provide data for the named time series has one or more rows with the wrong format. |
| Warning Messages | |
| 01 | Rainfall time step reduced to logging interval for Rain Gage xxx.
The rain time step was automatically shortened so that no wet periods were skipped during a simulation. |
| 02 | Increased maximum depth for Node xxx.
The maximum depth for the node was automatically raised to match the top of the tallest connecting conduit. |
| 03 | Negative offset ignored for Link xxx.
The stipulated offset of the link was below the inversion of the connection node, so its actual offset was set to 0. |
| 04 | Minimum elevation drop used for Conduit xxx.
The elevation drop between the end nodes of the conduit was below 0.001 feet (0.00035 m), so the latter value was used to calculate its slope. |
| 05 | Minimum slope used for Conduit xxx.
The calculated conduit slope was below the user-specified minimum conduit slope, so the latter value was used. |
| 06 | Time step from dry weather increased to time step from wet weather.
The user-specified time step for calculating runoff during dry weather periods was less than that defined for wet weather periods and was automatically increased to the wet weather value. |
| 07 | Reduced routing time step for rainy weather.
The user-specified time step for flow routing was greater than the wet weather flow time step and was automatically reduced to the flow time step to avoid loss of accuracy. |
| 08 | Elevation drop exceeds Conduit xxx length.
The elevation drop at the ends of a conduit exceeds its length. The program calculates the conduit slope as the elevation drop divided by the length instead of using the more accurate right triangle method. The user should check for errors in length and inverted elevations and offsets at the upstream and downstream nodes of the conduit. |
| 09 | time series interval greater than logging interval for Rain Gage xxx.
The smallest time interval between entries in the rainfall time series used by the rain gage is greater than the specified recording time interval for the gage. If this was not really intended, what appear to be continuous periods of rain in the time series will be read with time gaps in between. |
| 10 | crest elevation is below the downstream inversion for the Link xxx regulator.
The height of the opening in an orifice, dam, or outlet is below the inverted elevation of its downstream node. Users should check whether the governor offset height or inverted elevation of the downstream node is wrong. |
| 11 | mismatched attributes in Control Rule xxx.
The premise of a control rule is to compare two different types of attributes against each other (eg, conduit flow and junction water depth). |