Engine Error Number
|
Description
|
ERROR 101:
|
memory allocation error.
|
ERROR 103:
|
cannot solve KW equations for Link
|
ERROR 105:
|
cannot open ODE solver.
|
ERROR 107:
|
cannot compute a valid time step.
|
ERROR 108:
|
ambiguous outlet ID name for Subcatchment
|
ERROR 109:
|
invalid parameter values for Aquifer
|
ERROR 110:
|
ground elevation is below water table for Subcatchment
|
ERROR 111:
|
invalid length for Conduit
|
ERROR 112:
|
elevation drop exceeds length for Conduit
|
ERROR 113:
|
invalid roughness for Conduit
|
ERROR 114:
|
invalid number of barrels for Conduit
|
ERROR 115:
|
adverse slope for Conduit
|
ERROR 117:
|
no cross section defined for Link
|
ERROR 119:
|
invalid cross section for Link
|
ERROR 121:
|
missing or invalid pump curve assigned to Pump
|
ERROR 131:
|
the following links form cyclic loops in the drainage system:
|
ERROR 133:
|
Node %s has more than one outlet link.
|
ERROR 134:
|
Node %s has illegal DUMMY link connections.
|
ERROR 135:
|
Divider %s does not have two outlet links.
|
ERROR 136:
|
Divider %s has invalid diversion link.
|
ERROR 137:
|
Weir Divider %s has invalid parameters.
|
ERROR 138:
|
Node %s has initial depth greater than maximum depth.
|
ERROR 139:
|
Regulator %s is the outlet of a non-storage node.
|
ERROR 141:
|
Outfall %s has more than 1 inlet link or an outlet link.
|
ERROR 143:
|
Regulator %s has invalid cross-section shape.
|
ERROR 145:
|
Drainage system has no acceptable outlet nodes.
|
ERROR 151:
|
a Unit Hydrograph in set %s has invalid time base.
|
ERROR 153:
|
a Unit Hydrograph in set %s has invalid response ratios.
|
ERROR 155:
|
invalid sewer area for RDII at node
|
ERROR 156:
|
inconsistent data file name for Rain Gage
|
ERROR 157:
|
inconsistent rainfall format for Rain Gage
|
ERROR 158:
|
time series for Rain Gage %s is also used by another object.
|
ERROR 159:
|
recording interval greater than time series interval for Rain Gage
|
ERROR 161:
|
cyclic dependency in treatment functions at node
|
ERROR 171:
|
Curve %s has invalid or out of sequence data.
|
ERROR 173:
|
Time Series %s has its data out of sequence.
|
ERROR 181:
|
invalid Snow Melt Climatology parameters.
|
ERROR 182:
|
invalid parameters for Snow Pack
|
ERROR 183:
|
no type specified for LID
|
ERROR 184:
|
missing layer for LID
|
ERROR 185:
|
invalid parameter value for LID
|
ERROR 186:
|
invalid parameter value for LID placed in Subcatchment
|
ERROR 187:
|
LID area exceeds total area for Subcatchment
|
ERROR 188:
|
LID capture area exceeds total impervious area for Subcatchment
|
ERROR 191:
|
simulation start date comes after ending date.
|
ERROR 193:
|
report start date comes after ending date.
|
ERROR 195:
|
reporting time step or duration is less than routing time step.
|
ERROR 200:
|
one or more errors in input file.
|
ERROR 201:
|
too many characters in input line
|
ERROR 203:
|
too few items
|
ERROR 205:
|
invalid keyword %s
|
ERROR 207:
|
duplicate ID name %s
|
ERROR 209:
|
undefined object %s
|
ERROR 211:
|
invalid number %s
|
ERROR 213:
|
invalid date/time %s
|
ERROR 217:
|
control rule clause out of sequence
|
ERROR 219:
|
data provided for unidentified transect
|
ERROR 221:
|
transect station out of sequence
|
ERROR 223:
|
Transect %s has too few stations.
|
ERROR 225:
|
Transect %s has too many stations.
|
ERROR 227:
|
Transect %s has no Manning's N.
|
ERROR 229:
|
Transect %s has invalid overbank locations.
|
ERROR 231:
|
Transect %s has no depth.
|
ERROR 233:
|
invalid treatment function expression
|
ERROR 301:
|
files share same names.
|
ERROR 303:
|
cannot open input file.
|
ERROR 305:
|
cannot open report file.
|
ERROR 307:
|
cannot open binary results file.
|
ERROR 309:
|
error writing to binary results file.
|
ERROR 311:
|
error reading from binary results file.
|
ERROR 313:
|
cannot open scratch rainfall interface file.
|
ERROR 315:
|
cannot open rainfall interface file
|
ERROR 317:
|
cannot open rainfall data file
|
ERROR 318:
|
date out of sequence in rainfall data file
|
ERROR 319:
|
invalid format for rainfall interface file.
|
ERROR 321:
|
no data in rainfall interface file for gage
|
ERROR 323:
|
cannot open runoff interface file
|
ERROR 325:
|
incompatible data found in runoff interface file.
|
ERROR 327:
|
attempting to read beyond end of runoff interface file.
|
ERROR 329:
|
error in reading from runoff interface file.
|
ERROR 330:
|
hotstart interface files have same names.
|
ERROR 331:
|
cannot open hotstart interface file
|
ERROR 333:
|
incompatible data found in hotstart interface file.
|
ERROR 335:
|
error in reading from hotstart interface file.
|
ERROR 336:
|
no climate file specified for evaporation and/or wind speed.
|
ERROR 337:
|
cannot open climate file
|
ERROR 338:
|
error in reading from climate file
|
ERROR 339:
|
attempt to read beyond end of climate file
|
ERROR 341:
|
cannot open scratch RDII interface file.
|
ERROR 343:
|
cannot open RDII interface file
|
ERROR 345:
|
invalid format for RDII interface file.
|
ERROR 351:
|
cannot open routing interface file
|
ERROR 353:
|
invalid format for routing interface file
|
ERROR 355:
|
mis-matched names in routing interface file
|
ERROR 357:
|
inflows and outflows interface files have same name.
|
ERROR 361:
|
could not open external file used for Time Series
|
ERROR 363:
|
invalid data in external file used for Time Series
|
ERROR 401:
|
general system error.
|
ERROR 402:
|
cannot open new project while current project still open.
|
ERROR 403:
|
project not open or last run not ended.
|
ERROR 405:
|
amount of output produced will exceed maximum file size; either reduce Ending Date or increase Reporting Time Step.
|
Autodesk Technologist with Information about Stormwater Management Model (SWMM) for watershed water quality, hydrology and hydraulics modelers (Note this blog is not associated with the EPA). You will find Blog Posts on the Subjects of SWMM5, ICM SWMM, ICM InfoWorks, InfoSWMM and InfoSewer.
Monday, December 12, 2011
SWMM 5 Error Messages
Subscribe to:
Post Comments (Atom)
Today is day 356 or 97.5 percent of the year 2024
English: Today is day 356 or 97.5 percent of the year 2024 Mandarin Chinese: 今天是2024年的第356天,即97.5% Hindi: आज 2024 का 356वां दिन या 97.5 प्रत...
-
@Innovyze User forum where you can ask questions about our Water and Wastewater Products http://t.co/dwgCOo3fSP pic.twitter.com/R0QKG2dv...
-
Subject: Detention Basin Basics in SWMM 5 What are the basic elements of a detention pond in SWMM 5? They are common in our back...
-
Soffit Level ( pipe technology ) The top point of the inside open section of a pipe or box conduit. The soffit is the ...
27 comments:
Hi, is there a particular message you want more information about? I do reference some of the errors in the other blogs.
thanks for this useful information! Can you provide me some more information on error 353? what is the valid format interface files?
Hi, basically error 353 means you have the wrong number of pollutants, the wrong type of keyword (for example, it looks for the word flow) or values for the interface file locations less than 0
// --- check for correct file type
fgets(line, MAXLINE, Finflows.file);
sscanf(line, "%s", s);
if ( !strcomp(s, "SWMM5") )
{
report_writeErrorMsg(ERR_ROUTING_FILE_FORMAT, Finflows.name);
return;
I keep getting "ERROR 209: undefined object..." about a node I just added. I can't figure out why it's not recognizing the node. Any suggestions?
You should look at the rpt file and it should tell you the last line read.
Here's what is says:
ERROR 209: undefined object IECJ07 at line 4570 of [CONDUIT] section:
1797 3081 IECJ07 50.000000 0.013000 0.000000 0.000000 0.000000 0.000000
ERROR 209: undefined object IECJ07 at line 7513 of [CONDUIT] section:
CDT-15 IECJ07 3082 463.360040 0.013000 0.000000 0.000000 0.000000 0.000000
Where do I find lines 4570 and 7513? I'm not sure I'm looking in the right spot.
Hi,it means the node IECJ07 is not in your model, I would search for in the SWMM 5 input file to make sure or the search the SWMM 5 GUI
Hi,it means the node IECJ07 is not in your model, I would search for in the SWMM 5 input file to make sure or the search the SWMM 5 GUI
I finally figured it out! I just added the node and somehow it was turned off in the facility manager. Working now. Thanks!
Hi i have a broplem on
ERROR 209: undefined object * at line 70 of [SUBCACTCHMENT] section:SBV.07.05
* * 7855.154556 3225 25 6.352525 0.000000 0.000000
Hi Dan,
I think from your snippet it means that you have not defined the name of the raingage? At any rate this message means that some data is missing from the line.
On i have Named the rain station as SP1 . and on the start the error has been seen
Got a bunch of ERROR 115: adverse slope for Conduit errors. Would a negative slope prevent the model from running? My boss thought it would run still.
Hello Genevieve,
If you are using the Kinematic wave solution then you cannot have adverse slopes, if you switch to dynamic wave in Options then it will run - you can run all types of slopes.
I hope this helps.
I keep getting "ERROR 209: undefined object 0 at line 2219 of [INFLOW] section:
99 FLOW 0 FLOW 1.0 1.0 0.07 2. Any suggestions?
Here is what the inflows should look like
[INFLOWS]
;; Param Units Scale Baseline Baseline
;;Node Parameter Time Series Type Factor Factor Value Pattern
;;-------------- ---------------- ---------------- -------- -------- -------- -------- --------
102 FLOW INFLOW@102 FLOW 1.0 1.0
1SB3_MIL FLOW INFLOW@1SB3_MIL FLOW 1.0 1.0
1SB1 FLOW INFLOW@1SB1 FLOW 1.0 1.0
it looks like you have two columns with the name flow or a time series with the name flow
Dear All, I have a real case in simulating the Stormwater system, as described below:
- The Outfall of this system was influenced by tidal regime: 0-12 AM, the maximum of tidal height is + 85m above mean sea level, 13-23 PM that of tide is + 94m. In case, +85 tidal height, the stormwater system can discharge into outfall freely but in case of +94m. the stormwater system was impacted by tide and can not discharge into outfall. So, Please help me to simulate this case by using SWMM Model? Thanks all,
Dear All, I have a real case in simulating the Stormwater system, as described below:
- The Outfall of this system was influenced by tidal regime: 0-12 AM, the maximum of tidal height is + 85m above mean sea level, 13-23 PM that of tide is + 94m. In case, +85 tidal height, the stormwater system can discharge into outfall freely but in case of +94m. the stormwater system was impacted by tide and can not discharge into outfall. So, Please help me to simulate this case by using SWMM Model? Thanks all,
Thanks for this. Is there more information available for Error 185? I have checked each tab in my Bio-Retention control editor, and see no red flags for improper values.
Thanks
Hi i am constantly getting error 363: invalid format of input file. how can I resolve the issue.
I am tryin to see precipitation events.
Thanks yoU,
Hi i am constantly getting error 363: invalid format of input file. how can I resolve the issue.
I am tryin to see precipitation events.
Thanks yoU,
Hi, could you help me please?
ERROR 363: invalid data in external file used for Time Series Lluvia.
Thank you!
Hi, Can you send me your external data to robert.dickinson@gmail.com as there is probably a time or date issue.
HOW CAN I RESOLVE ERROR 329? I AM NEW TO THIS. PLEASE HELP
How did you make your runoff interface file? Is it a valid file?
I KEEP GETTING ERROR 325 AFTER I MODIFY THE EXISTING MODEL. WE RECEIVED THE INTERFACE FILE FROM THE ONE WHO CREATED THE MODEL. THE PRE CONDITION RUN SUCCESSFULLY BUT WHILE I MODIFY IT IN POST CONDITION (I.E. ADDING A NEW SUBBASIN, NODES/LINKS), IT GETS ME ERROR 325.
I RUN 100 YEARS EVENTS SUCCESFULLY IN PRE, I MODIFY THAT FOR POST CONDITION AND IT IS WORKING PERFECTLY. HOWEVER, I GET 325 ERROR IN 25 YEARS & 10 YEARS EVENTS. CAN YOU PLEASE HELP?
Post a Comment