Latest Contributions by V_StuartFoote

@souris_boo, Covered in this open thread, sticky at the top of the forum... Stuart ... View more

Peter, The installation log looked fine, just the usual MSI installer confusion over ROOTDRIVE and TARGETDIR pointing to another drive on the system H:\--non issues for the install, and the HECGeoHMS looks to have fully installed. Did you afterword go ahead and back out the ArcHydro Tools 2.1.0.30 and install the 2.1.0.98 build? Also, regards the ArcToolbox Window crash when docking in ArcCatalog, does it otherwise seem to behave when the Arc Toolbox window is allowed to float without docking? If it works, suggest you don't dock it. There have been past problems with objects of the Desktop 10.0 GUI associated with docking and undocking actions, most were supposedly taken care of at SP2. But suppose they could have resurfaced at SP5. Stuart ... View more

Peter, If installed from a command windows as per the example, the installation log (archydrotoolsInstall.log) would be in the same folder from where the installation package (ArcHydroTools.msi) was run. However, it looks like something is wrong as your screen shot of your "Toolbox Window" does not show Arc Hydro Tools, yet its .tbx file is visible in your System Toolbox screen shot. I am pretty sure that when correctly registered the Arc Hydro Tools toolbox is treated as a "default" toolbox and should show. On the other hand, the HEC GeoHMS Tools does not get picked up in the Toolbox Window--so it is not treated as a default toolbox and must be added. Adding it to the Toolbox Window should proceed without issue--as is visible in the attached screen clip where the GeoHMS Toolbox has been added. So I suspect your installation did not run completely, as the screen capture of your Add Toolbox dialog does not show the GeoHMS Tools as present in the System Toolboxes object. Have a look in the C:\Program Files (x86)\ArcGIS\Desktop10.0\ArcToolbox\Toolboxes folder for the GeoHMS Tools.tbx. If not there, something went wrong with your installation and I'd look for problems with your installer privileges and reinstall. If the toolbox file is present, then I would rename or delete your ArcGIS user profile (the files listed below) to allow default per user settings to be reestablished for your account on next launch and see if working with a default profile clears issue: [INDENT]C:\Users\<username>\AppData\Roaming\ESRI C:\Users\<username>\Documents\ArcGIS\Toolbox.tbx C:\Users\<username>\Documents\ArcGIS\Default.gdb **careful of deleting this one as you may have project data held there and from a Registry edit session: rename or delete the HKEY_CURRENT_USER\Software\ESRI[/INDENT] If the GeoHMS Tools.tbx is not present in the Toolboxes folder, then the installation was flawed. Reviewing the log file may help you to identify the issue. One common problem for example would have been to run the installation as a non-priviledged user. The log should help identify that as well and I'd first check to be sure you've run the installation from a command window "Run as Administrator". Stuart ... View more

Peter, Answered you over on the Hydro forum. Stuart ... View more

