Blank Error message when trying to run Add GTFS to ND

[HilaryPage1]

Hi,

I've successfully used this toolbox for years now, but I'm suddenly stumped.  When I open up the dialog box of one of the scripts in the tool box, I get a red X as you can see on the attached, even when using files and locations I've successful used as input in the past. When I hit OK, I get a blank yellow exclamation mark pop-up error before it even tries to run. I installed the toolbox on this computer in 2017, I believe.

I would just try uninstalling and reinstalling the most recent version, but I'm concerned what that could do to the existing network datasets I have saved on my computer, and the transit evaluator associated with them.

Can anyone help with this?

[MelindaMorang]

Wow, that's a really unhelpful error message.  Sorry about that!  I really don't know what would cause that problem, so I think you're right that uninstalling and reinstalling Add GTFS is a good thing to try.

The transit evaluator is not saved in the network dataset itself.  It's part of the overall tool installation.  Without the tool installed, your network datasets will not work.  However, if you reinstall the evaluator, they should start working again.  They are not going to be permanently broken.

The only exception to this would be if your networks were really really old and I had made some changes to the evaluator itself in a way that was no longer compatible with older networks.  I do that sometimes, since this tool is effectively in permanent beta and not guaranteed to always be backwards compatible.  However, I haven't done anything like that in like 3 years or more, so I don't expect any problems with your networks if you were to uninstall and reinstall the latest version.

Let me know if uninstalling and reinstalling doesn't fix the problem.

[HilaryPage1]

Thanks for the quick reply. Unfortunately, uninstalling and reinstalling (and restarting) didn't help. Do you have any other ideas?

If it's relevant, I have the 64-bit background geoprocessing, ArcMap 10.6 Advanced license.

Also, I've been teaching myself python and it seemed that sometimes there was an issue with having Python 2.7 paths in the ArcGISx6410.6 versus ArcGIS10.6 folders. Do you think that might be an issue? Is it ok to uninstall one or the other?

[MelindaMorang]

A couple of things here related to 64-bit background geoprocessing:

1. If you have the 64-bit background geoprocessing extension installed, you should have two versions of python.  One is a 32-bit python associated with ArcMap,and the other is a 64-bit python associated with the 64-bit background GP extension.  You should keep both of these on your computer.  Do not delete either one, as the product they're associated with will stop working correctly.

2. Since you have two versions of python on your machine, you need to be careful about which one is being used and when.  If you're running a standalone python script, you need to point to the correct python executable for the version of python you intend to use.  If you want to run against ArcMap, use C:\python27\ArcGIS10.6\python.exe.  If you want to run against the 64-bit background GP extension, use C:\python27\ArcGISx6410.6\python.exe.  You will need to use these explicit paths in the command line or configure your python IDE to use whichever of these you want to use.  I'm assuming you want 64-bit since you went to the trouble to install it.  It will be better for solving large problems because it can use all your memory resources.

3. If you're running tools in ArcMap, they will use ArcMap if you have background geoprocessing turned off.  If, instead, you turn background geoprocessing on (Geoprocessing menu -> Options -> Enable background processing checkbox), it will switch over to using the 64-bit background geoprocessing extension.

4. If you want to use the Add GTFS to a Network Dataset tools and the network datasets produced with them with the 64-bit background geoprocessing extension, you have to do an additional installation procedure, as described in the user's guide.  However, the error you're seeing looks unrelated to this.

---

I think your current issue is unrelated to 64-bit background geoprocessing, though.  I see that you have a very large list of input GTFS datasets.  Can you try adding just one of them to the tool dialog?  Do you get the issue if you just have one in there?  If not, can you add them in one at a time until the error appears?  Maybe it's something about a specific dataset, and if that's the case, maybe you can send me that dataset for debugging?

[HilaryPage1]

OK, everything you said makes sense, except I didn't really understand the instructions here: How To: Register function tools (DLL) for both Desktop and 64-bit Background Processing  - I'm not sure whether to pursue it or not, if it doesn't seem to be the problem.  I'm inserting a screencap of the Evaluator Files, in case it helps. 

Otherwise, no, using just one GTFS folder doesn't help.  I have the red X at the top left as soon as I open the dialog box, and hovering over it does not provide any more information. Will try to figure out how to attach the files, just in case.  (I've also tried several different directories individually, and I was able to use them just fine a few weeks ago.)

[MelindaMorang · Accepted solution]

Since you get the error when you first open the tool dialog, before putting any inputs in, then the problem is related to the tool and is not related to your data.

You said everything worked fine just a few weeks ago.  Did you install the 64-bit background geoprocessing extension or make any other changes to ArcMap between then and now?  Did you install Anaconda, by any chance?

Also, try this:

1. Open the python window in ArcMap.
2. Type "import arcpy" (without quotes).

Does this work (ie, do nothing), or does it throw a bunch of errors?  If it throws errors, this means your python installation is messed up somehow, and you'll need to call Esri Support to get it resolved.

[HilaryPage1]

Yep, big old crash.  I'll get in touch with Esri Support, and will provide an update here when everything is sorted.

Thanks again, Melinda.

**Update: All back in working order after a full uninstall and reinstall