Hi Jason, 

Hi Sarah,

 

Those commands show what is currently registered in the Windows File Association database as the default handler for .py files. We can see that it is C:\Python27\python.exe, which is the Python interpreter in the default location decided by the Python team, as opposed to the location that ArcGIS uses when it installs its own copy of Python, which is C:\Python27\ArcGIS10.7 for ArcGIS 10.7.x. This suggests that you manually installed Python yourself after installing ArcGIS. By default, whenever the Python installer runs, it updates the File Associations to so that the version being installed becomes the handler for Python files. So when you installed it, the installer changed the File Assocation from C:\Python27\ArcGIS10.7\python.exe to C:\Python27\python.exe.

 

While it is possible to have both ArcGIS and MGET use a version of Python that you install yourself, it can be quite tricky. Most likely, you were trying to get MGET working and installed Python yourself to see if that would help. I’m sorry if MGET’s installation instructions were not clear on that point. In any case, unless you have a specific reason for installing Python yourself, it would be best to change the Windows file associations back so that Windows will use ArcGIS’s copy of Python by default.

 

To do that, first start a Command Prompt with the “Run As Administrator” option. This is necessary so you can change the file associations, as opposed to just displaying them:

 

1.   Click the Windows Start button

2.   Type cmd.exe

3.   Right click on Command Prompt and select Run As Administrator:

 

 

4.   If it shows Windows PowerShell instead of Command Prompt, don’t run it. Contact me instead.

5.   After you click Run As Administrator, Windows will prompt you with Yes/No asking if you want the app to make changes to the device. Click Yes.

6.   Type in the following three ftype commands. I would send you a batch file to do it, but the email systems would just strip it off, thinking it was a malicious file.

 

 

That will change Windows back to using the ArcGIS 10.7.1’s Python interpreter. Now, to get MGET working, first you might as well remove MGET, pywin32, and Python itself that were manually installed to the non-ArcGIS location:

 

7.   Close all ArcGIS programs.

 

8.   From Windows Control Panel, Programs and Features:

a.    Remove Python 2.7 Marine Geospatial Ecology Tools, if present

b.    Remove Python 2.7 pywin32, if present

c.    Remove Python 2.7 itself, if present

 

9.   A bug in Python itself prevents MGET’s uninstaller from completing all of its tasks. Just to be sure that all of the current MGET is gone, use Windows File Explorer to manually delete the entire directory C:\Program Files\GeoEco.

 

Now install pywin32 and MGET to the ArcGIS copy of Python:

 

10. Install pywin32. The file name should be similar to pywin32-XXX.win32-py27.exe, where XXX is the build number (225 is the most recent build). When you run the installer it will ask you where you want to install it. Make sure you choose C:\Python27\ArcGIS10.7 which will hopefully be selected by default. If this is not available or you cannot figure out how to select it, stop without completing the installer and contact me.

 

11. Install MGET. You want MGET-0.8a72.win32-py27.exe. Download here if you don’t have it handy already.

 

12. Try MGET again. Hopefully it will work, but if not, almost definitely you will see a different error, because most likely it will at least be installed in the right place.

 

If you have any immediate questions about this procedure, feel free to ask before trying it. It looks complicated but is not that bad. Still, it might be scary if you have not done much of this kind of thing before.

 

Best,

 

Jason

 

 

 

From: Sarah Gravem <>
Sent: Tuesday, October 8, 2019 4:27 PM
To: Jason Roberts <>
Cc: ; Dickens, John <>
Subject: Re: [mget-help] error code when using MGET models

 

Hi Jason, 

Thanks a bunch for your help. This is what the command says, so it looks like we have problem #1

 

 

Thanks, 
Sarah

 

On Fri, Oct 4, 2019 at 7:03 AM Jason Roberts <> wrote:

Hi Sarah and John,

 

This is definitely an installation problem. I should be able to help you get it working.

 

