Skip to main content
Solved

Fatal error after upgrading to 2019

  • August 12, 2019
  • 2 replies
  • 61 views

Forum|alt.badge.img

Hello,

 

after upgrading to FME 2019 from 2018 my workspace stopped working with error

Saving spatial index into file 'C:\\Users\\dusan\\AppData\\Local\\Temp\\wb-cache-Konacni_model_jul-KaOtqX\\Main_FeatureMerger_4 -1 298 fo 4 _lt_REJECTED_gt_ 0 82253bb54d545775c6265f622c6bd44f5854eccb.fsi'

Finished saving spatial index into file 'C:\\Users\\dusan\\AppData\\Local\\Temp\\wb-cache-Konacni_model_jul-KaOtqX\\Main_FeatureMerger_4 -1 298 fo 4 _lt_REJECTED_gt_ 0 82253bb54d545775c6265f622c6bd44f5854eccb.fsi'

Transcoding the binary string '1`\\xA8\\x83\\x191\\x02\\x00\\x00\\x00H\\xE1z$\\x04\\x14YA\\xB8\\x1E\\x85\\x8B\\x03\\x14YA\\xD7\\xA3p\\xAD\\xA4bRA333s\\xA5bRA\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x001\\x00\\x00\\x00\\x00\\x02\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\xF8\\x00\\x00\\x00\\x00\\x00\\x00\\xF8\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00' to another encoding can not be done

A fatal error has occurred. Check the logfile above for details

 

Can someone help me because this is the first time this happend to me.

Best answer by takashi

Hi @luckym, this looks like an internal bug on handling non-ASCII character encoding. I would recommend you to send a workspace and sample dataset which reproduce the error to Safe support, in order to let them closer look at this.

Report a Problem - select "Defect" in 2. Type of Inquiry

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

takashi
Celebrity
  • 7843 replies
  • Best Answer
  • August 12, 2019

Hi @luckym, this looks like an internal bug on handling non-ASCII character encoding. I would recommend you to send a workspace and sample dataset which reproduce the error to Safe support, in order to let them closer look at this.

Report a Problem - select "Defect" in 2. Type of Inquiry


Forum|alt.badge.img
  • Author
  • 39 replies
  • August 12, 2019

Hi @luckym, this looks like an internal bug on handling non-ASCII character encoding. I would recommend you to send a workspace and sample dataset which reproduce the error to Safe support, in order to let them closer look at this.

Report a Problem - select "Defect" in 2. Type of Inquiry

Thank you @takashi. I reported problem under case number C147344.