Bug ID Number |
BUG-000179795 |
Submitted | September 30, 2025 |
Last Modified | October 5, 2025 |
Applies to | ArcGIS Pro |
Version found | 3.5.3 |
Operating System | Windows OS |
Operating System Version | 11.0 64 bit |
Status | In Product Plan
The issue has been added to the development team's backlog. The goal for issues with this status is to address them in a near-term release (next release or two). Check the issue's Additional Information or Alternate Solution section to see if there is helpful information until it can be fully addressed.
|
Additional Information
The use of Python and Excel in the same workspace is required to reproduce the issue. The fix for this issue is in FMEENGINE-87239. This behavior is first reported in FME 2025.0 (ArcGIS Pro 3.5) and fixed in the upcoming release FMEEngine 2025.1 (ArcGIS Pro 3.6).
The root cause is that an incorrect libxl.dll file is loaded by FME when ArcPy is imported in workspaces that use Excel formats, for example, an Excel format reader (explicitly with a startup script or PythonCaller) and SchemaMapper (implicitly). The workaround is to downgrade ArcGIS Data Interoperability to ArcGIS Pro 3.4 or use an alternative format to Excel, such as CSV.
Workaround
Switch from using Excel files in the SchemaMapper to another format like CSV. Since the SchemaMapper uses ArcPy to import the Excel worksheet, changing the lookup table to CSV helps avoid the error.
Steps to Reproduce