Troubleshooting#

This short troubleshooting guide might help resolve some issues but if you are stuck please reach out via our contact form.

Contact Form

Installation Test#

  1. Test FLO-2D engine by running a model from a project folder. Copy the Run for Project files from

    C:\Program Files (x86)\FLO-2D PRO\Run for Project Folder

../_images/installtest01.png
  1. Paste the files into any project folder with *.DAT files like Barn.

    C:\Users\Public\Documents\FLO-2D PRO Documentation\Example Projects\Example Projects\Barn Mudflow

../_images/installtest02.png
  1. Double click FLOPRO.EXE to start a test run.

  2. If the computer is activated with the professional version, this message will appear.

../_images/installtest03.png
  1. If the computer isn’t activated, this message will appear.

../_images/installtest04.png
  1. Any other message might need some troubleshooting. Find the related issue below.

FLO-2D Pro Troubleshooting#

If something isn’t working, do not uninstall FLO-2D. That is rarely a correct way to fix the installation. email FLO-2D via the Contact Form for support.

Data Errors#

Most FLO-2D errors stem from data errors in the *.dat or *.hdf5. These files contain the data used by the engine during a simulation. Error messages are typically written to the FLO-2D *.chk files. These ascii files can be read using any text editor but FLO-2D Software recommends NotePad++ or any program that has column editing mode.

The check files are:
  • ERROR.CHK

  • STORMDRAIN_ERROR.CHK

  • ARF_ADJUSTMENT.CHK

  • CHANBANKEL.CHK

  • CHANNEL.CHK

  • UndergOUTFALLS.CHK

Check files contain:
  • Notes

  • Warnings

  • Errors

If the simulation stops with an error message, review the check files for errors. Notes and warnings will not stop a simulation.

Troubleshooting Help:
  • FLO-2D Data Input Manual Chapter 7

  • Storm Drain Guidelines

  • FLO-2D Plugin Technical Reference Manual

Fortran Errors#

Fortran error messages appear when the FLO-2D engine (flopro.exe) gets a data format or character that is not recognized. The error messages contain references that point to the file causing the problems.

Example 1

In the following image, vc2005con.dll and swmm_startif.f90 are listed in the error message. This indicates that the error is in the storm drain files.

../_images/fortran.png

Example 2

In the following image, hydrst.f90 is listed in the error message. This indicates that the error is in the hydraulic structure system.

../_images/fortran2.png

Check the data in the files for errors that could disrupt flopro.exe.

Drive Errors#

OneDrive

Running a model on a drive that is using OneDrive sync can disrupt the processing. Do not run long models on directories using OneDrive sync.

External Drives

Running a model on an external drive might slow a model down or be disrupted by a drive related issue such as maintenance or connection disruptions. Do not run long models on an external drive.

Virtual Machines

Running a model on a Virtual Machine is a good practice. Windows OS is required. Install and activate FLO-2D on the VM. Visual studio redistributable packages must be installed. VMs may be slower than running on a good computer.

FLO-2D Plugin and QGIS Errors#

Error messages related to the FLO-2D Plugin may appear as Python Errors, or an error messages reported by the FLO-2D plugin.

FLO-2D Plugin Error#

FLO-2D Plugin errors messages appear in error message windows. If the error message isn’t helpful, more troubleshooting ideas are sometimes available in the individual sections of the user manual. For example, if an error message appeared during Create Grid, see the Troubleshooting section of Create a Grid.

../_images/trouble002.png

Plugin error messages are also listed in the FLO-2D Plugin Technical Reference manual. Find it here:

C:\Users\Public\Documents\FLO-2D PRO Documentation\flo_help\Manuals

Python Error#

Python error messages have clues about the location of the error.

In this case, the error points to a problem with the FLO-2D Plugin. Use the contact form to send a request to fix the but.

Some error messages are related incorrect data in the QGIS vector or raster layers. In those cases, use Chat GPT or the Stack Exchange to get ideas on how to fix a layer.

../_images/trouble001.png

GDS and Mapper Troubleshooting#

GDS and Mapper are written in Visual Basic code. Visual basic has been obsolete code for more than a decade. Because of SysWOW (System Windows on Windows), old programs can be used but are challenging to install. Some computers won’t have any issues and others simply will not run GDS and Mapper because things like Microsoft Data Access (MDAC) and Data Access Objects (DAO) will not load or be recognized by the computer.

FLO-2D solved this issue by upgrading to QGIS and the FLO-2D Plugin. If you still want to use GDS or Mapper and you get missing dll failures or struggle to use GDS processors, this section may help.

  1. GDS might not be connected to it’s MapObjects dlls. These are the objects that do things like load images, load tables, intersect shapefiles, and create the grid. The fault will look like this:

../_images/gdsfault01.png
  1. If this fault shows up, delete the contents of this folder and run the FLO-2D Pro Setup Installer - MapObjects section again.

    C:\Program Files(x86)\Common Files\ESRI

    Don’t worry, these old files are not used by ArcGIS Desktop or ArcGIS Pro.

  2. GDS might give an error message when the user tries to set up a new project using Define Working Region…. A path correction will fix this fault. When a new project doesn’t have a project path, it tries to write data to the C:\Program Filex(x86)\FLO-2D Pro path. This path is protected by Admin Rights.

../_images/gdsfault03.png
  1. The error message that appears states something about admin rights or permissions. Correct it by applying a project path in GDS\Tools\Options\Directory Paths

../_images/gdsfault04.png
  1. GDS and Mapper may have overflow or out of memory error messages. This is not a correctable fault. They are both 32-bit programs and have limitations related to the memory they can use. This varies by computer and by screen size so if you get this fault on one computer, it may not show up on an older computer.

../_images/gdsfault05.png
  1. GDS and Mapper default settings are for computers in the USA. It may be necessary to adjust the number separator. If an error message appears about the number separator, use the Control Panel\Clock and Region\Additional Settings to set the decimal separator to a “.”. International users might want to use QGIS so this is not necessary.

../_images/gdsfault06.png
  1. Sometimes the Microsoft Data Access program doesn’t install correctly and GDS cannot find the MDAC dlls. It may be possible to reinstall the MDAC setup program. Download GDS Patch.

  1. GDS Tutorials are no longer part of the FLO-2D Pro Setup. To get the GDS and Mapper Tutorials, Run this installer: Download GDS Tutorials.