I'm having a strange problem this morning that I've seen mentioned a couple time here on the forum without resolution.
Suddenly (as in, has changed in the last couple weeks) I am unable to access SDE connections through an external python interpreter (that is, one that is outside of ArcMap or ArcCatalog).
From within Arc's python window something such as
print [i.name for i in arcpy.Describe(r'path_to_sde_connections\user@current_sde_version.sde\dataset\feature_class').fields]
will work perfectly fine, but in an interpreter (the same version/site-packages as used by Arc) it will fail:
Traceback (most recent call last): File "<stdin>", line 1, in <module> File "C:\Program Files (x86)\ArcGIS\Desktop10.2\arcpy\arcpy\__init__.py", line 1234, in Describe return gp.describe(value) File "C:\Program Files (x86)\ArcGIS\Desktop10.2\arcpy\arcpy\geoprocessing\_base.py", line 374, in describe self._gp.Describe(*gp_fixargs(args, True))) IOError: "path_to_sde_connections\user@current_sde_version.sde\dataset\feature_class" does not exist
path_to_sde_connections\user@current_sde_version.sde\dataset\feature_class being a placeholder, this is generalized and has been tried with a number of sde connections, this print cmd works on non-sde gdbs.)
This is resulting in a script that I used and ran last month only working form being loaded into a python window within arc, where before I could run it from the command line.
Has anyone seen this before, or perhaps found a solution?
I can't begin to understand why suddenly this would occur. This is after a system reboot to ensure it would be conflict/lock-free. The only recent things I've done would be a pip update of lxml and pandas—which shouldn't be effecting it, as it works from within Arc.