I recently upgraded to Arc Pro v3.4.0 and wanted to calculate the geometry of an attribute. I added a numeric field to the layer, then highlighted the attribute and went to calculate the geometry. When I selected it I received the error message below. I have tried the simple turn on and off again option and that did not work.
Any idea how I could fix this?
Note, I am able to calculate the geometry in ArcGIS pro v3.2.0 which I have access to on another PC but would like to see this issue resolved in v3.4.0. I
--------------------------------------------------------------------
'management.CalculateGeometryAttributes'
initializeParameters Error: Traceback (most recent call last):
File "c:\program files\arcgis\pro\Resources\ArcToolbox\toolboxes\Data Management Tools.tbx\CalculateGeometryAttributes.tool\tool.script.validate.py", line 1, in <module>
import arcpy
File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\__init__.py", line 101, in <module>
from arcpy._version import __version__, version
File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\_version.py", line 192, in <module>
version = Version()
^^^^^^^^^
File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\_version.py", line 27, in __init__
self.data = self._get_installation_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\_version.py", line 96, in _get_installation_data
tree = etree.parse(fpth)
^^^^^
UnboundLocalError: cannot access local variable 'etree' where it is not associated with a value
Hello @MelissaWalker , do any of the Analysis tools work for you in your ArcGIS Pro 3.4.0 ? The "line 96, in _get_installation_data" part of the error message seems to be looking for some fundamental installation information from the ArcGIS.Installation.xml file.
I am having a similar issue. I use the measure tool for a line and get 26' but when I use the calculate geometry in the attribute table I get 56'. Any suggestions?
Thank you.
I just ran into a similar error - upgrading the 'lmxl' package from 5.3.0 to 5.3.1 appears to have fixed the issue.