<< Click to Display Table of Contents >> Navigation: Wadiso 6 User Guide > Time/Water quality simulation > Running the Time/WQ Simulation > Time/WQ Simulation Error and Warning Messages |
The following is a list of error and warning messages which can be issued by the EPANet hydraulic engine, either during a steady state hydraulic balance, or during a time/WQ simulation analysis.
No |
Explanation |
101 |
An analysis was terminated, due to insufficient memory available. |
110 |
An analysis was terminated, because the network hydraulic equations could not be solved. Check for portions of the network not having any physical links back to a tank or reservoir, or for unreasonable values regarding network input data. |
200 |
One or more errors were detected in the input data. The nature of the error will be described by the 200-series error messages listed below. |
201 |
There is a syntax error in a line of the input file, created from the network data. This is most likely to have occurred in the *.INP text file, created by the Wadiso program, and stored as WadZEPA.INP. on the ...\Windows\Temp\Wadiso5 directory. Call GLS Consulting if this happens. |
202 |
An illegal numeric value was assigned to a property. |
203 |
An object refers to an undefined node. |
204 |
An object refers to an undefined link. |
205 |
An object refers to an undefined time pattern. |
206 |
An object refers to an undefined curve. |
207 |
An attempt is made to control a check valve. Once a pipe is assigned as a Check Valve, its status cannot be changed by either time-, clocktime-, simple- or rule-based controls. |
208 |
Reference was made to an undefined node. This could occur in a control statement, for example. |
209 |
An illegal value was assigned to a node property. |
210 |
Reference was made to an undefined link. This could occur in a control statement, for example. |
211 |
An illegal value was assigned to a link property. |
212 |
A source tracing analysis refers to an undefined trace node. |
213 |
An analysis option/setting has an illegal value (an example would be a negative time step value). |
214 |
There are too many characters in a line read from an input file. The lines in the *.INP file are limited to 255 characters (See also 201 above). |
215 |
Two or more nodes or links share the same ID number. |
216 |
Energy data were supplied for an undefined pump. |
217 |
Invalid energy data were supplied for a pump. |
219 |
A valve is illegally connected to a reservoir or tank. A PRV, PSV or FCV cannot be directly connected to a reservoir or tank. Use a length of pipe to separate the two. |
220 |
A valve is illegally connected to another valve. PRVs cannot share the same downstream node, or be linked in series, PSVs cannot share the same upstream node, or be linked in series, and a PSV cannot be directly connected to the downstream node of a PRV. |
221 |
A rule-based control contains a misplaced clause. |
223 |
There are not enough nodes in the network to analyse. A valid network must contain at least one tank/reservoir node and one ordinary node. |
224 |
There is not at least one tank or reservoir in the network. |
225 |
Invalid lower/upper levels were specified for a tank (e.g., the lower lever is higher than the upper level). |
226 |
No pump curve was supplied for a pump. A pump must be assigned a curve ID Number, or 1, 2 or 3 pairs of Flow/Head data must be provided. |
227 |
A pump has an invalid pump curve. A valid pump curve must have decreasing head with increasing flow. |
230 |
A curve has non-increasing X-values. |
233 |
A node is not connected to any links. |
302 |
The system cannot open the temporary input file. |
303 |
The system cannot open the status report file. See Error 302. |
304 |
The system cannot open the binary output file. See Error 302. |
308 |
Could not save results to file. This can occur if the disk becomes full. |
309 |
Could not write results to report file. This can occur if the disk becomes full. |