Skip to main content
Question

Excel reader "Length too short" error


jmcarthur
Contributor
Forum|alt.badge.img+1

Using a reader to consume a pretty basic spreadsheet, but loading it fails with the following message:

 

Excel Reader: Failed to open the dataset 'C:\path\to\file.xlsx'. Error message was 'Length too short' 
A fatal error has occurred. Check the logfile above for details
Failed to read schema features from dataset 'C:\path\to\file.xlsx' using the 'XLSXR' reader

 

This file has ~450 rows. Other files generated by the same system work just fine. The only difference between this file and the last one that worked is row count, around 150.

4 replies

Forum|alt.badge.img+2
  • October 27, 2020

@jmcarthur​  You'll probably either have to attach the data file here or open a case with Safe Support. Please also include the version of FME you're using.


jmcarthur
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • October 27, 2020
markatsafe wrote:

@jmcarthur​  You'll probably either have to attach the data file here or open a case with Safe Support. Please also include the version of FME you're using.

I'll look into opening a support request. I can't post the file as it contains sensitive data, but it appears there might be a row limitation in the Excel reader. I cropped the data to 101 rows (header + 100 rows) and the Reader didn't puke.


jmcarthur
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • October 27, 2020

After deleting all but 100 rows, saving, Ctrl+Z to bring them back, and saving, the dataset was loaded into the reader and the job ran. No idea what's going on with this.


chrisatsafe
Contributor
Forum|alt.badge.img+2
  • Contributor
  • October 28, 2020

It looks like this issue may be isolated to this particular workbook (possible corruption). We found that simply by opening the .xslx file in Excel and saving the file resolved the issue. If you are experiencing the same behaviour, first try opening the file in Excel and saving the file in Excel before reading it into FME Workbench.

 

If that doesn't resolve the issue or if this is occurring with multiple files, please file a case so our team can look into what might be causing this issue!


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings