Skip to main content

Running a simple script of point cloud to Las in FME 2020 desktop. My input is five .e57 files. The script fails after writing the first Las file with the error message: E57 reader:

E57 reader: An error occurred while reading. The error was 'checksum mismatch, file is corrupted (E57_ERROR_BAD_CHECKSUM)' with context 'fileName=C:\\1-Working\\GDB\\E57\\1-01-C-01_200219-0.e57 computedChecksum=10167370 storedChecksum=2581601340 page=2465744 length=4044457984' (error code = 16)

FFS writer: Failed to get block of 10000 points starting at index 167600000

Stored 1 feature(s) to FME feature store file `C:\\Users\\Employee\\AppData\\Local\\Temp\\wb-cache-e572las-IwHIxO\\Main_point_cloud -1 2 -1 0 5593c33571a1202057291a33f5c5400df0f2e01f.ffsupdating'

Saving spatial index into file 'C:\\Users\\Employee\\AppData\\Local\\Temp\\wb-cache-e572las-IwHIxO\\Main_point_cloud -1 2 -1 0 5593c33571a1202057291a33f5c5400df0f2e01f.fsi'

Finished saving spatial index into file 'C:\\Users\\Employee\\AppData\\Local\\Temp\\wb-cache-e572las-IwHIxO\\Main_point_cloud -1 2 -1 0 5593c33571a1202057291a33f5c5400df0f2e01f.fsi'

point_cloud Feature Recorder -1 2147549186 (RecorderFactory): Failed to write feature data to `C:\\Users\\Employee\\AppData\\Local\\Temp\\wb-cache-e572las-IwHIxO\\Main_point_cloud -1 2 -1 0 5593c33571a1202057291a33f5c5400df0f2e01f.ffsupdating'

Saving spatial index into file 'C:\\Users\\Employee\\AppData\\Local\\Temp\\wb-cache-e572las-IwHIxO\\Main_point_cloud -1 2 -1 0 5593c33571a1202057291a33f5c5400df0f2e01f.fsi'

Finished saving spatial index into file 'C:\\Users\\Employee\\AppData\\Local\\Temp\\wb-cache-e572las-IwHIxO\\Main_point_cloud -1 2 -1 0 5593c33571a1202057291a33f5c5400df0f2e01f.fsi'

Failed to write feature data to `C:\\Users\\Employee\\AppData\\Local\\Temp\\wb-cache-e572las-IwHIxO\\Main_point_cloud -1 2 -1 0 5593c33571a1202057291a33f5c5400df0f2e01f.ffsupdating'

Translation FAILED with 4 error(s) and 1 warning(s) (0 feature(s) output)

FME Session Duration: 28.7 seconds. (CPU: 16.4s user, 11.9s system)

END - ProcessID: 15616, peak process memory usage: 45600 kB, current process memory usage: 45600 kB

Failed to write feature data to `C:\\Users\\Employee\\AppData\\Local\\Temp\\wb-cache-e572las-IwHIxO\\Main_point_cloud -1 2 -1 0 5593c33571a1202057291a33f5c5400df0f2e01f.ffsupdating'

Program Terminating

Translation FAILED.

The same files in a similar scenario (pulling input files from local drive and writing to local drive) have been output with success from another computer with another FME license.

Is this a permissions issue? I recently updated to 2020, perhaps I did not install a required element? I'm also wondering if maybe it is an issue with default folders?

Just a hunch... how much free space is there on the drive where your temporary files are stored?


That's difficult to tell if it's really the reader or writer that's failing? Can you read the source data into the FME Data Inspector? Or can you put a FeatureHolder transformer between the reader and writer in the workspace? Both of these methods will show if the reader is working correctly.

If FME reads the data correctly, then check the writer, in particular the permissions on the output folder. If it can't, then perhaps as @redgeographics points out, it is a shortage of temporary space, or the file might actually be corrupted as it suggests!


Just a hunch... how much free space is there on the drive where your temporary files are stored?

The drive has 219 GB free.


Thank you for your help. I have been able to successfully run the script. It seems as though it was a corruption of the data when copying it from our server to a local drive.
Thank you for your help. I have been able to successfully run the script. It seems as though it was a corruption of the data when copying it from our server to a local drive.
hello, @heather4624

 

 

How did you solve this? Was there a special way of exporting the data?

 

 


@andreasb

I'm not sure if by exporting you mean pulling the data down off the server. If so, it was just a copy and paste from the server to my local drive. I find that my point cloud scripts work faster (and have less of a chance of timing out and failing) if FME is pulling from a local drive. This was an interesting case because myself and a coworker used 2 of the same datasets pulled off of our server to test the script. Both of mine returned with the checksum error while his processed. Literally both of my datasets were corrupted during the move to the local. But third time is the charm and it worked as expected. Sorry that I can't be of more help. I think there just might have been some type of disruption when moving the files the first 2 times.


Reply