This specific message, ImportError: No module named _GeoEcoArcGISHelper, occurs when the MGET script invoked by ArcGIS (C:\Program Files\GeoEco\ArcGISToolbox\Scripts\RExploratoryPlotsScatterplotMatrixForArcGISTable.py in this case) tries to access the rest of MGET, which is a Python package similar to ArcGIS’s own arcpy and arcgisscripting packages, or the popular numpy and scipy packages, or the pywin32 package that you installed that MGET requires. _GeoEcoArcGISHelper is a special Python module that helps MGET’s ArcGIS scripts access the MGET package. This ImportError occurs when the script asks Python to load the module but the module does not exist.

 

Usually this problem happens when there are multiple versions of Python installed on the machine, as can happen when ArcGIS is upgraded or when Python is manually installed. It is ok to have multiple versions installed, but when this is done, it is important that 1) the Windows “file association” database be configured such that the default handler for Python scripts is the installation of Python that ArcGIS expects, and 2) pywin32 and MGET are installed to that installation of Python.

 

First let’s check #1. You have ArcGIS 10.7.1. For ArcGIS to work properly, it is important that Windows be set to use the copy of Python installed with ArcGIS 10.7. You can check it from a command prompt like this:

 

 

To start a command prompt, click the Windows Start button, type cmd.exe and press Enter. Then type the assoc and ftype commands as shown above. Send me a screenshot.

 

If the second command says something different, such as Python.file="C:\Python27\python.exe" ... then we’ll need to change it back to what ArcGIS wants. After this, we can check for problem #2.

 

Best,

Jason

 

From: <> On Behalf Of Sarah Gravem
Sent: Thursday, October 3, 2019 6:06 PM
To:
Cc: Dickens, John <>
Subject: [mget-help] error code when using MGET models

 

Hi, 

My student John and I are new to MGET and trying to run a simple GLM in ArcMap between mussel cover and temperature to get started using the Fit GLM tool. I've also tried doing a Scatterplot Matrix for Table between some of my covariates. For both, I receive a  "No module named _GeoEcoArcGISHelper" error, which is copied below. 

 

I used the advice here https://lists.nicholas.duke.edu/sympa/arc/mget-help/2012-07/msg00011.html and have uninstalled and re-installed MGET with no luck. 

I updated my ArcGIS Desktop from 10.5 to 10.7.1 this morning, then uninstalled and reinstalled Python 2.7pywin32-224. I also have Python 2.7.16 in my program list, which I think I installed during the MGET setup. I see in the help that there may be a problem with calling the correct Python version? 

Thanks, 
Sarah and John

 

 

Executing: RExploratoryPlotsScatterplotMatrixForArcGISTable iButton_2 "RoboMaxDaily #" # Histogram Smooth Correlation # # # # 1000 6500 6500 10 white
Start Time: Thu Oct  3 14:01:07 2019
Running script RExploratoryPlotsScatterplotMatrixForArcGISTable...
Failed script RExploratoryPlotsScatterplotMatrixForArcGISTable...

Traceback (most recent call last):
  File "C:\Program Files\GeoEco\ArcGISToolbox\Scripts\RExploratoryPlotsScatterplotMatrixForArcGISTable.py", line 1, in <module>
    import sys, _GeoEcoArcGISHelper
ImportError: No module named _GeoEcoArcGISHelper

Failed to execute (RExploratoryPlotsScatterplotMatrixForArcGISTable).
Failed at Thu Oct  3 14:01:07 2019 (Elapsed Time: 0.05 seconds)

 

 

--

Sarah A. Gravem, PhD (she/her)

Research Associate (Postdoctoral)
Oregon State University

541-737-8404

www.sarahgravem.com

www.piscoweb.org/sea-star-wasting-syndrome-task-force

primed-osu.weebly.com/

...🐌...🐌...🐌

 

--

Sarah A. Gravem, PhD (she/her)

Research Associate (Postdoctoral)
Oregon State University

541-737-8404

www.sarahgravem.com

www.piscoweb.org/sea-star-wasting-syndrome-task-force

primed-osu.weebly.com/

...🐌...🐌...🐌