Has anyone experienced FME crashes when importing arcpy in a 64 bit FME from ArcGIS 10.4.1.
The arcpy from ArcGIS 10.3.x has no issue with 64 bit FME, and the 10.4.1 works with 32 bit FME.
In 32-bit I'm pointing to C:\\Windows\\SysWOW64\\python27.dll
In 64-bit I'm pointing to C:\\Windows\\System32\\python27.dll
If I use any other interpreter I get the "no module named arcpy" error.
I did notice that in your post, you have the 32-bit pointing to 64-bit Python and vice-versa. Is this a typo? Also, have you tried installing the ArcGIS 64-bit Background Geoprocessing plugin? If I am using ArcGIS and 64-bit FME, I always install the geoprocessing plugin that matches the version of ArcGIS that I have installed - I am wondering if this could help.
I did notice that in your post, you have the 32-bit pointing to 64-bit Python and vice-versa. Is this a typo? Also, have you tried installing the ArcGIS 64-bit Background Geoprocessing plugin? If I am using ArcGIS and 64-bit FME, I always install the geoprocessing plugin that matches the version of ArcGIS that I have installed - I am wondering if this could help.
If using 32-bit FME, the path to the ArcGIS Python Interpreter will resemble the following:
C:\\Windows\\SysWOW64\\python27.dll
If using 64-bit FME, the path to the ArcGIS Python interpreter will resemble the following:
C:\\Windows\\System32\\python27.dll
I do have the 64 bit geoprocessing plugin installed.
If using 32-bit FME, the path to the ArcGIS Python Interpreter will resemble the following:
C:\\Windows\\SysWOW64\\python27.dll
If using 64-bit FME, the path to the ArcGIS Python interpreter will resemble the following:
C:\\Windows\\System32\\python27.dll
I do have the 64 bit geoprocessing plugin installed.
@MarkAtSafe, do you have any insight, since you edited the previously mentioned article?
If you have several Python interpreters on the same machine, make sure to point the PYTHONHOME environment variable to the correct installation directory. Just specifying the pythonxx.dll isn't always enough.
If you have several Python interpreters on the same machine, make sure to point the PYTHONHOME environment variable to the correct installation directory. Just specifying the pythonxx.dll isn't always enough.