Skip to main content
  • EN

Hi all,

I am currently using ArcPro 3.5 DI tool that uses,

FME(R) 2025.0.0.0 (20250228 - Build 25208 - WIN64)

Some of my FME scripts are failing when reading an excel file if it as a python start up script that imports arcpy specifically. If i remove arcpy, the excel reader works fine.

Is this a bug with the FME build that came with our ArcPro 3.5 or is it consistent with a stand-alone FME install?

Some of the warnings are:

----------------------------------------------------------

The Startup Python Script changed the current FME process locale from 'English_New Zealand.utf8' to 'English_New Zealand.1252' and FME has restored it back to 'English_New Zealand.utf8'. It is undefined behavior to change locale and doing so may cause unexpected errors. For more information, visit http://fme.ly/PythonLocaleError
-----------------------------------------------------------

Excel Reader: Could not read cell at row '0', column '1' for sheet 'can't read more cells in trial version'. Error message is 'can't read more cells in trial version'. This cell value will be skipped
 

Cheers

Chris

I believe these are two unrelated errors.

I saw the Excel error with another user reading an Excel worksheet on a SchemaMapper, I tried the same workspace in FME Form 2025.1 and the error is not reproducible. His co-worker also reported the same error with a similar workspace. They have licensed versions of Microsoft 365 and I cannot reproduce their errors. I suggest submitting this as a case to ESRI Support.

For the python error, please run your workspace and show a screen capture of your translation log. Below is mine using a random workspace.

 

 

Thanks for the feedback.

Yep it maybe ESRI’s issue withe FME 2025 build they packaged with their data interoperability extension tool. I will raise it with them as well.

Thanks for the feedback.

Yep it maybe ESRI’s issue withe FME 2025 build they packaged with their data interoperability extension tool. I will raise it with them as well.

The Python and Excel issues are mutually inclusive. The fix to this issue is in FMEENGINE-87239. This behaviour was first reported in FME 2025.0 (Pro 3.5) and has been fixed in upcoming release 2025.1 (Pro 3.6). The root cause is the incorrect libxl.dll is loaded by the Workbench app when arcpy is imported on workspaces that use Excel formats - e.g. Excel format reader (explicitly with a startup script or PythonCaller) and SchemaMapper (implicitly).  The suggested workaround is to downgrade Data Interop to Pro 3.4 or use an alternative format to Excel, like CSV.

Community Stats

31,923
Posts
121,242
Replies
39,545
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.