I'm experiencing problems with HEC-GeoHMS as well. As soon as I add HEC-GeoHMS toolbox within ArcCatalog is crashes and I have to uninstall HEC-GeoHMS to resolve the problem, before being able to restart ArcCatalog. I'm running ArcGIS 10 SP5 on Windows 7 64 bit. HEC-GeoHMS is hard coded for some reason that it requires Arc Hydro 2.1.0.30 to be installed and won't accept a new version such as 2.1.0.98.  My first obersvation is that as soon as you add HEC-GeoHMS toolbox to your ArcToolbox within ArcCatalog, it crashes ArcCatalog. I had to delete the Normal.gxt to get ArcCatalog to open without crashing. The second problem that I've found is that if you run "Adjoingt Catchment Processing" from within ModelBuilder or the toolbox the output is empty. ... I previously had Arc Hydro 2.1.0.98 and had to uninstall it as HEC-GeoHMS 10.0.0.85 wants Arc Hydro 2.1.0.30. Once I had uninstalled Arc Hydro 2.1.0.98, I was able to install HEC-GeoHMS and ArcHydro. I've come accross two problems, the first is that if you add HEC-GeoHMS toolbox to ArcCatalog Toolbox it crashes ArcCatalog and the only way to get ArcCatalog to open without crashing is to delete the Normal.gxt. The second problem that I've found is that if you run Adjoint Catchment from the toolbox or within ModelBuilder the output is always empty. Just wondering if you have come across the following. Peter, Not certain your issue will be the same as OP is having with HEC GeoRAS where language settings and out of cache conditions seem to be the problems. That said, I believe yours and others issues with the two HEC pacakges would be helped by the application of ArcGIS Desktopp 10.0 SP5 and shifting to current Desktop 10.0 build of ArcHydro Tools, i.e. 2.1.0.98 For HECGeoHMS issues, my understanding is that the USACE HEC asks Esri to limit the ArcHydro version to simplify their configuration management (and internal user support) of the HECGeoHMS package. If you choose to install HECGeoHMS, build 10.0.0.85, you are limited by its Microsoft installer packaging to install with the bundled version of ArcHydro, i.e. 2.1.0.30 As you found, if you already have an ArcHydro build installed, the HECGeoHMS installer will prompt you to uninstall it from the Add/Remove programs panel and then abort. So, run the Add/Remove programs GUI (appwiz.cpl) and uninstall the "Arc Hydro Tools", or alternatively open a command window "Run as Administrator" and enter msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} This is one of the few instances that I would not aggressively clean-up the registry since you will be leaving ArcGIS Desktop 10.0 in place and will be reinstalling the version of ArcHydro Tools bundled with HECGeoHMS. If you want to be a bit more thorough about a full removal, you could download the ApRegWork utility from the ftp site and run ESRI.APWR.ApRegWork.exe and select only the "ARCHYDRO" search text. With ArcGIS Desktop 10.0 intact, go ahead and run the HECGeoHMS installer. I prefer to run from a command window to be able to fully log the installation and to run the installation as Administrator, but you could simply select the installer and deal with UAC. The installer will now detect that no ArcHydro Tools are present and launch the installer for build 2.1.0.30, and then the HECGeoHMS installer, build 10.0.0.85--allow them to complete. At this point I'd launch ArcMap and add both the "Arc Hydro Tools" toolbar and the "HEC-GeoHMS" to be sure they are functional then close them both, and close ArcMap. Next use Add/Remove programs (appwiz.cpl) and uninstall the 2.1.0.30 version of "Arc Hydro Tools" as before. Then download the current build of Arc Hydro Tools for Desktop 10.0, build 2.1.0.98 (2012-07-10) from the FTP site. Install that from command prompt "Run as Administrator" with msiexec.exe /i ArcHydroTools.msi /L*v archydrotoolsInstall.log Following the installation, review the log looking for any weirdness with installer variables--TARGETDIR, ROOTDIR, PYTHONHOME. And, if your Python26 installation was done outside of ArcGIS, you'll need to copy the ArcHydroTools.pth file from C:\Python26\ArcGIS10.0\Lib\site-packages to the correct Python Lib\site-packages location on your system. Then launch ArcMap and again add both the "Arc Hydro Tools" toolbar and the "HEC-GeoHMS" toolbar to check for function. Not guaranteed but that should have resolved the issues with your Adjoint Catchment. Regards your problems with ArcCatalog, not sure I follow your issue. You don't add/customize the ArcCatalog toolbar. Rather, the Arc Hydro Tools and HEC GeoHMS and GeoRAS Tools should be accessed from the catalog tree view (ArcCatalog --> Windows --> Catalog Tree), but having the latest patches for the ArcHydro Tools and Desktop SP5 installed should help with stability. Note: there is no version yet of HECGeoHMS or HECGeoRAS for ArcGIS Desktop 10.1 Stuart ... View more

I wanted to find out if you have used the latest version of HEC-GeoHMS 10.0.0.85. I previously had Arc Hydro 2.1.0.98 and had to uninstall it as HEC-GeoHMS 10.0.0.85 wants Arc Hydro 2.1.0.30. Once I had uninstalled Arc Hydro 2.1.0.98, I was able to install HEC-GeoHMS and ArcHydro. I've come accross two problems, the first is that if you add HEC-GeoHMS toolbox to ArcCatalog Toolbox it crashes ArcCatalog and the only way to get ArcCatalog to open without crashing is to delete the Normal.gxt. The second problem that I've found is that if you run Adjoint Catchment from the toolbox or within ModelBuilder the output is always empty. Just wondering if you have come across the following. Peter, This currently sticky thread was opened for ArcHydro support on ArcGIS Desktop 10.1. So let's work your ArcHydro and HEC GeoHMS for 10.0 issue over on the Hydro thread where other HEC GeoHMS and GeoRAS users will see it. Stuart ... View more

