Troubleshooting
Work in this order
Section titled “Work in this order”Run Validate first, then the Design check after a run. Most problems are named for you before you need to diagnose anything.
The order matters, and it is the order the design check itself recommends: connectivity, then slope, then sizing. A model that cannot drain is not worth resizing.
The run fails with an error number
Section titled “The run fails with an error number”The codes below cover almost everything you will meet while building a model. The full list of all 110 codes is searchable by number.
| Code | What SWMM says | What to do |
|---|---|---|
| 200 | one or more errors in input file | A generic wrapper: one or more lines in the input file could not be read. The specific problem is reported alongside it, usually as 203, 205, 207, 209 or 211. |
| 203 | too few items | A line has fewer values than the section requires. A storage node with a shape but no parameters is the usual cause. |
| 205 | invalid keyword name | A keyword is not one SWMM recognises in that position. Check spelling and the allowed set. |
| 207 | duplicate ID name name | Two objects of the same kind share an id. Ids must be unique within their type. |
| 209 | undefined object name | Something references an object that does not exist: a link naming a missing node, an RDII entry naming a missing hydrograph, a pump naming a missing curve. |
| 211 | invalid number name | A value that should be a number is not, or is negative where only positive makes sense. |
| 217 | control rule clause invalid or out of sequence | A control rule could not be parsed. Check the RULE, IF, THEN and PRIORITY clauses. |
| 111 | invalid length for Conduit name | Conduit length must be greater than zero. Check for a conduit created with coincident end points. |
| 112 | elevation drop exceeds length for Conduit name | The drop between the two node inverts is greater than the conduit’s length, which is geometrically impossible. Lengthen the conduit or correct an invert. |
| 115 | adverse slope for Conduit name | The downstream invert is higher than the upstream one. Correct the inverts, or the offsets that lift the pipe off the node floor. |
| 117 | no cross section defined for Link name | Every conduit needs an entry in [XSECTIONS]. Set its cross-section shape and size. |
| 121 | missing or invalid pump curve assigned to Pump name | The curve assigned to the pump is not a pump curve (Pump1 to Pump5), for example a storage or rating curve picked by mistake. A curve name that does not exist raises 209 instead. |
| 122 | startup depth not higher than shutoff depth for Pump name | The pump’s startup depth must be greater than its shutoff depth. |
| 131 | the following links form cyclic loops in the drainage system: | The links listed form a loop. Dynamic-wave routing handles loops, but kinematic wave cannot: switch routing method, or break the loop. |
| 133 | Node name has more than one outlet link | Only dynamic-wave routing allows a node to have more than one outlet link. Switch to DYNWAVE or remove the extra link. |
| 135 | Divider name does not have two outlet links | A flow divider must have exactly two outlet links: the main one and the diverted one. |
| 138 | Node name has initial depth greater than maximum depth | Initial depth cannot exceed maximum depth. Common on storage nodes when the initial level was entered as an elevation rather than a depth. |
| 139 | Regulator name is the outlet of a non-storage node | Under steady or kinematic-wave routing, an orifice, weir or outlet can only discharge from a storage node. Switch to dynamic wave, change the upstream node to storage, or use a conduit. |
| 141 | Outfall name has more than 1 inlet link or an outlet link | An outfall must be a terminal node: exactly one inlet link and no outlet link. |
| 151 | a Unit Hydrograph in set name has invalid time base | The unit hydrograph’s time to peak or recession makes its time base invalid. Check T and K. |
| 153 | a Unit Hydrograph in set name has invalid response ratios | The R values of a unit hydrograph sum to more than 1.0, or one is negative. R is the fraction of rainfall entering the sewer, so the three terms cannot exceed all of it. |
| 155 | invalid sewer area for RDII at node name | The RDII sewershed area must be positive. An area of zero runs but generates no RDII at all. |
| 158 | time series for Rain Gage name is also used by another object | A time series used by a rain gage cannot also be used by an inflow or anything else. Give the gage its own series. |
| 171 | Curve name has invalid or out of sequence data | Curve values must increase monotonically in X. Sort the points and remove duplicates. |
| 173 | Time Series name has its data out of sequence | Time series entries must be in chronological order. |
| 183 | no type specified for LID name | Every LID control needs a type on its first line. |
| 187 | LID area exceeds total area for Subcatchment name | The LID units assigned to a subcatchment cover more area than the subcatchment has. |
| 191 | simulation start date comes after ending date | The simulation start date is after its end date. |
| 195 | reporting time step or duration is less than routing time step | The reporting step cannot be shorter than the routing step. |
Validation catches most of these before you run, and names the element.
The run succeeds but the results are wrong
Section titled “The run succeeds but the results are wrong”Continuity error above 5 percent. Nothing else is worth reading. Shorten the routing step first - it is the cause by a wide margin. Then look for adverse slopes and nodes that cannot drain.
Everything floods. Check the rain gage - an intensity entered as a volume, or the wrong time interval, produces enormous rainfall. Check the units: the flow unit declares the whole model’s system, and it reinterprets rather than converts.
Nothing flows at all. No inflow defined, no rainfall reaching the catchments, or the catchments do not have their outlets set to nodes.
A pipe is always full. Genuine capacity limits, or an adverse slope, or an offset that puts the pipe above the node it drains into.
Something is configured but produces nothing
Section titled “Something is configured but produces nothing”The model will not open
Section titled “The model will not open”Check it is a .inp file and not an .out or .rpt. Very old SWMM 4 files may need
converting. Sections the application does not recognise are preserved rather than dropped,
so an unfamiliar section is not itself a problem.
The model opens but the map is empty
Section titled “The model opens but the map is empty”The model has no [COORDINATES]. It still works, but there is nothing to draw. Use the
Schematic view, or import coordinates from GIS.
The map is in the wrong place
Section titled “The map is in the wrong place”Coordinates are in a projected system that was not recognised. Use Georeference to place the model manually.