To see why InfoSewer didn’t run, start with the run manager error message and then check the model setup for data problems, invalid curves, node/link errors, pump and force main issues, and any bad imports from GIS or other sources.

What to check

  • Read the exact error code or message first, because it usually points to the problem area.
  • Check data setup for nodes, links, curves, and peaking parameters, since those are common causes of run failures.
  • Review pump, force main, and flow split settings if your model includes those features.
  • Look for invalid or incomplete data that may have been entered manually or imported incorrectly.
  • If the problem is not obvious from the error, use the built-in help or troubleshooting guide for the specific code.

If the model will not initialize

If you mean the model is not even getting ready to run, one common issue is that the ArcGIS extension for InfoSewer is not enabled, which can leave the initialization button greyed out. In that case, open the ArcGIS Customize menu, check Extensions, and make sure the InfoSewer extension is selected; uncheck and recheck it if needed.

Fast workflow

  1. Open the run message or log.
  2. Match the message to the error guidance.
  3. Check the related model objects: nodes, links, curves, pumps, force mains.
  4. Verify imported data and settings.
  5. Re-run after fixing the flagged issue.

Practical example

If the run complains about a curve or wet well issue, inspect the curve definitions and node data first, because those are specifically called out as common error sources. If the model is simply greyed out and not ready to initialize, fix the extension setting before looking for deeper data problems.

Bottom line

The quickest way to understand why InfoSewer didn’t run is to use the exact error message as your guide, then check the model elements that match that error, especially data entry, imports, curves, and pump/force main setup.