I have both installed on the same box. There are DTBGGP64.pth and a Server10.1.pth files in the C:\Python27\ArcGISx6410.1\Lib\site-packages folder. The first points to the the C:\Program Files (x86)\ArcGIS\Desktop10.1\bin64 folder and the second points to the C:\Program Files\ArcGIS\Server\bin folder. This seems to be a conflict.
When I enable background processing and debug into a Python geoprocessing task it fails when arcpy is imported. Printing sys.path reveals:
Note that it is pointing to the 32-bit Desktop bin folder, before the 64-bit Desktop bin64 folder is pointed to. Where is all these extra path entries coming from?
I need to publish the geoprocessing task to Server. In the past we have used ArcMap on the Server box in authoring our web applications, which call a geoprocessing task. Is this not possible anymore?
The two .PTH files are fine. 64bit BG and Server share 64bit Python.
Whats the error you get while importing arcpy?
It looks like you've done the sys.path print from the Python window in ArcMap? Heres the output of print sys.path in the Python window. Not quite the same as yours.
The two .PTH files are fine. 64bit BG and Server share 64bit Python.
As long as any differences between the versions of the arcgisscripting.pyd files at both locations don't cause problems running the same script in Server and ArcMap BGGP64.
Whats the error you get while importing arcpy?
>>> Unhandled exception while debugging... Traceback (most recent call last): File "C:\ARCGIS~1\GEOPRO~1\TGT_GP~1\Scripts\ExportGeoPdfScript.py", line 47, in <module> import arcpy File "c:\program files (x86)\arcgis\desktop10.1\ArcPy\arcpy\__init__.py", line 21, in <module> from arcpy.geoprocessing import gp File "c:\program files (x86)\arcgis\desktop10.1\ArcPy\arcpy\geoprocessing\__init__.py", line 14, in <module> from _base import * File "c:\program files (x86)\arcgis\desktop10.1\ArcPy\arcpy\geoprocessing\_base.py", line 14, in <module> import arcgisscripting ImportError: DLL load failed: %1 is not a valid Win32 application.
It looks like you've done the sys.path print from the Python window in ArcMap?
Yep, I inserted it into my script immediately before the import statement for arcpy.
Do you have Python entries in your actual PATH environment variable? Do you have a PYTHONPATH environment variable pointing at something?
The arcgisscripting.pyd is the same file used in both Server and 64bit BG.
Thats the error I suspected you were getting. Its 32bit trying to call into 64bit. Some wire, somewhere has been crossed and its trying to use the wrong libraries.
Are you running a script tool out of process? If so, can you try running in process?
Any chance your script is calling subprocess or multiprocess? That is, something in your script is making threads or other processes or even doing a os.command?
Any chance your script is calling subprocess or multiprocess? That is, something in your script is making threads or other processes or even doing a os.command?
I use os.getpid(). Why would that cause a problem? I'll try it without. Here's the entire script, up to the point where it blows up:
import sys import string import os import shutil import uuid import platform import getpass import time
I've added the BGGP64 update to another machine with only Desktop 10.1 SP1 installed and am seeing the exact same issue, so it's not the presence of ArcGIS Server that is messing things up. Both machines are Win 7.
Clearly you do have 32-bit paths in your sys.path that do not belong there when you are running the 64-bit python. The question is where they are coming from.
This sure looks like something you'd want to open a support incident to get to the bottom of the issue.