That would be ftp://RiverHydraulics:river%[email protected]/ArcHydro/Setup10.1/ from a web browser. Far more efficient to use an FTP client (FileZilla perhaps) with these login credentials: [INDENT]ftp.esri.com login: RiverHydraulics password: river.1114 As provided for the initial ArcHydro 2.0.x version here: http://forums.arcgis.com/threads/8274-ArcHydro-in-ArcGIS-10?p=35289&viewfull=1#post35289[/INDENT] Stuart ... View more

All, The latest release of ArcHydro -- build 2.1.0.98 (2012-07-10)  retains hard coded dependencies on ArcGIS 10.0 Nothing posted to the ftp site, and no word from Esri Water Resources group on when or if ArcHydro for ArcGIS 10.1 will be built. Suspect it will be, but for now if you need to use ArcHydro tools--do not upgrade to ArcGIS Desktop 10.1 Stuart ... View more

Tim, Back when we first had an 1606 error with the ArcHydro tools installation ( http://forums.arcgis.com/threads/42198-ArcHydro-2.0-MSI-installer-Error-1606-when-Python26-not-in-default-ESRI-location?p=143543&viewfull=1#post143543 ) the problem was a Microsoft Installer error in handling a Python 2.6 installation in a non-Esri location (e.g. other than C:\Python26\ArcGIS10.0) and an incorrect laydown of the Lib\site-packages\ArcHydroTools.pth search path. It is incorrect in the final ArcHydro 2.0 build, 2.0.1.133 The Water Resources team worked on the installer and by the 2.1.0.19 build had it all sorted. So, exactly which version of ArcHydro tools are you installing?  What is your Python 2.6 configuration, i.e. what is the path to your python.exe and pythonw.exe? Current build on the ftp site is 2.1.0.92, r.2012-06-26 Stuart ... View more

Curtis, For ArcHydro 2.1 and 2.0 where ApFramework is bundled with ArcHydro the GUID Product Code for silent uninstall should be: msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb For ArcHydro 1.4 ApFramework had its own Product Code, while ArcHydro used the same Product Code as in 2.1 and 2.0. So, you'd need to run two. msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb msiexec.exe /x {58B1A257-249D-4852-854C-3957088BDE2D} /qb Make it /qn if you really want it silent -- no user interface, for GPO or MSSCCM scripting. Suggest that following a "silent" uninstall, you follow up with a run of the ESRI.APWR.ApRegWork.exe registry cleaner from the ApRegwork Utility folder on the ESRI_RiverHydraulics ftp site. At least a couple of times until until you know that the Microsoft installer is really cleaning everything related out of the Registry. Let us know if it all works. Stuart =-=-= P.S. Below are the Installer Package IDs and Prduct Codes that I had available. I don't have installer packages for the earlier 1.3 and 1.4 products handy to check Product Codes against, but could probably dig them out if needed. ArcHydro 2.1 & ApFramework 2.1.0.91 -- {BC962DAD-C5BA-4AE9-BA40-56834D395BE1} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb 2.1.0.43 -- {3093608A-4517-4D08-8866-5E6EAD4E1618} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb 2.1.0.40 -- {46370555-D6A3-45F4-B267-399E55B9A6CA} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb 2.1.0.32 -- {6F8D0A9D-E18D-49CF-80AA-09C8CA9AC557} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb 2.1.0.27 -- {8C0989C3-A1AA-43E0-AFFB-DDE1CD9B4791} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb 2.1.0.22 -- {E9AB51B2-5596-4CE0-8B9F-8D8085D1982E} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb 2.1.0.19 -- {79918C94-8E10-4715-8E43-43CE9BF5BE73} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb 2.1.0.1 -- {385905AA-59AC-4082-B104-88D7D3190362} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb =-=-= ArcHydro 2.0 & ApFramework 2.0.1.133 -- {4A528FE9-44A4-4FB1-ADDA-125761FDA66F} (Final 2.0, 2011-10-10) msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb 2.0.1.131 -- {C4A909B2-5452-40CC-819E-6AA23AC9E998} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb 2.0.1.117 -- {3C07041C-21CB-459D-A2F1-39B7E7505E3B} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb 2.0.1.102 -- {719FF312-0F6F-4A4F-BE34-76D68458668F} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb 2.0.1.88 -- {050683D1-4238-44C2-AD60-0CCE5F7FDA5A} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb 2.0.1.78 -- {757B18E9-6F3D-44B7-A512-566CAF6F8EB6} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb 2.0.1.47 -- {43219135-F5FE-4ED0-8235-1E33007094FA} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb 2.0.1.31 -- {CFED3F92-0F13-4E69-A8DE-76CA71E88102} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb 2.0.1.30 -- {F36525F7-7DF3-415E-A174-14B45F25B7DE} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb 2.0.1.15 -- {32605F23-E5B3-46F7-978F-6588C31C0AF9} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb 2.0.1.7 -- {7DDB2E95-9B8F-4F20-920D-AE33F3C1ED4D} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb 2.0.0.66 -- {077B8E71-7338-4109-AE8F-39450D6F4A70} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb 2.0.0.40 -- {EAD23E6B-7620-4B9D-AFF2-8B79FC024504} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb =-=-= ArcHydro 1.4 & ApFramework 3.1 1.4.0.256 -- {584E49B6-FC78-46EC-A623-4B8ECA639CAE} msiexec.exe /x {777B898F-BB2C-4A7E-8FD9-A7E251C14E9D} /qb 3.1.0.103 -- {B0CF4C6E-FFE9-4E9B-B082-0B5656B66E2C} msiexec.exe /x {58B1A257-249D-4852-854C-3957088BDE2D} /qb ... View more

Tung Hoang, They are only available with access to the Customer Care Portal ( http://customers.esri.com ) There you'll find a Software Download tab. And from there a listing of product lines, you'd want Data and Maps --> Esri Data & Maps for ArcGIS 10, it is the third selection Esri Data & Maps for ArcGIS 10 #3 If you do not have individual access to the Customer Care Portal, identify your Esri license coordinator at your work or school (whomever you received your license from)--they'll have access to be able to download. Otherwise you will need to request the DVD from your Esri distributor or Regional office. The Data & Maps DVDs are not made available to Esri ArcGIS Desktop Trial users. Stuart ... View more

Ellery, Hmm, how are you integrating your Fusion VM Windows session into OS X, not running under Unity are you?  Do you also have a functional BootCamp instance you could work from? Esri will flat out NOT answer any support issues if you are running Fusion, Parallels or Virtual Box. And of course you should be aware that ArcHydro users are expected to be self supporting--although the Water Resources team is happy to receive legitimate bug reports. If installed correctly, ArcHydro is pretty robust under native Windows, although I'd disagree with Mark about using ArcHydro version found in the Corps of Engineers HEC served release of GeoHMS, or their GeoRAS posting.  The "development" versions from the ftp site of these and the ArcHydro releases have bug patches applied as they are uncovered. Considerable delay in the patched releases finding their way back to the HEC site. Quite a bit of installation help to ensure your ArcGIS Desktop 10 is configured correctly--one of the biggest issues being insufficient user rights elevation to fully register all COM assemblies--disable UAC on your VM or activate THE Administrator account and install from it. Another issue being exhaustion of registry resources during installation--have to pre-set registry to its maximum size (search forum for RegistrySizeLimit - 0xffffffff). And if the ArcHydro installer runs correctly, you will have an ArcHydro entry present from the Customize --> Toolbars to use to activate the Extension. And you will have ArcHydro tools registered into the ArcToolbox with no additional configuration needed for use.  Have another go at an installation, uninstall ArcHydro and then download and run the ApRegWork utility ( ESRI.APWR.ApRegWork.exe ) from the ftp site--use it to fully remove residuals of your prior installations. Then run the latest ArcHydro (or GeoHMS) .msi installer from the ftp site  "Run as Administrator", or as THE Administrator of your Windows VM. Post back if any of that is unclear, or if you follow it all but are still stuck. Stuart ... View more