Hydra Engine Run Time Errors

  1. Run Time Error 5: Invalid procedure or argument.
  2. Run Time Error 6: Overflow, when opening Hydra.
  3. Run Time Error 6: Overflow, when doing Check Data.
  4. Run Time Error 6: Overflow, when viewing profile data.
  5. Run Time Error 9: Subscript out of range. 
  6. Run Time Error 13: Type mismatch, after selecting menu option for analysis.
  7. Run Time Error 13: Type mismatch, trying to generate a flow file.
  8. Run Time Error 53: File not found, or Obsolete or bad SET command: HAO.
  9. Run Time Error 75: Path File Access Error, on opening project data 
  10. Run Time Error 91: Object or with block variable not set.  or couldn’t find installable ISAM
  11. Run Time Error 372: Failed to load control ‘SSTab’ from TABCTL32.OCX.
  12. Run Time Error 380:  Invalid property value, on running the Hydra program 
  13. Run Time Error 429: Active X component can’t create object.
  14. Run Time Error 3021 No Current Record, during analysis
  15. Run Time Error 3036: Database has reached maximum size, during analysis
  16. Run Time Error 3078: The Microsoft Jet database engine cannot find the input table to query “CombinedFields”.  Make sure it exists and that its name is spelled correctly.
  17. Run Time Error 3146: ODBC call failed, on selecting File / Formatted Results Reports.
  18. Run Time Error 3218: Couldn’t update currently locked, on running an analysis.
  19. Run Time Error 3260: Couldn’t update, currently locked by user [ ] on machine [ ].
  20. Run Time Error 3265:  Item not found in this collection, when trying to open a collection system layer.
  21. Run Time Error 3375 SS2Q already has an index named G_ID, on updating database by query.
  22. Run Time Error 3218 Error processing results.  Failed to remove entity common records.  Database error: Couldn’t update: Currently locked.
  23. Run Time Error 3421 Data type conversion error, during analysis.
  24. Run Time Error 3464: Data type mismatch in criteria expression, on opening layer as “active”.
  25. Run Time Error 3464: Data type mismatch in criteria expression, doing Select Upstream Entities.

HYDRA® Interface Error Messages

During Installation

  1. On installing Hydra:  CPEAUT32.DLL is not self-registering. 
  2. Error initializing the Database Engine, ‘ActiveX’ component can’t create object, on running Hydra

