Runtime messages

These messages may be displayed while a simulation is being processed. Many of them are for information but some are serious warnings. All warnings should be checked and investigated if necessary.

Key to Messages

Left Column	The error message number is used internally by InfoWorks. This number is unique, and may be useful when contacting Autodesk Support.
Centre Column	Name: The error or warning message that is displayed and written out to the Log File. When the simulation is complete, you can view the log results in a separate window. Info: Additional information about the error or warning, such as the name of the network object where the anomaly occurred Cause: Why the message has been displayed Advice: What, if anything, you need to do about it.
Right Column	Information only - no further action needed Warning - action may be required Error - action necessary

List of Runtime Messages

The blue text is the actual text that will be displayed in the log file. Click the blue text for further information.

022	Pumps cannot provide PST Duty Head Info Pumping Station name, duty head required and duty head provided. Cause The combination of pumps cannot provide the required duty head. Advice InfoWorks WS will use the available head, so no computational inaccuracy will occur. Check the pump data for the pumping station.
024	Monthly Demand Coefficients are not normalised for category Info Name of the Demand Category Cause The sum of all twelve monthly coefficients is not twelve, and therefore the annual average will not be 1. Advice You should generally give normalised values for these coefficients, although you are allowed to enter arbitrary values.
025	Weekly Demand Coefficients are not normalised for category Info Name of the Demand Category Cause The sum of all seven daily coefficients is not seven, and therefore the weekly average will not be 1. Advice You should generally give normalised values for these coefficients, although you are allowed to enter arbitrary values.
038	Number of equations and system coeff's Info Number of equations and system coefficients (measure of the size of matrix to be solved). Average bandwidth (no. of equations / no. of coefficients). Maximum bandwidth (after network reorganisation to minimise matrix bandwidth and number of coefficients to be calculated in each iteration). Cause For information Advice For information only. No action required.
041	HYDRANT node must have SINGLE connection Info Node name Cause Node to which hydrant control has been applied is connected to more than one link. Advice Check that hydrant control has been applied to correct node. Add node with short link to network to model hydrant.
042	HYDRANT node cannot be Reservoir/Fixed Head Info Node name Cause Node to which hydrant control has been applied is a Reservoir or a Fixed Head node. Advice Check that hydrant control has been applied to correct node. Add node with short link to network to model hydrant.
043	Hydrant ignored - available flow = 0 (disabled), Node Info Node name Cause Hydrant opening percentage has been specified as zero. Advice This may be intentional. If not, check hydrant opening percentage.
046	No Reservoir/FixHead in disconnected network part(s) Info Number of disconnected networks Cause One or more disconnected networks does not contain a means of calculating head. Advice Ensure that each disconnected network contains a Reservoir of Fixed Head Node.
047	Network has disconnected parts Info Number of disconnected networks Cause Network contains two or more disconnected sections. Advice For information only. No action required.
106	Control - INITIAL time must be less than FINAL! Info Start Time and End Time of simulation Cause The Start Time specified in the Hydraulic Run Schedule is later than the End Time. Advice Amend Start Time / End Time of simulation
411	PST - Control policy table is empty, PST is OFF Info Name of the pumping station Cause The pump control data sheet is empty or there are no available pumps in the pumping station. All the pumps in the pumping station are set to OFF. Advice Make sure a control policy is defined for each pumping station in the Control Set and run the simulation again.
436	PST Flow is set too high Info Pump name, flow set, PST nominal flow Cause The flow profile specified for a PST in FLOW control mode is outside of the PST defined curve range. Advice Check pump curves are correct. Check specified flow is correct. Replace pumps in station with more suitable units.
442	Pipe permanently closed/unavailable Info Pipe name Cause Pipe is closed due to pipe control. Advice For information only. No action required.
448	No pipe specified for Hydrant target point Info None Cause Missing parameter in the Fire Flow Options dialog when running a Forced Fire Flow simulation. The Insert FF_Target_Point node in pipe option has been selected in the Fire Flow Options dialog, but a pipe ID has not been entered. Advice Check the parameters in the Fire Flow Options dialog (accessed via the Schedule Hydraulic Run View).
449	Hydrant target point not found in network Info None Cause Incorrect parameter in the Fire Flow Options dialog when running a Forced Fire Flow simulation. The Insert FF_Target_Point node in pipe option has been selected in the Fire Flow Options dialog and a pipe ID that does not exist in the network has been entered. Advice Check the parameters in the Fire Flow Options dialog (accessed via the Schedule Hydraulic Run View).
450	No node specified for Hydrant target point Info None Cause Missing parameter in the Fire Flow Options dialog when running a Forced Fire Flow simulation. The Use existing node option has been selected in the Fire Flow Options dialog, but a node ID has not been entered. Advice Check the parameters in the Fire Flow Options dialog (accessed via the Schedule Hydraulic Run View).
451	Hydrant target point node not found in network Info None Cause Incorrect parameter in the Fire Flow Options dialog when running a Forced Fire Flow simulation. The Use existing node option has been selected in the Fire Flow Options dialog, and a node ID that does not exist in the network has been entered. Advice Check the parameters in the Fire Flow Options dialog (accessed via the Schedule Hydraulic Run View).
452	Close pipe option will be ignored Info None Cause Unexpected option selected in the Fire Flow Options dialog when running a Forced Fire Flow simulation. The Close connected pipe option has been selected in the Fire Flow Options dialog, but the node selected as the hydrant target point does not have a "From" link and a "To" link. Advice Check the parameters in the Fire Flow Options dialog (accessed via the Schedule Hydraulic Run View).
453	Hydrant target point split pipe distance too small Info None Cause Distance along pipe parameter defined in the Fire Flow Options dialog (when running a Forced Fire Flow simulation) is too small. The Insert FF_Target_Point node in pipe option has been selected in the Fire Flow Options dialog and the Distance along pipe value specified is less than the minimum allowable pipe length (0.1m). Advice Check the parameters in the Fire Flow Options dialog (accessed via the Schedule Hydraulic Run View).
454	Hydrant target point pipe too short to split Info None Cause Pipe selected in the Fire Flow Options dialog (when running a Forced Fire Flow simulation) is too short. The Insert FF_Target_Point node in pipe option has been selected in the Fire Flow Options dialog and the length of the pipe to be split is less than twice the minimum allowable pipe length (0.1m). Advice Check the parameters in the Fire Flow Options dialog (accessed via the Schedule Hydraulic Run View).
455	Hydrant target point split pipe distance too large Info None Cause Distance along pipe parameter defined in the Fire Flow Options dialog (when running a Forced Fire Flow simulation) is too large. The Insert FF_Target_Point node in pipe option has been selected in the Fire Flow Options dialog and the length of selected pipe - Distance along pipe value specified is less than the minimum allowable pipe length (0.1m). Advice Check the parameters in the Fire Flow Options dialog (accessed via the Schedule Hydraulic Run View).
456	Test flows must be greater than zero Info None Cause Incorrect parameter in the Fire Flow Options dialog when running a Forced Fire Flow simulation. A Test Flow specified in the Fire Flow Options dialog is less than or equal to zero. Advice Check the parameters in the Fire Flow Options dialog (accessed via the Schedule Hydraulic Run View).
457	Hydrant target point node must be Node, Hydrant or Transfer Node Info None Cause Incorrect parameter in the Fire Flow Options dialog when running a Forced Fire Flow simulation. The Use existing node option has been selected in the Fire Flow Options dialog and the selected node is not an allowable type. Allowable types of hydrant target point node are: Basic Node Hydrant Node Transfer Node Advice Check the parameters in the Fire Flow Options dialog (accessed via the Schedule Hydraulic Run View).
547	Pumping against TRANSFER or from DEMAND zone Info Pump station name. Demand downstream of pump station. Cause Negative flow is required through pumping station in a branched part of the network to satisfy demand. Advice Check direction of pump station. Check boundary conditions of demand zone (for example check for missing reservoirs or fixed head nodes).
800	Reservoir FULL - Total Overflow Info Cumulative overflow from start of simulation. Name of the reservoir. Cause The reservoir is full and overspilling (inflow remains higher than outflow). Advice This may be intentional if modelling an emergency case. If not, select all the reservoirs and use the Non Time Varying Report to see all reservoirs that have suffered from overspill. For reservoirs where overspill is excessive, you can display a grid of time varying results for the reservoir and analyse the overspill further. Your aim should be to define a control policy that prevents significant loss through overspill.
801	Reservoir EMPTY - Total Deficit Info Cumulative deficit from start of simulation. Name of the reservoir. Cause The reservoir is empty because outflows have exceeded inflows by a sufficient margin that the reservoir is completely empty. From now on, results are of dubious value. InfoWorks will continue computation, assuming that the reservoir water level never falls below the reservoir bottom level. The water deficit (the amount of water "invented" by the software to maintain the minimum water level) is recorded and available in the simulation results. Advice You may want to deliberately analyse this situation. If so, bear in mind that InfoWorks artificially maintains a minimum water level, so results elsewhere in the network will not reflect an actual occurrence of this kind. If not, select all the reservoirs and use the Non Time Varying Report to see all reservoirs that have suffered from water deficit. For reservoirs where deficit has occurred, you can display a grid of time varying results for the reservoir and analyse the deficit further. Your aim should be to develop a control policy that prevents reservoirs emptying and maintains adequate reserves.
810	Pump OFF - suction below cut-off level Info Name of the pumping station, the pump number, and the total number of pumps in pumping station. Cause Pressure (head) in the suction (upstream) node of this pumping station has dropped below the dangerous level for the pump mentioned. InfoWorks has stopped the pump. The pump will restart when local pressure reaches a safe level. Advice This should not occur in normal operation. You may have created this situation intentionally to analyse an emergency case. You should aim to develop a control policy that prevents this situation arising.
811	PST (FLOW) Flow change by timer control Info Name of the pumping station. Old and new value of flow. Cause A scheduled change of flow in the pumping station. Advice For information only. No action required.
812	PST (PLAN) No. of active pumps changed Info Name of the pumping station. Old and new number of active pumps. Cause A scheduled change in the pumping station. One or more pumps has been switched on or off. Advice For information only. No action required.
813	PST (AUTO) Level Control pumps change Info Name of the pumping station. Old and new STATUS for all pumps. Cause A scheduled change in the pumping station. One or more units is switched on or off. Advice For information only. No action required.
814	PST (FLOW) OFF by Timer Control Info Name of the pumping station. Cause The pumping station has been switched off as scheduled. Advice For information only. No action required.
815	PST (PLAN) OFF by Timer control Info Name of the pumping station. Old and new number of active pumps. Cause A scheduled change in the pumping station. All pumps are switched off. Advice For information only. No action required.
816	PST (AUTO) OFF by Pressure Control Info Name of the pumping station. Old and new STATUS for all pumps. Cause A scheduled change in the pumping station. All pumps are switched off. Advice For information only. No action required.
817	PST (FLOW) ON by Timer control Info Name of the pumping station. Old and new value of flow. Cause A scheduled change in the pumping station. The pumping station is restarted. Advice For information only. No action required.
818	PST (PLAN) ON by Timer control Info Name of the pumping station. Old and new number of active pumps. Cause A scheduled change in the pumping station. The pumping station is restarted. Advice For information only. No action required.
819	PST (AUTO) ON by Pressure Control Info Name of the pumping station. Old and new status for all pumps. Cause A scheduled change in the pumping station. The pumping station is restarted. Advice For information only. No action required.
820	PST (PLAN) Pump Speed Change Info Name of the pumping station. Pump unit number. Old and new speed for pump. Cause A scheduled change in the pumping station. The speed of the pump is changed. Advice For information only. No action required.
821	Control Valve Opening Change Info Name of the valve. Old and new opening. Cause A scheduled change of valve opening. Advice For information only. No action required.
823	Float Valve Closed Info Labels of both end nodes for the float valve. Cause This float valve was closed to prevent overspilling in the reservoir (downstream node). Advice For information only. No action required.
824	Float Valve Activated Info Labels of both end nodes for the float valve. Cause Water level in the reservoir (downstream node) is increasing, and the float valve starts to throttle the inflow to prevent overspilling. Advice For information only. No action required.
826	Exceptional Flow at NODE Info Node name and exceptional demand flow. Cause Exceptional Demand is defined in the Control Data for the node. Advice For information only. No action required.
827	Exceptional Flow cancelled - Node isolated Info Node name and exceptional demand flow Cause All exceptional demand assigned to this node will be deleted because the node is isolated from the rest of the network. Advice This may be intentional. If not, you must fix the error that has left this node isolated.
829	Hydrant Operation in progress at Node Info Node name Cause A scheduled opening of hydrant. Advice For information only. No action required.
830	Hydrant operation cancelled - Node isolated Info Node name Cause All hydrant operation assigned to this node will be deleted because the node is isolated from the rest of the network. Advice This may be intentional. If not, you must fix the error that has left this node isolated.
835	PST outside (right) of defined curve range Info Name of the pumping station. Head delivered by pumping station. Cause Pumping station is operating outside of curve defined by user specified pump curves (delivering lower head and higher flow than defined by curve). Advice Check sufficient points have been specified for pump curves of units in the pumping station. Replace pumps in station with more suitable units.
836	PST operates on ZERO FLOW - Head too high Info Name of the pumping station. Head from first entry of pump curve / pumping station curve. Cause Head required cannot be provided with the existing pumps in the pumping station. Advice Check for hydraulic restrictions downstream of pump. Check pump curves of units in the pumping station. Replace pumps in station with more suitable units.
837	PST OFF by Pressure Control Info Name of the pumping station. Old and new STATUS of all pumps. Cause The pumping station is switched off because pressure at the control node is outside the limits specified in the pumping station control data (Pressure On and Pressure Off). Advice Probably no action required. Examine the control policy if this event was unexpected.
838	PST ON by Pressure Control Info Name of the pumping station. Old and new STATUS of all pumps. Cause The pumping station has been switched on. Pressure at the control node has returned within the bounds set in the control data for this node (Pressure On and Pressure Off). Advice Probably no action required. Examine the control policy if this event was unexpected.
850	Node isolated, Demand DELETED Info Name of node. Demand deleted from this node. Cause All demand assigned to this node will be deleted because the node is isolated from the rest of the network. Advice This may be intentional. If not, you must fix the error that has left this node isolated.
852	Transfer CANCELLED - Node isolated Info Name of node. Demand assigned to node. Cause All demand assigned to this transfer node will be deleted because the node is isolated from the rest of the network. Advice This may be intentional. If not, you must fix the error that has left this transfer node isolated.
854	FLOW change to meet DEMAND/TRANSFER Info The name of both end nodes of the pump, flow specified from PST, new flow value. Cause Flow required by demand/transfer differs from that specified in flow profile for PST in FLOW control mode. Advice Check that FLOW control mode is the correct control mode for the PST or check if the demand area/transfer is isolated from alternative supplies.
855	Demand suppressed by pipe closures Info Number of nodes. Cause Demand cannot be met due to closed pipes isolating demand nodes. Advice This may be intentional. If not, you must fix the error that has left these nodes isolated. To view node names of isolated nodes, choose to "Show imagessages for all isolated nodes with demand" in the Simulation Options dialog when running a simulation.
856	Pipe Closed Info The name of both end nodes of the pipe Cause The pipe has been closed as scheduled. Advice For information only. No action required.
857	Pipe reopened Info The name of both end nodes of the pipe Cause The pipe has been opened as scheduled. Advice For information only. No action required.
858	Link - Time Closures replicated for next day Info Name of link Cause May occur if a simulation is run over a time period greater than 24 hours. Time varying link controls specified for 24 hours or less will be replicated for the following day. Advice For information only. No action required.
861	PST - Time Profile replicated for next day Info Name of pumping station Cause May occur if a simulation is run over a time period greater than 24 hours. Time varying pump controls specified for 24 hours or less will be replicated for the following day. Advice For information only. No action required.
862	VALVE - Time Profile replicated for next day Info Name of valve Cause May occur if a simulation is run over a time period greater than 24 hours. Time varying valve controls specified for 24 hours or less will be replicated for the following day. Advice For information only. No action required.
863	TRANSFER - Time Profile replicated for next day Info Name of node Cause May occur if a simulation is run over a time period greater than 24 hours. Time varying transfer node controls specified for 24 hours or less will be replicated for the following day. Advice For information only. No action required.
864	Fix.Head - Time Profile replicated for next day Info Name of fixed head node Cause May occur if a simulation is run over a time period greater than 24 hours. Time varying fixed head node controls specified for 24 hours or less will be replicated for the following day. Advice For information only. No action required.
865	!! SOLUTION INVALID (Iteration, Max.error, Node) Info Number of iterations reached, Maximum Error, Node name at which maximum error occurred. Cause InfoWorks WS could not compute solution for timestep. Advice Review system operation and control policy.
870	Calibration Info Time, number of calibration steps taken, calibration factor applied at step, sum of fractional differences between calculated and measured pressures and flows Cause A calibration run type has been carried out. Advice For information only, No action required.
871	Watsed: Invalid combination of Sediment Density and Diameter Info None Cause The pipe sedimentation calculations are based on the well established Ackers-White theory for sedimentation modelling. The dimensionless grain size is outside the range of application for the Ackers-White model. Advice Review sediment density and diameter values.
952	!! INVALID SNAPSHOTS Info Number of timesteps Cause InfoWorks WS could not compute solution for number of timesteps. Advice Review system operation and control policy.
1005	Electric Tariffs file missing/not used Info None Cause An Electricity Tariff file has not been selected for use in the Hydraulic Run Schedule. Advice For information only. No action required.
1114	PST not found in the control - will be shut off Info Name of the pumping station Cause The Control Set does not contain any data for this pumping station. InfoWorks WS assumes that the pumping station is switched off for the duration of the simulation. Advice You can do this if you want, but it is probably less confusing to create control data for the pumping station, and explicitly set all pumps to OFF.
2000	The rtc/upc definitions for this event contain errors. See above for details. Info UPC error messages displayed in run log above error message. Cause There are errors in the UPC scenario used to run the simulation Advice Check that the correct UPC scenario has been used.
2001	Cannot create results file Info None Cause May occur due to disk space problems. May occur if the working folder is on a server and there are network problems. Advice Check for adequate disk space. Check for possible network problems.
2002	Cannot write summary to results file Info None Cause May occur due to disk space problems. May occur if the working folder is on a server and there are network problems. Advice Check for adequate disk space. Check for possible network problems.
2003	Cannot write results at time Info Simulation time step Cause May occur due to disk space problems. May occur if the working folder is on a server and there are network problems. Advice Check for adequate disk space. Check for possible network problems.