Skip to content

Troubleshooting

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 codes below cover almost everything you will meet while building a model. The full list of all 110 codes is searchable by number.

CodeWhat SWMM saysWhat to do
200one or more errors in input fileA 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.
203too few itemsA line has fewer values than the section requires. A storage node with a shape but no parameters is the usual cause.
205invalid keyword nameA keyword is not one SWMM recognises in that position. Check spelling and the allowed set.
207duplicate ID name nameTwo objects of the same kind share an id. Ids must be unique within their type.
209undefined object nameSomething 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.
211invalid number nameA value that should be a number is not, or is negative where only positive makes sense.
217control rule clause invalid or out of sequenceA control rule could not be parsed. Check the RULE, IF, THEN and PRIORITY clauses.
111invalid length for Conduit nameConduit length must be greater than zero. Check for a conduit created with coincident end points.
112elevation drop exceeds length for Conduit nameThe drop between the two node inverts is greater than the conduit’s length, which is geometrically impossible. Lengthen the conduit or correct an invert.
115adverse slope for Conduit nameThe downstream invert is higher than the upstream one. Correct the inverts, or the offsets that lift the pipe off the node floor.
117no cross section defined for Link nameEvery conduit needs an entry in [XSECTIONS]. Set its cross-section shape and size.
121missing or invalid pump curve assigned to Pump nameThe 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.
122startup depth not higher than shutoff depth for Pump nameThe pump’s startup depth must be greater than its shutoff depth.
131the 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.
133Node name has more than one outlet linkOnly dynamic-wave routing allows a node to have more than one outlet link. Switch to DYNWAVE or remove the extra link.
135Divider name does not have two outlet linksA flow divider must have exactly two outlet links: the main one and the diverted one.
138Node name has initial depth greater than maximum depthInitial depth cannot exceed maximum depth. Common on storage nodes when the initial level was entered as an elevation rather than a depth.
139Regulator name is the outlet of a non-storage nodeUnder 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.
141Outfall name has more than 1 inlet link or an outlet linkAn outfall must be a terminal node: exactly one inlet link and no outlet link.
151a Unit Hydrograph in set name has invalid time baseThe unit hydrograph’s time to peak or recession makes its time base invalid. Check T and K.
153a Unit Hydrograph in set name has invalid response ratiosThe 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.
155invalid sewer area for RDII at node nameThe RDII sewershed area must be positive. An area of zero runs but generates no RDII at all.
158time series for Rain Gage name is also used by another objectA time series used by a rain gage cannot also be used by an inflow or anything else. Give the gage its own series.
171Curve name has invalid or out of sequence dataCurve values must increase monotonically in X. Sort the points and remove duplicates.
173Time Series name has its data out of sequenceTime series entries must be in chronological order.
183no type specified for LID nameEvery LID control needs a type on its first line.
187LID area exceeds total area for Subcatchment nameThe LID units assigned to a subcatchment cover more area than the subcatchment has.
191simulation start date comes after ending dateThe simulation start date is after its end date.
195reporting time step or duration is less than routing time stepThe 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”

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 has no [COORDINATES]. It still works, but there is nothing to draw. Use the Schematic view, or import coordinates from GIS.

Coordinates are in a projected system that was not recognised. Use Georeference to place the model manually.