Arc Hydro/GIS Troubleshooting GuideSolutions, Tips and Tricks The purpose of this document is to provide solutions to some common issues encountered when using ArcGIS and the Arc Hydro tools. Table of Contents Arc Hydro Issues............................................................................................................................................ 3 Automation Error ...................................................................................................................................... 3 VAT missing from Catchment Grid ............................................................................................................ 3 Too many records for Create Weir Stations tool to calculate .................................................................. 3 Grid process bombs out ............................................................................................................................ 4 Arc Hydro “System.Runtime…” Error (Flow Direction with Sinks) ............................................................ 4 Drainage Area Characterization (empty values) ....................................................................................... 5 Drainage Boundary Smoothing Error ........................................................................................................ 5 Arc Hydro does not completely uninstall.................................................................................................. 6 How To .......................................................................................................................................................... 7 Change Arc Hydro default from personal .mdb to file .gdb ...................................................................... 7 Turn off Auto Target Location Creation on .MXD Save............................................................................. 8 Calculate lowest spill elevation for catchments ....................................................................................... 8 Generate spill points on catchment boundaries .................................................................................... 11 Generate irregular cross-section lines and extract elevations from a DEM ........................................... 12 Check for Duplicate Features .................................................................................................................. 14 Populate FROM_NODE and TO_NODE for ICPR_LINKs........................................................................... 16 Snap Lines to Nearest Nodes .................................................................................................................. 17 Hydraulic Element Point (HEP) Errors ......................................................................................................... 18 HEP Error message “HRESULT_E_FAIL” .................................................................................................. 18 Bridge Deck HEP Error “System.Argument.Exception” ........................................................................... 18 HEP error message “System.Runtime…Spatial References Do Not Match” ........................................... 19 Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 1 Hydraulic Element ID Tool Error (Could not load file or assembly ‘ApUniqueIDMgrExt…) .................... 19 XML Issues................................................................................................................................................... 20 Export to XML error ................................................................................................................................ 20 Out of Memory Error .............................................................................................................................. 21 SWFWMD Connectivity Tools ..................................................................................................................... 25 Connect HydroJunctions – HydroJunction won’t connect ...................................................................... 25 Connect HydroJunctions – Zero-length polylines not allowed ............................................................... 27 AH Connectivity Refinement Tools ............................................................................................................. 29 Connect Control Structure Junctions – Error HRESULT E_FAIL ............................................................... 29 Connect Control Structure Junctions – HydroJunction Won’t Connect ................................................. 29 General GIS errors ....................................................................................................................................... 30 Load Objects Error .................................................................................................................................. 30 Empty Toolbox Tool Dialog ..................................................................................................................... 31 Load Objects – HEP subtypes all default to PIPE during load ................................................................. 32 SWFWMD Toolbar - Load Objects Error ................................................................................................. 35 Dual Maps Not Working.......................................................................................................................... 37 Arc Map crashes during save .................................................................................................................. 38 Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 2 Arc Hydro Issues Automation Error This error may occur when some temporary files are incorrectly deleted. Solution Clean up the Windows temp directory that defaults to: C:\Documents and Settings\username\Local Settings\Temp Then rerun the process. VAT missing from Catchment Grid Error sometimes occurs when attempting to run the Drainage Point Processing tool. It could be that it ran out of memory and failed to create the VAT table. Solution Recreate the VAT table by using the Multi Output Map Algebra gp tool under Spatial Analyst toolbox. Enter the following: BuildVAT D:\enter path name here\cat Then remove CAT Grid and re-add it to the map. The Drainage Point Processing tool should run now. Too many records for Create Weir Stations tool to calculate Error occurs when attempting to run the Irregular Weir – Create Stations tool if the dataset has too many vertices. Error getting list of OIDs from the table. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 3 000.Solution Increase the “JET engine max # of records to calculate” setting.exe which is located under C:\Program Files\ArcGIS\Utilities\ and change the setting to 1.000 or more Click OK. Solution Edit registry to increase the maximum number of records for automatically creating the grid table (default is 65536) Click Start >> Run and type Regedit Browse to… HKEY_LOCAL_MACHINE\SOFTWARE\ESRI\Raster\Preferences Right-click grid.max_table_range and click modify Increase value from 65536 to 1.Runtime…” Error (Flow Direction with Sinks) The following error may occur when running the Flow Direction with Sinks tool. Run ArcMapSettings.000 or more. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 4 . Solution Clean up the Windows temp directory that defaults to: C:\Documents and Settings\username\Local Settings\Temp Then rerun the process. System. Grid process bombs out Grid process quits before finishing.000. close Registry Editor and reboot for settings to take effect Clean out temp directory and retry Arc Hydro “System.COMException (0x80041098): ERROR 010067: Error in executing grid expression.InteropServices.Runtime. x and . IGeometry toPolyline.InterpolateZFromSource(IGeometry fromPolyline. at ESRI. Boolean asRatio.00 seconds) Solution Make sure the coordinate system is defined for the feature dataset where you are attempting to write the output (smoothed drainage boundary lines).InteropServices.GDBHelper.APWR.ArcGIS.ICurve.ApHydro.ApHydro. ICurve& outSubcurve) at ESRI.s temp files located in the .GDBHelper.Geometry.GetSubcurve(Double fromDistance.. Double toDistance.. End Time: Wed Jun 09 15:15:24 2010 (Elapsed Time: 48. ICurve& outSubcurve) at ESRI.Runtime. Solution Clean up the Windows temp directory that defaults to: C:\Documents and Settings\username\Local Settings\Temp Also delete . Double toDistance. System. String& exMessage) System. at ESRI.\Program Files\ArcGIS\Bin directory.Geometry.ICurve.APWR.Drainage Area Characterization (empty values) Partial population of the EAV table may occur when some temporary files are incorrectly deleted.InterpolateZFromSource(IGeometry fromPolyline. Boolean asRatio. Then rerun the process. IGeometry toPolyline. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 5 . String& exMessage) Failed to execute (DrainageBoundarySmoothing).ArcGIS.COMException (0x80040202): The operation was attempted on an empty geometry.Runtime.GetSubcurve(Double fromDistance.InteropServices.COMException (0x80040202): The operation was attempted on an empty geometry. Drainage Boundary Smoothing Error Error message occurs during drainage boundary smoothing. APWR.exe to search for leftover references in the registry and delete them.Arc Hydro does not completely uninstall Some files are left behind in the bin directory after uninstalling Arc Hydro Solution Run the latest ApRegWork. 2.esri.1114 Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 6 .ApRegWork. ftp://ftp. Do not delete references to the JEA Arc Hydro Irregular ApFramework Weir tools.com/ TimeSeriesManager Username = RiverHydraulics WshpTools Password = river. ApUniqueIDMgrExt ARCHYDRO1 ESRI.exe is available for download from SWFWMD2 the ESRI Arc Hydro ftp site. Run for the following Searching Text: AHMorphology 1. Do not delete references to the SWFWMD toolbar or ApHydro SWFWMD terrain toolbar. Delete ArcHydroTools. The default is a personal geodatabase. d. Browse to: HydroConfig > ProgParams > LocationType > Vector b.xml with the XML viewer (XMLViewEdit. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 7 . 2. either they need to delete ArcHydroTools. Save the XML (Click Yes to overwrite the exiting) and close the XML editor. Open ArcHydroTools. but can be changed to a file geodatabase. Change Value from 0 to 1 and click OK.gdb Arc Hydro will automatically create a new geodatabase when first saving an ArcMap document (.ahd from the Application Data\ESRI\ArcHydro Tools folder or make changes in both files.ahd from C:\Document Settings\username\Application Data\ESRI\ArcHydroTools AH GP tools (toolbox tools) use this ahd to create target workspace.exe) – both are located in: C:\Program Files\ESRI\WaterUtils\ArcHydro9\Bin\ a.mxd).xml in the bin folder. If user makes any changes to ArcHydroTools.mdb to file .How To Change Arc Hydro default from personal . Right-click Vector and select Edit Text c. Solution 1. 7 23 1 3 84.MXD Save The default setting is for Arc Hydro to automatically create a target geodatabase.Spill_Elev = DrainageBoundary.Turn off Auto Target Location Creation on .xml with the XML viewer (XMLViewEdit.0 … … … … Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 8 . How to determine the lowest spill point elevation for each catchment and the corresponding drainage boundary to create preferential flowpath links. and select Edit Text. Input needed: Catchment (FC).1 22 1 4 85. raster folder.2 24 5 1 85.MXD.exe) C:\Program Files\ESRI\WaterUtils\ArcHydro9\Bin\ArcHydroTools.xml Browse to: HydroConfig > ProgParams > CreateGPConfigOnSave Right-click CreateGPConfigOnSave. and .1 25 -1 1 87. double) to DrainConn table Join DrainConn table to Drainage boundary feature class through FeatureID. Change Value from 1 to 0 and click OK. HydroID fields Calc DrainConn. DrainConn (table). Solution Add field (Spill_Elev. Solution Open the ArcHydroTools. Calculate lowest spill elevation for catchments Note: the following process has been replaced by the automated tool “Define Overland Preferential Node Link Schema” under ArcToolbox -> Arc Hydro Tools -> Terrain Morphology -> AH Connectivity Refinement. It is provided here as a reference only. DrainageBoundary (FC).MinElev Remove Join Create a new table “Catchment_Spill_Elev” in ArcCatalog with the following fields: CatchmentID (Long Integer) DrainageBoundaryID (Long Integer) Spill_Elev (Double) DrainConn (Table) FeatureID FeatureID1 FeatureID2 Spill_Elev 21 1 2 86.ahd file when first saving a new . This requires running the Simple Data Loader twice to account for all possible boundary connections for each catchment.1 1 22 85. Catchment_Spill_Elev (Table) CatchmentID DrainageBoundaryID1 Spill_Elev 1 21 86.1 1 25 87. With one extra record (CatchmentID = -1) due to the external boundary. This can be done by adding a common field to relate the two tables.2 … … Need a way to link the Catchment_Spill_Elev and Catchment_Min_Spill tables to identify which DrainageBoundary corresponds to the lowest spill elevation for a given catchment.7 1 23 84.0 … … … Catchment_Min_Spill (Table) CatchmentID MIN_Spill_Elev 1 84. Write the output to a new table “Catchment_Min_Spill” Note: there should be a 1-1 (+1) relationship between the number of records in the Catchment_Min_Spill table and the number of features in the Catchment feature class. For the Catchment_Spill_Elev table: Add field MIN [short integer] Add field INT_ELEV [long integer] Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 9 .Use “Load Data…” tool in ArcCatalog to load from “DrainConn” table into the “Catchment_Spill_Elev” table. Second Data Load Target Field Matching Source Field CatchmentID [int] FeatureID2 [int] DrainageBoundaryID [int] FeatureID [int] Spill_Elev [double] Spill_Elev [double] Run Summary on “Catchment_Spill_Elev” table to determine the minimum spill elevation for each catchment.2 1 24 85. First Data Load Target Field Matching Source Field CatchmentID [int] FeatureID1 [int] DrainageBoundaryID [int] FeatureID [int] Spill_Elev [double] Spill_Elev [double] 2. 1. 4 91400 2_91400 3 76.4 1 91400 2_91400 … … … … … … Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 10 . Add field APPEND [text. Calc MIN = 1 for all selected records in Catchment_Spill_Elev table. Catchment_Min_Spill (Table) CatchmentID Spill_Elev INT_ELEV APPEND 1 84.2 1 84200 1_84200 … … … … … … 2 36 95.7 76800 3_76800 … … … … Catchment_Spill_Elev (Table) CatchmentID DrainageBoundaryID Spill_Elev MIN INT_ELEV APPEND 1 21 86. 15] Calc INT_ELEV = INT((Spill_Elev +0.05) x 1000) Calc APPEND = CatchmentID & “_” & INT_ELEV For the Catchment_Min_Spill table: Add field INT_ELEV [long integer] Add field APPEND [text. Select all records in Catchment_Min_Spill table.1 <null> 86100 1_86100 1 22 85.6 <null> 95700 2_95700 2 39 91.2 84200 1_84200 2 91.05) x 1000) Calc APPEND = CatchmentID & “_” & INT_ELEV Relate Catchment_Spill_Elev and Catchment_Min_Spill tables through the APPEND fields. 15] Calc INT_ELEV = INT((MIN_Spill_Elev +0.7 <null> 85800 1_85800 1 23 84. Open related table (Options > Related Tables). Extract surface elevation from DEM: 3D Analyst -> Functional Surface -> Surface Spot Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 11 .Generate spill points on catchment boundaries Generate a layer of spill points that represent the lowest point location and spill elevation along each boundary segment between two catchments. Solution Required input – HydroJunctions* *must include the ones generated by Arc Hydro using the Drainage Connectivity Characterization tool (where FType = Boundary Node). Select by Attributes… Export selected features to a new feature class called SpillPoints. use 3D Analyst Tools > Functional Surface > Interpolate Shape tool to convert the line to 3D and create additional vertices (source of heights is DEM or TIN). ICPR_XSECT. Initially the line will have a minimum of two vertices (at the beginning and end of the line). ArcToolbox -> Arc Hydro Tools -> Terrain Morphology -> Drainage Boundary Processing -> Station-Elevation Characterization Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 12 . IRREGULAR_CROSSSECTION. etc. Import the generated line into an existing polyline feature class that is MZ enabled (e. Now the line contains vertices at the various elevation breaks along the line.Generate irregular cross-section lines and extract elevations from a DEM Solution Digitize a line in the desired location of the cross-section (using either temporary shapefile or feature class). Run the “Station-Elevation Characterization” tool to write the station/elevation information to a table.g. Next.) and assign HydroIDs. StationMPct. Elevation.Note: when writing out to ICPR_XSECT_STATIONS some manual cleanup is needed afterwards to make the table GWIS compliant. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 13 . and StationMLen when finished. StationMFra. NAME = FeatureID (or relate back to line feature class if actual names were assigned) STATION = StationMLen ELEV = Elevation Delete fields: FeatureID. Solution Use XTools Pro to find duplicates and either remove them or flag them. and 31802).Check for Duplicate Features Check for duplicate records in a table or duplicate geometries in a feature class. 31800. three of which are duplicates (HydroIDs = 31796. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 14 . In the screen capture below there are eight lines total. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 15 . Check the Remove Duplicates box to automatically remove them or leave the box unchecked to populate an index field with a 0 or 1. If searching for duplicate geometries check the Shape box.When the Find Duplicates dialog box opens choose the Input Table or Feature Layer. Specify the output location. where a 1 indicates the record is a duplicate. Save Edits vi. Target Features: ToNode ii. Target Features: FromNode ii. Output storage: FromNode (temp feature class) iii. Output storage: ToNode (temp feature class) iii. ToNode. Remove join 4. End Points: From b. End Points: To 2. Iteration #1 i. Join Features: ICPR_Node iii. Join Features: ICPR_Node iii. Output Feature Class: FromNode_SpatialJoin (temp feature class) iv. Input feature: ICPR_LINK ii. Join to ToNode_SpatialJoin. Join Field: NAME ii. Match option: INTERSECTS b. Join Operation: JOIN_ONE_TO_ONE v. through NAME field iii. XToolsPro -> Feature Conversions -> Convert Features to Points a. Remove join b. Join to FromNode_SpatialJoin. Calc From_Node = FromNode_SpatialJoin. Join Operation: JOIN_ONE_TO_ONE v. Match option: INTERSECTS 3. Input feature: ICPR_LINK ii. Table Join (join ICPR_LINK to…) a. Start Editing iv.NAME1 v. Iteration #2 i. Iteration #2 i. Iteration #1 i. Join Field: NAME ii. Start Editing iv.Populate FROM_NODE and TO_NODE for ICPR_LINKs Solution 1. Delete temp feature classes: FromNode. Spatial Join a. FromNode_SpatialJoin. ToNode_SpatialJoin Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 16 . Iteration #1 i. Output Feature Class: ToNode_SpatialJoin (temp feature class) iv. Calc To_Node = ToNode_SpatialJoin. Stop Editing.NAME1 v. Iteration #2 i. through NAME field iii. Snap Note: Need to Specify Type and Distance Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 17 .Snap Lines to Nearest Nodes Solution Use Editing Tools . Exception” Error occurs when placing Bridge Deck HEPs with tool (when running ArcGIS 9.Argument. Solution Delete ApField FLOW_DIRECTION_DESC from the XML configuration file.3) This is an issue with the snapping environment in 9.Hydraulic Element Point (HEP) Errors HEP Error message “HRESULT_E_FAIL” The error message appears during placement of HEPs using the HEP tool (when running ArcGIS 9.3. Go to C:\Program Files\ESRI\WaterUtils\ArcHydro9\Bin Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 18 . Solution Download the latest version of the Arc Hydro tools (5/8/09 or later) Bridge Deck HEP Error “System.3) This is an issue with the XML configuration file. System.COMException (0x80041203): The spatial references do not match.mxd is first created. Solution Create a new . Open ArcHydroTools.Runtime…Spatial References Do Not Match” Error message appears when placing HEPs even though the DEM and feature classes have the same spatial reference. overwrite the existing one.mxd.mxd before any feature classes when the .Runtime. Hydraulic Element ID Tool Error (Could not load file or assembly ‘ApUniqueIDMgrExt…) Error message appears when trying to use the Hydraulic Element ID tool to update HydroIDs and related identifiers. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 19 . then add the DEM and save the .InteropServices. Navigate to: HydroConfig (HydroConfig) ProgParams ApFunctions (ApFunctions) ApFunction (HEPDataEntry) ApLayers (ApLayers) ApLayer (BRIDGE_DECK) ApFields (ApFields) ApField (FLOW_DIRECTION_DESC) Right-click and delete the FLOW_DIRECTION_DESC node Save the XML. HEP error message “System. Close the XML editor and open ArcMap.xml using XMLViewEdit.mxd.exe (also located in the Bin directory). add the feature classes first. This error occurs if the DEM is added to the . Solution Download latest Arc Hydro setup.xml Solution (1) Access the old exchange export to xml by adding the dll ArcMapExportXMLGUI9. XML Issues Export to XML error ApUtilsNet9 error – No workspace defined for any of the defined layer/table! Error message occurs when trying to export to xml from ArcMap using toolbar tool: ApUtilities > Additional Utilities > Export GIS Data to XML This is a new exchange tool – out of synch with GWISICPRExportControl_2008.dll This will add ClsArcMapExchange.dll using: Customize > Add from file and browsing to C:\Program Files\ESRI\WaterUtils\ApFramework9\bin\ArcMapExportXMLGUI9. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 20 . String baseUri) at MS. String prefix. String prefix.g..OutOfMemoryException error may occur when trying to export datasets with a large number of records (e.XPathDocument. String baseUri) at MS. Exporting data from D:\ARC_HYDRO_TESTING\BRADEN_XML_TEST\FORSREERESH\BR_GWIS..AHXMLExchangeExport. Starting to export GIS data from geodatabase Still exporting. Failed to execute (ExportToXML). Use the “Export GIS Data to XML” tool under the GIS Data Exchange toolbox along with the latest XML control file2 from the SWFWMD ftp site.ctor(String uri) at ESRI.GDB.APWR.NodePageFactory.Internal.XPathDocumentBuilder..Xml.ctor(String uri.Xml.AddSibling(XPathNodeType xptyp. Exception of type 'System.Internal. XPathNodeType xptyp.swfwmd.GDB had been created Preparing workspace for export.Utils. XmlSpace space) at System.Execute(IArray paramvalues. select Data Exchange... Solution (2) Install the newest Arc Hydro tools from the SWFWMD ftp site1.state. and drag the command Export to XML onto your toolbar.000 records in the XSECTION_STATIONS table). +200.Cache.Xml..APWR.state. String namespaceName) at System. Workspace for D:\ARC_HYDRO_TESTING\BRADEN_XML_TEST\FORSREERESH\BR_GWIS. System. String namespaceUri..ArcHydroGPTools.NewNode(XPathNode[]& page. 1.. Int32& idx) at MS.xml false Start Time: Tue Aug 31 11:03:33 2010 Creating temporary modified control file C:\Documents and Settings\jjanke\Local Settings\Temp\tmp511.XPath. Layer ICPR_ModelNetwork_Junctions was not found in the map and will not be exported. IGPMessages message) Generating export XML.GISXDE.Cache.XPathDocument. XmlSpace space) at System.. Creating workspace to export GIS data.PrepareGxdeWorkspaces(GDEWorkspaceExports gdeWSExports) at ESRI.OutOfMemoryException: Exception of type 'System.swfwmd.Xml.XPath.Xml.XPathDocumentBuilder.us/pub/GWIS/ 2.. Executing: ExportToXML ArcHydro D:\Arc_Hydro_Testing\Braden_XML_test\ForSreeresh\GWIS_ICPR_ExportControl_20100312. http://ftp. String localName..LoadFromReader(XmlReader reader.Under categories.WriteStartAttribute(String prefix.AllocateSlot(XPathNode[]& page.XPathDocument.Cache..Internal. String localName.fl.XPathDocumentBuilder.OutOfMemoryException' was thrown.GxDEWSExportUtil.Cache. http://ftp..fl. ITrackCancel trackcancel.Xml. GIS data exchange parameters are correctly configured. String namespaceUri.XPath..XPathDocumentBuilder. IGPEnvironmentManager envMgr.Internal.OutOfMemoryException' was thrown.us/pub/GWIS/GWIS_v1.6/XML_to_ICPR/ Out of Memory Error System. End Time: Tue Aug 31 11:13:29 2010 (Elapsed Time: 9 minutes 56 seconds) Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 21 . String localName.xml.Xml. at MS.xml D:\Arc_Hydro_Testing\Braden_XML_test\ForSreeresh\exportXMLs\GWIS_export. 1. Remaining information will be imported into ICPR via XML. 2. Copy ICPR_Xsect_DBF_format. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 22 . Load ICPR_XSECT_STATIONS into xsec_points (match fields as shown below) *Note: if the ICPR_XSECT_STATIONS were thinned use the query builder during the last step of the import process to load only those stations where ISSTATION = 1. Remove the ICPR_XSECT feature class and ICPR_XSECT_STATIONS table from the ArcMap document and retry the XML export process (including transform) for remaining information. Load ICPR_XSECT into xsec (match fields as shown below) ii. Use “Load Data…” to import records from original GWIS gdb into the copied gdb from 2a i. Open ArcCatalog a.Solution Export Xsection information to dbf tables and import into ICPR.gdb from \\bkvnas02\EngProj\GWIS\GWIS_Geodatabase b. Select XML file from step 1 a.dbf *Note: the naming convention is critical for the next step when the tables are imported into ICPR.dbf ii. c. xsec -> ICPR_xsec.dbf ICPR_xsec_points. turn on everything except Cross Sections Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 23 . Import XML information i. Open ICPR and create a new ICP file (File -> New…) a. Export xsec and xsec_points to dbf format i. xsect_points -> ICPR_xsec_points.dbf Filestem Filestem 3. ICPR_xsec. File -> Import/Export -> XML Import… 1. b. File -> Import/Export -> Import DBF… 1. Filestem = ICPR Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 24 . Import DBF information i. turn on Cross Sections only b. Select path as location of dbf from 2c a. SWFWMD Connectivity Tools Connect HydroJunctions – HydroJunction won’t connect The process runs without any errors. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 25 . but afterwards the Junction is still not connected. ) this “error” may occur. Note: make sure INCLUDECONNECT_DESC field is set to 1 and CONNECTDONE is set to <null> or 0.Even when the Junction is snapped to the boundary using the Snap HydroJunctions tool and contains all the required fields (Hydraulic_Type_Desc = Culvert. and Boundary Drainage Line) are all in one feature dataset. IncludeConnect_Desc = True. Drainage Boundary. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 26 . This is a geodatabase snapping issue that sometimes occurs if the required input feature classes are located in different feature datasets. HydroEdge. etc. Solution Copy the DrainageBoundary feature class into the HydroNetwork feature dataset and rerun the tool. The HydroJunction should connect. Make sure the required input layers (Drainage Area. HydroJunction. COMException (0x800417018): Zero-length polylines not allowed … This error may occur if any of the HydroJunctions you are trying to connect are snapped to the same boundary location as a Boundary Node placed by Arc Hydro. snap to another vertex along the boundary).e.Connect HydroJunctions – Zero-length polylines not allowed System.Runtime. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 27 .InteropServices. Before Snap HydroJunctions tool After Snap HydroJunctions tool Solution Find any manually placed HydroJunctions that intersect boundary nodes and move them (i. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 28 . In the Table of Contents modify the names to keep the versions straight Open Layer Properties for HydroJunction (1) o Click on Definition Query tab and click Query Builder… "JUNCTION_PLACEMENT_DESC" = 'MAN' o Click OK. OK Select By Location o Select features from: HydroJunction (1) that intersect features from: HydroJunction (2) The selected features from HydroJunction (1) need to be moved away from the boundary node.To find the ones that intersect each other you need to load the same HydroJunction layer into ArcMap twice and set up two different definition queries. OK Open Layer Properties for HydroJunction (2) o Click on Definition Query tab and click Query Builder… "JUNCTION_PLACEMENT_DESC" = 'AH' o Click OK. Once the Junctions have been moved rerun the Connect HydroJunctions tool and those Junctions will now connect. InteropServices.AH Connectivity Refinement Tools Connect Control Structure Junctions – Error HRESULT E_FAIL ArcToolbox -> Arc Hydro Tools -> Terrain Morphology -> AH Connectivity Refinement -> Connect Control Structure Junctions Two possible error messages: 1) System. Solution Start Editing and move the end of the HydroEdge (HydroJunction will also move automatically) so the HydroJunction is no longer in the same DEM cell as the Sink Node. Error(s) typically occurs if the INCLUDECONNECT_DESC field type is set as text instead of long integer. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 29 .COMException (0x80004005) : An invalid SQL statement was used. Make sure to calculate INCLUDECONNECT_DESC = 1 for all manually placed HYDROJUNCTIONS with HYDARULIC_TYPE_DESC set to INLET or CS. Solution Delete INCLUDECONNECT_DESC (text) and add back as long integer.COMException (0x80004005) : Error HRESULT E_FAIL has been returned from a call to a COM component… 2) System.InteropServices.Runtime. Connect Control Structure Junctions – HydroJunction Won’t Connect Tool will not connect a HydroJunction at the end of a pipe sequence (HYDRAULIC_TYPE_DESC = INLET/OUTLET or CONTROL STRUCTURE) if it is located in the same cell as the Sink Node. save edits and retry Connect Control Structure Junctions tool.Runtime. Stop editing. Select all the features with a valid length and export to a shapefile. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 30 .1 2 3 4 1) Inlet/Outlet HydroJunction located in the same DEM cell as the Sink Node 2) Move HydroJunction to adjacent cell 3) Run Connect Control Structure Junctions tool 4) Move HydroJunction back to original location General GIS errors Load Objects Error Can’t load objects from one geodatabase (source) into another geodatabase (target) because the source feature class contains some features with zero length and these features cannot be deleted in edit mode. Solution 1. 2. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 31 . Empty Toolbox Tool Dialog A blank dialog box appears when opening any ArcToolbox tool. By opening ArcMap a new ESRI folder is created in the registry. 3. Import the shapefile into a temp geodatabase with the same spatial reference as the target geodatabsase. Somehow the user profile became corrupted. Use Load Objects… tool to import from the temp geodatabase into the target geodatabase. Solution Open the registry (Start -> Run -> Regedit) Go to HKEY_CURRENT_USER -> Software Rename ESRI folder “ESRI_old” Open ArcMap and the tools should work again. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 32 .Load Objects – HEP subtypes all default to PIPE during load When using the “Load Objects…” tool to import HEPs from one feature class into another the subtype field (SUBELEMENT_TYPE) will default to PIPE for all the imported features (see example below). Target HEP feature class (114 records) Source HEP feature class (8 records) Use the object loader to import features from Source into Target. All the imported features default to PIPE even though the original subtype was either BARREL or WEIR. Notice that the POINT_TYPE_DESC is correct for the imported features. Solution The workaround is to add a temporary field for the subtype before performing the load objects. 5. 3. Browse to the source data. Match subtype_temp [int] (target) with SUBELEMENT_TYPE [int] (source) and click Next. Next. Start Editing. set HEP as the Target and click on Load Objects… tool 4. Open the attribute table of the target feature class. 6. select it and click Open. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 33 . Name the field subtype_temp and set the type to Long Integer. Click Next. and then Finish. 1. click on Options -> Add Field… 2. Click the Add button then click Next. or are not null. 12. Select where: “subtype_temp” > 0 Note: This selects all the records that have any value. The new features should now be assigned the correct subtypes. If everything looks correct save edits and stop editing. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 34 . 13. in the subtype_temp field. 11. Right-click on the SUBELEMENT_TYPE field and select calculate values. Set SUBELEMENT_TYPE = subtype_temp and click OK. 10. 14. These are the records for the features just loaded. Open the Target HEP attribute table 8. 7. Right-click subtype_temp field and delete. Click on Options -> Select by Attributes 9. Load Objects Error Layers do not display (red exclamation point appears) when added using Add SWFWMD Data tool Likely cause is a lost connection to SDE Solution (note: must be done by admin account on Windows 7 machines) Navigate to System Properties (Start Menu > Right-Click Computer and select Properties) Click “Advanced system settings” Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 35 .SWFWMD Toolbar . ” under System Variables and add a new TNS_ADMIN variable as shown below Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 36 ...Go to the “Advanced Tab” and Click on “Environment Variables” Click “New. Solution Open Internet Explorer -> Tools -> Internet Options Delete Browsing history under the General tab.Dual Maps Not Working Empty Internet Explorer window appears after activating the Dual Maps button and clicking on the map. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 37 . mxd. Arc Hydro/GIS Troubleshooting Guide (January 2011) Page 38 .mxd it displays the pathname instead.Arc Map crashes during save Arc Map crashes as soon as you try to save the .mxd. logo. Solution Two ways to fix: 1) delete the image reference and reinsert the image.) within the layout view. A broken link may occur if the image is stored on someone’s local drive and another user opens the map or if the image was moved or deleted and no longer exists in its original location. Whenever Arc Map can’t find an image referenced in the . The most likely cause is a broken link to an image (graphic. or 2) repair the pathname under picture properties (right-click image to open properties window). This is a known ESRI bug. Tip: One way to prevent this issue is by deleting the Element Name when you first insert an image. etc. Clearing out this reference will store the image within the .