On Opening a Project or Layer

  1. Error opening layer:  Unable to create [name].DBF.  That table already exists
  2. Couldn’t find installable ISAM, on opening project data.
  3. [Layername] isn’t an index in this table.  Look in the Indexes collection of the TableDef object to determine valid index names
  4. Tag [#] not found or already recalled
  5. Type mismatch error, on loading a layer into HYDRA 
  6. Error occurred opening project.  JETVBA file failed to initialize when called
  7. Field not found: G_ID, G_TYPE, G_NUMDOT… MEMO, on opening a layer
  8. Field not found:  SWMM_TYPE, SWMM_DES, on opening an SY layer
  9. Error: database missing record for G_ID of [#]
  10. Error detected in SY_.DXA.  See DXA.ERR
  11. Can’t load MSJTER35.DLL, on opening a project.
  12. Program halted.  Error #2 (File Not Found)  Error reading [path]\DES_CONFIG_[UNITS].DBF. Copy file CONFIG.DBF.

Query / Selection Set-Related

  1. Error loading selection set. File format invalid
  2. Program halted.  Error #2 File not found.  Set index to [Proj Dir/Layer Name].MDX

During Data Checks / Topology 

  1. Topology problems.  Verify System Continuity gives error “System failed to walk # entities”
  2. Warning “HYDRA_SEQ not set. This entity will not be included in the analysis” on outfalls when I Check Data on the Collection System Layer
  3. Warning “[field name] exceeds maximum allowed value” when I Check Data on the Service Area, or Drainage Layer
  4. “Can’t find a single qualified downstream link”

During Analysis

  1. Warnings about low flow velocity, or minimum flow velocity
  2. Error executing Hydra:  Invalid input to engine, number of parameters.   Error [AnalysisRun].CMD [line number].  ” [parameter] must be [requirement] “.
  3. Error [AnalysisRun].CMD [line number]:  Invalid number of parameters (4,13)
  4. Error [AnalysisRun].CMD [line number]:  Command requires Type, n, EntranceK and 2-30 sets of Elev/width.  
  5. Error [AnalysisRun].CMD [line number]:  Location X must be >=0.00 and <=7,620,000.000
  6. Error [AnalysisRun].CMD [line number]:  Tag [G_ID] not found or already record.
  7. Error [AnalysisRun].CMD [line number]:  Get link data, attempt to read record [G_ID], when last record is [G_ID].
  8. Warning: [AnalysisRun].CMD[1] No such command or command not implemented
  9. Backwater found. Unknown transport unit
  10. Error executing Hydra.  Internal error #-214748113.  Unexpected runtime error in HydraEng.DLL.  
  11. Error executing Hydra:  Internal error.  Invalid pointer operation
  12. Error executing Hydra:  ~ method ~ of object failed
  13. Error writing command file.  Invalid use of null
  14. Error writing command file.  Data type mismatch in criteria expression.
  15. Ox0000007E unable to locate module
  16. Analysis error:  HOL To[G_ID].

Run Time Error 5: Invalid procedure or argument.  During initialization

This can be caused by certain non-standard dual monitoring settings.  It can also be related to printer settings.  Try reinstalling your default Windows printer.

On Viewing Analysis Results

This can be caused be extraordinary high results data, for example an HGL that is miles above the ground elevation.  Check units for correctness, for example pipe diameters in meters rather than centimeters.  Also, make sure your flows in File Files are within range of reasonableness, check your flow-generation layer field definitions, to make sure you understand what they
mean.
Back to Top


Run Time Error 6:  Overflow, when opening Hydra

Is your computer configured for dual monitors?  Try changing your computer to only use one monitor and see if the error happens again.  If not, there is a configuration problem on your computer.


Run Time Error 6: Overflow, when doing Check Data

A data value in your database (DBF) file is extremely large, or extremely small — far beyond the range Hydra is expecting.  Look at your database either using Hydra’s Browse Database feature, or an external database program and try to find extreme values and correct them.  Please report this error and the results to


Run Time Error 6:  Overflow, when opening Hydra

Is your computer configured for dual monitors?  Try changing your computer to only use one monitor and see if the error happens again.  If not, there is a configuration problem on your computer.


Run Time Error 6:  Overflow, when viewing profile data

The structure of your SY.DBF file has been modified, probably from editing your database with a spreadsheet.  Compare the structure of your project SY database (field types, widths, etc) to the structure of the SY database for a sample project, and make the necessary corrections.  In the future, study the documentation for your spreadsheet program to avoid making changes to your DBF
file.
Back to Top


Run Time Error 9: Subscript out of range.

If this happens during analysis, this is a problem with some data sets.  Please be sure you have the latest version of the Hydra interface.

If this happens when loading a layer, there is a problem with the graphics files.  Re-register the layer in GisMaster, and try loading it in Hydra again.  Or, check for formatting problems in your DXA file, such as tabs instead of spaces between data.  Have you opened the DXA file in a word processing program, such as Microsoft Word?  We recommend only using text editors, such as Notepad or WordPad, to view Hydra data, in order to avoid adding “illegal” formatting to the file.
Back to Top


Run Time Error 13: Type mismatch, after selecting menu option for analysis.

Your PROJECT.SET file, which contains saved analysis settings used in the Analyze System dialog box has gotten corrupted.  Delete or move the PROJECT.SET in your Project Directory.  Hydra will re-create it next time you run an analysis, however, if you have any special functions, you will have to re-enter those.
Back to Top


Run Time Error 13: Type mismatch, trying to generate a flow file

Field formatting (ie numeric vs. character) in the project database (ie, SE_.DBF) have been changed, probably due to editing the database with a spreadsheet.  Another possibility is that you created the .DBF file as a new file with default structure, using a database program, such as Microsoft Access. Compare your DBF file to a functioning DBF (such as the sample data which comes with Hydra) to make the corrections.  A great tool for this is WCREATE.EXE which can be downloaded from: http://www.softsci.com/free.htm

Also, in File Explorer, delete the files called [layer name].NDX and [layer name].INF.

In the future, study the documentation of your spreadsheet program to prevent corruption of your project databases when you export to a DBF.

Back to Top


Error Message:  On running an analysis:  Run Time Error 3218 couldn’t update currently locked, or Obsolete or bad SET command: HAO, Run Time Error 53 file not found.  

This may be caused by a mismatch of Hydra interface and Hydra engine program files.  In Hydra, go to Help / About, and see the version information for Hydra.  Both the interface and the engine should be listed as 6.1.  If the Hydra engine is listed as 6.0, you need to reinstall the Hydra 6.1 update (CD labeled October 2000).  This is easiest if you first uninstall Hydra by running the Hydra installation program and selecting UNINSTALL from the options.  If you have not received your October 2000 update CD, or if you have misplaced it, please call Pizer at 206-634-2808.

“Couldn’t Update, Currently Locked” may also be caused by corruption of the PROJECT.MDB file, where results are stored. Delete the file called PROJECT.LDB, and try running analysis again.  It could also be caused by network interference between your server and your local computer, causing Hydra’s results import into Access to stop midway.  Try moving your project files to your local computer.
Back to Top


Error Message: On opening project data:  Run Time Error 75 Path File Access Error.

This can be caused by read-only properties on project files, a common problem when users have moved project data by copying files onto a CD.  Select project files in Windows File Explorer, right-click on them, select Properties, then make sure files are set to read-write access.

This error can also be caused by changing network path to data, path names longer than 250 characters, or project DBF files longer than 8 characters.

Back to Top


Run Time Error 91: Object or with block variable not set, or couldn’t find installable ISAM

There are problems with shared program files relating to Access database.  Re-install Hydra.

Back to Top


Run-time error ‘372’: Failed to load control ‘SSTab’ from TABCTL32.OCX. 

Check your version number in Hydra’s Help menu, About.  If you are using a version prior to Hydra 6.1.18, you’ll need to get an update from Pizer.  If you installed with a Hydra 6.0-series CD, you’ll need to reinstall with a Hydra 6.1 install CD.   If you have an early version of 6.1, you can request an update.

Back to Top


On running the Hydra program:  Run Time Error 380  Invalid property value.

This is caused by trying to run Hydra on a Windows NT computer configured for dual monitors.  The current version of Hydra does not support that feature.  Go to Control Panel, turn off dual monitors, then try running Hydra again.
Back to Top


Error Message:  Run Time Error 429 Active X component can’t create object.

This is caused by conflicts with shared program files, or other files on your computer not properly registered.  Make sure you have installed Hydra from a recent (October 2000 or later) installation CD.  If not, contact Pizer for a replacement CD. 

On Opening a Project

Install the Layer Transfer Wizard.

During Analysis

The HydraEng.DLL is not being recognized by the operating system, probably because of an installation problem.  From the Start button, select Run…  then input REGSVR32 followed by the full path to HydraEng.DLL (should be the same as your Hydra install). Note that if the path contains spaces, long file names, etc, put quotes around the path.

On selecting “Formatted Results Reports” from the File menu

This may occur using versions 6.0, 6.1, or 6.2.  This error should not occur in Hydra 6.3.  Use the formatted results reports designed to run from within Microsoft Access version 2000 or later.  The file HydraReporter.MDB is included on the Hydra
install CD.

Back to Top


Run Time Error 3021 No Current Record, during analysis

The Topology process has not been completed, and so there are no entities in your analysis Command File.  In Topology View, select Update Topology from the Topology menu.  Make sure the HYDRA_UP, HYDRA_DN, and HYDRA_SEQ fields (in your SY data grid) contain values.

Back to Top


Run Time Error 3036: Database has reached maximum size, during analysis

The Microsoft Access MDB database, called PROJECT.MDB, which stores Hydra’s analysis results has reached it’s maximum file size, and cannot hold any additional analysis run results.  If your project is very large, or if you have stored a large number of analysis runs, you will need to do one of the following:

  1. Delete extraneous analysis runs from your results database and “pack” the database to completely remove the records.  You can use the database packing function in Hydra’s File menu.
  2. Create a subfolder in your Project Directory for the PROJECT.MDB which includes your previously stored analysis runs.  Then Hydra will automatically create a new empty PROJECT.MDB file for future analysis runs.  Especially if you project is very large, you might consider using a separate PROJECT.MDB file kept in a separate subfolder for each analysis scenario.

Back to Top


Run Time Error 3078: The Microsoft Jet database engine cannot find the input table to query “CombinedFields”.  Make sure it exists and that its name is spelled correctly, during analysis.

Possible corruption of the PROJECT.MDB file where results are stored.  Try deleting or renaming the file, and then re-run an analysis to have HYDRA regenerate a new PROJECT.MDB file.

Back to Top


Error Message:  On selecting File / Formatted Results Reports:  Run Time Error 3146 ODBC call failed.

There is most likely a problem with shared program components caused by a newer operating system and newer versions of Microsoft Access.

From your Hydra installation CD, copy HydraReporter.MDB from HydraReports file folder to your Hydra Project Directory.  From Access 2000, you can open HydraReporter.MDB and print formatted results reports.  You can also change the format of the reports
using Access 2000.

Back to Top


Error Message:  On running an analysis:  Run Time Error 3218 couldn’t update currently locked, or Obsolete or bad SET command: HAO, Run Time Error 53 file not found.  

This may be caused by a mismatch of Hydra interface and Hydra engine program files.  In Hydra, go to Help / About, and see the version information for Hydra.  Both the interface and the engine should be listed as 6.1.  If the Hydra engine is listed as 6.0, you need to reinstall the Hydra 6.1 update (CD labeled October 2000).  This is easiest if you first uninstall Hydra by running the Hydra installation program and selecting UNINSTALL from the options.  If you have not received your October 2000 update CD, or if you have misplaced it, please call Pizer at 206-634-2808.

“Couldn’t Update, Currently Locked” may also be caused by corruption of the PROJECT.MDB file, where results are stored. Delete the file called PROJECT.LDB, and try running analysis again.  It could also be caused by network interference between your server and your local computer, causing Hydra’s results import into Access to stop midway.  Try moving your project files to your local computer.
Back to Top


Run Time Error 3265:  Item not found in this collection, when trying to open a collection system layer.  

Check to make sure the name of your files fit within Hydra’s naming conventions.  The collection system layer must start with SY_ and then have no more than 5 characters following, with a DXA and DBF file extension.
Back to Top


Error Message:  On updating database by query: Run Time Error #3375 – SS2Q already has an index named G_ID

This is a rare error that occurs when temporary files created by HYDRA during the update query process get corrupted.  The solution is to look at your Project Directory in Explorer and delete all files named SS2Q in your Project Directory.  There should be both a database (DBF) and an index file.  Once these have been deleted, open HYDRA again and try the update
query again.

Back to Top


Error processing results.  Failed to remove entity common records.  Database error: Couldn’t update: Currently
locked.  

At the time Hydra is trying to write analysis results, some other program or process is accessing your PROJECT.MDB database file, the file is read-only, or you do not have full read-write access to the file.  Check the file, your network, your log-on privileges for any
possible conflict.  You can also delete your PROJECT.LDB index file to have Hydra regenerate it.
Back to Top


Run Time Error 3421 Data type conversion error, during analysis

If you recently installed Hydra 6.2 and now get this error during analysis at the point where Hydra says “Importing HAO file into HydraGraphics”, there may be a mis-match of Hydra 6.2 interface and 6.1 analysis engine.  Check the version numbers by selecting Help / About.  If it does show a 6.1 analysis engine, then you need to manually register the 6.2 HydraEng.DLL by selecting Start / Run… then typing REGSVR32 followed by the path to your Hydra 6.2 HydraEng.DLL in quotes.

Back to Top


Run Time Error 3464: Data type mismatch in criteria expression, doing Select Upstream Entities

Field formatting (ie numeric vs. character) in the project database (ie, SE_.DBF) have been changed, probably due to editing the database with a spreadsheet.  Specifically the HYDRA_DN field has been changed from numeric to character.

Run Time Error 3464: Data type mismatch in criteria expression, on opening layer as “active”

Same as above, but make sure the G_ID field is numeric.

A great tool for fixing these problems is WCREATE.EXE which can be downloaded here:  http://www.softsci.com/free.htm (also included on the Hydra install CD).  The WCREATE tool allows you to quickly and easily view the structure of a DBF file. Compare the file structure of your layer .DBF file to one of the sample files, or a similar layer DBF which functions properly. Make any necessary changes with WCREATE, and save the file.

In the future, study the documentation of your spreadsheet program to prevent corruption of your project databases when you export to a DBF

Back to Top


On installing Hydra:  CPEAUT32.DLL is not self-registering. This is a message that occurs on some computer systems.  You can simply ignore this message and complete the installation.  If you have any other messages during installation, write them down and contact Pizer Technical Support.

Back to Top


Error initializing the Database Engine, ‘ActiveX’ component can’t create object, on running Hydra Error occurred opening project.  JETVBA file failed to initialize when called. Complete the Hydra installation by running the Hydra/GIS Layer Transfer Wizard installation program found on the Hydra installation CD.  This will register certain shared program files which may not have properly registered when you installed Hydra.

Back to Top


Error opening layer:  Unable to create [name].DBF.  That table already exists. This is caused by having a layer name that is longer than 8 characters.  In File Explorer, change the name of your DXA file to an 8 character name, and change the associated DBF file to the same name.
Back to Top


On opening project data: Error loading Project Directory; Couldn’t find installable ISAM.

This is caused by a problem with the installation of Hydra, related to shared database program files. Make sure you have the an installation CD that is from Oct 2000 or later. Make sure all components of Microsoft Office are not running while you install — this includes button bars. Install the GIS Layer Transfer Wizard in addition to Hydra. Un-install Hydra by running the installation program and selecting the Uninstall option. Then re-run the installation program and select the Install option.
Back to Top


[Layername] isn’t an index in this table. Look in the Indexes collection of the TableDef object to determine valid index names.Make sure your [Layername].DBF is not being used by another application, or access otherwise denied by your computer system. Delete your [Layername].NDX, [Layername].INF, [Layername].

Back to Top


Error Message: Tag [#] not found or already recalled. This is caused by incompatible field definitions in the layer database [LAYERNAME].DBF, specifically the HYDRA_SEQ field has been changed from a numeric to a character-type field.
This most often happens when a spreadsheet program is used to edit the HYDRA layer database. Spreadsheet programs, especially older versions, often change the field definitions (ie, changes character fields to numeric, or field width) as they save to a DBF file. The solution to this problem is to learn more about how to prevent your spreadsheet program from changing the field definitions of a DBF file, or use a database program to manipulate your HYDRA layer data.

Back to Top


Error Message: On loading a layer into HYDRA: Type mismatch error.This is caused by incompatible field definitions in the layer database [LAYERNAME].DBF. This most often happens when someone uses a spreadsheet program to edit the HYDRA layer database. Spreadsheet programs often change the field definitions (ie, changes character fields to numeric, or field width) as they save to a DBF file. A great tool for fixing this is WCREATE.EXE which can be downloaded from: http://www.softsci.com/free.htm

Prevention of this problem is to learn more about how to prevent your spreadsheet program from changing the field definitions of a DBF file, or use a database program to manipulate your HYDRA layer data.

Back to Top


Error initializing the Database Engine, ‘ActiveX’ component can’t create object, on running Hydra Error occurred opening project. JETVBA file failed to initialize when called. Complete the Hydra installation by running the Hydra/GIS Layer Transfer Wizard installation program found on the Hydra installation CD. This will register certain shared program files which may not have properly registered when you installed Hydra.

Back to Top


Field not found: G_ID, G_TYPE, G_NUMDOT… MEMO, on opening a layer Hydra is not able to open the layer because the layer database (.DBF) is open in another application or another instance of Hydra. Close the .DBF file and try again.

Feild not found: SWMM_TYPE, SWMM_DES, on opening an SY layerThis likely occurred with a project created in Hydra 6.0 or 6.1 when opening in Hydra 6.2 or 6.3 for the first time. Something is preventing Hydra from converting the database to the latest format, so it is not able to open the layer.

First, make sure the project data is “read-write” access. If you have moved your project data using a CD, the files are automatically “read-only” access. Select the files or folder, right-click, and select “properties” to change.

If you still have this problem, check the structure of the SY_.DBF carefully. Compare it to an SY.DBF file from one of the sample projects, or another project which does open. Hydra requires the layer .DBF files to conform to dBASE III structure requirements, but versions 6.0 and 6.1 were more tolerant to non-conformity. Something about the structure of this DBF file is preventing Hydra from making minor conversions to the layer to update it to the 6.2/6.3 file format, including adding the SWMM_TYPE and SWMM_DES fields.

Error: Database missing record for G_ID of [number], and data grid looks blank. Most likely, Hydra is not able to read the fields in the layer’s database .DBF because of a problem with the database index file. Either the file has gotten corrupted, or it was created with an incompatible version of Hydra. To solve the problem, open Windows File Explorer to your Project Directory. Sort the files by name, and scroll to where your layer is (ie SY_1999). Delete the files with extensions of .ENT, .NDX, .INF, and/or .MDX. Then try opening the layer in Hydra again.

Back to Top


How can I show hydraulic results based on Q/Q? Hydra outputs DESIGNQ, which is the total calculated gravity flow, and EPI_QFULL, which is the total flow capacity for that pipe. You can export these fields to an ASCII file for use in other programs.

Within Hydra, to highlight all pipes with a certain Q/Q, in results view, go to the menu Results / Results Selection Set Query. Click on the View SQL button to open the SQL text box.

The text in your SQL text box would look like this: SELECT [TAG] AS G_ID FROM CombinedFields WHERE [DESIGNQ]/[EPI_QFULL] > 1.25 AND RUNID=3

Click on the Do It button to run the Query. Repeat for other values and other highlighting colors.

Back to Top


Error detected in [layername].DXA. See DXA.ERRHydra is not able to open your collection system layer . To see comments on the problem, open the file called DXA.ERR in a text editor (ie Notepad or WordPad). The problem could include:

Digitizing errors, illegal entity types, or errors such as duplicate entities or duplicate ID numbers.

Path/File access error: Either your Hydra project files are “read-only access” — which commonly happens when you moves files via CD — or Hydra is not able to fully access the files over the network. If you need to use files over the network, you will need to specifically map the network drive to your local computer.

Back to Top


Can’t load MSJTER35.DLL, on opening a project. Install the GIS Layer Transfer Wizard from the Hydra CD to update this shared program component.

Make sure you are installing Hydra while logged in as Administrator.

Back to Top


Program halted. Error #2 (File Not Found) Error reading [path]\DES_CONFIG_[UNITS].DBF. Copy file CONFIG.DBF. Hydra 6.2 or 6.3 with SWMM module requires a file called CONFIG.DBF to be in your Project Directory. This is automatically copied there when you set up a project. However, if you copy files to a new Project Directoy, you’ll need to also copy the CONFIG.DBF or copy the file called DES_CONFIG_USA.DBF or DES_CONFIG_METRIC.DBF to your Project Directory and rename it to CONFIG.DBF.

Back to Top


Error loading selection set. File
format invalid.
Make sure you did not use quote symbols ( ” ) in your selection set file description or color key description.

Back to Top