Introduction

This is a temporary workaround for a bug in Version 7.0 and 7.0.1. 

This bug can be encountered when a model has both Pipe Network Gates and gates on a hydraulic structure (SA/2D Connection or Lateral Structure). It will produce an access violation as shown below. 

Workaround

The core of this issues involves the order at which gate boundary conditions are read in from the Unsteady Flow File (.u##). If Pipe Network gate conditions are NOT read-in first, the access violation will be thrown. To resolve this, first make a backup of the .u## file. Then open the .u## file in a text editor and cut/paste all the Pipe Network Gate Boundary conditions above the other structure gate boundary conditions.

In the example below, the gate boundary condition was identified by searching the work 'Conduit'. The the text was cut from the 'Boundary Location =...' to just before the next instance of that, then the text was pasted above the other gate boundary conditions.

The resulting file looks like this: