Skip to main content
Question

Encoded string not valid on GEODATABASE_SDE writer

  • January 8, 2024
  • 1 reply
  • 154 views

waterbeemds
Contributor
Forum|alt.badge.img+3

Hello,

 

We recently upgraded from FME version 2022.0.0.0 (20220428 - Build 22337 - WIN64) to 2023.1.1.1 (20231011 - Build 23636 - WIN64).

After the upgrade one of my tools gives the following error:

GEODATABASE_SDE writer: The encoded string is not a valid US-ASCII string: ''AsfaltverhardingPlaatsori\\xC3\\xABntatie''

 

This happens at a GEODATABASE_SDE writer. The writer uses the following settings:

Feature operation: fme_db_operation

Table handling: Use Existing

Update Spatial Column(s): Yes

Actions preceding the writer determine what kind of db operation is needed

 

Problem: It tries to process a 'ë' but fails to do so

 

After some debugging and looking at other similar questions on the forum, I think it has to do with the locale/character set. In FME 2022 the process encoding was set to UTF-8.

When I look at the locale/encoding used in our ArcGIS Pro enviroment (3.1.3) via Python I get 'Dutch_Netherlands, 1252'. This mismatches with encoding used by FME in the proces.

 

Is there a solution for this problem? If any other information is needed, feel free to ask.

 

Thanks!

1 reply

kailinatsafe
Safer
Forum|alt.badge.img+19

Hello there @waterbeemds​, thanks for posting! Suspect you've hit FMEENGINE-80388, which was related to special characters and the GEODATABASE_SDE writer failing. I believe the issue has been resolved in FME Form 2023.1 23638+ (as well as 23.2 and 24.0), which is available on the Downloads Page. Please reach out again if upgrading does not resolve the issue. Happy FMEing, Kailin.


Reply


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