Chronological Thread 

< Chronological >      < Thread >

---

Thank you for your detailed answer! Indeed, I inadvertently nuked ArcGIS's
version of Python with another version. My level of experience with Python
is, unfortunately, Cro-Magnon, so I probably should have just stopped instead
of blundering through a variety of "it might work" solutions. I have solved
the problem by upgrading to ArcGIS 10.5.1, which restored ArcGIS's version of
Python, and the red X has gone away. I appreciate your help. --Julie

Julie Howar
Coastal Program Biologist/GIS Specialist
Office: 805-735-7300

Point Blue—Conservation science for a healthy planet.

-----Original Message-----
From: Jason Roberts []
Sent: Monday, February 12, 2018 8:24 AM
To: Julie Howar <>
Cc:
Subject: RE: [mget-help] Can't run data products tools

Dear Julie,

The problem of having the "red X" for the first parameter of all MGET tools
has vexed us for a while. But I believe I have figured it out.

I believe the reason the red X comes up is because ArcGIS tries and fails to
import certain Python packages into the Python interpreter that runs when you
open the dialogue box for a Python-based tool such as MGET. In this scenario,
the red X will occur for all such tools, not just MGET. For example, most of
ArcGIS's own tools in the Spatial Statistics toolbox are Python tools. (You
can check that on your machine, if desired.)

I was able to reproduce this problem on my main ArcGIS 10.6 machine this
morning by closing ArcGIS, then (temporarily) renaming the
C:\Python27\ArcGIS10.6\Lib\site-packages\numpy directory to something else.
When I started ArcGIS and opened any Python-based tool, the red X would
appear on the first parameter. Apparently, ArcGIS tries to import the numpy
package as part of bringing up the tool dialogue box. As a programmer, I am
curious as to why ArcGIS is now importing numpy as part of the tool dialogue
box--it didn't used to, and I can speculate as to why it does now--but that
is not the critical question for you. The critical question is: why is the
failure happening and how do we fix it?

Most likely, all of this stems from an installation problem of some kind.
When ArcGIS is installed, it also installs Python (to C:\Python27\ArcGIS10.4
for your version of ArcGIS) and several Python packages (including numpy),
configures that Python to access ArcGIS's own Python packages (e.g. arcpy,
arcgisscripting), and configures the Windows File Association database so
that copy of Python is the default handler for Python files (e.g. those with
extensions .py, .pyc, and .pyo). ArcGIS expects that the machine will remain
in this state. If you install your own copy of Python, you have to take care
to either not overwrite the Windows File Association database so that your
copy of Python does not "take over" the running of Python files from ArcGIS's
copy, or you have to configure your copy to have all the stuff that ArcGIS
expects.

There's no reason anyone would foresee this unless they are a Python expert
and it is easy to accidentally disrupt ArcGIS in this way--all you have to do
is install Python yourself and accept the default options it prompts you with
in its installer. Once that is done, the operating system now considers that
new version of Python to be the default one to use.

In general, the best solution to this problem is to restore the system to the
state that ArcGIS expects, where its own Python interpreter is the default. I
would recommend this unless you plan to use Python yourself for some
non-ArcGIS purpose and the version of Python that comes with ArcGIS is not
sufficient for that purpose. In that case, it is possible (but tricky) to
install your own copy of Python and configure it properly so that ArcGIS can
use it.

So, how would you like to proceed? I can help you restore the machine to the
state that Arc expects, if you like. Alternatively, if you need your own copy
of Python I can provide some advice on that route, but unless you are an
expert Python user, I will be reluctant to spend time on it. Just let me know
your preference..

Best,
Jason


-----Original Message-----
From:
[] On Behalf Of
Sent: Friday, February 9, 2018 4:34 PM
To:
Subject: [mget-help] Can't run data products tools

Hi MGET team--
Thanks for such a great tool! It's been very helpful and saved me a lot of
download/processing time.

I'm currently having a problem similar to what Iason-Zois Gazis described in
December. When I try to create rasters for NASA OceanColor L3 SMI Product, a
red and white X appears next to "Sensor" and hitting OK to run the process
gives a generic yellow triangle with an exclamation point in it. There is no
text, and putting the mouse on either sign does not display any message.
This seems to happen for most of the tools that I tried under Data Products.

I’ve tried a couple of solutions (downloading and overwriting PODAAC.py,
downloading and installing the Windows x86 MSI Installer, reinstalling MGET),
but have not hit upon the correct one.

I’m using ArcGIS 10.4.1, MGET 0.8a69 (just downloaded and tried it), and have
also downloaded Python 2.7 pywin32-222, Python 2.7.14.

Thanks, Julie

---

• [mget-help] Can't run data products tools, jhowar, 02/09/2018
  • RE: [mget-help] Can't run data products tools, Jason Roberts, 02/12/2018
    • RE: [mget-help] Can't run data products tools, Julie Howar, 02/12/2018

---

Archive powered by MHonArc 2.6.19.