Hi folks, how can I resolve the error below;
2024-09-06 07:06:19| 1.5| 0.0|ERROR |BADNEWS: No MULTI_WRITER dataset name was specified (couldn't find a value for `PRIMARY_DEST_DATASET' or `MULTI_WRITER_DATASET')
2024-09-06 07:06:19| 1.5| 0.0|ERROR |(D:\code\fme\source\engine\core\engine\writrimp.cpp:672) class StatusInfo __cdecl STFWriterImp::getDataset(class stk::ex::UString<0> &) const
Question
Geodatabase writer error
+28- Enthusiast
+64- Celebrity
What are you trying to write out to? We don’t really have enough information to go on with the above
+3- Contributor
Same problem trying to write to ESRI gdb native format
“Esri Geodatabase (File Geodb)”
Attatched a very simple workspace that throws an error in 2024.1 but works in 2022.1 (Have to replace the creator)
Running with Version combinations:
FME(R) 2024.1.0.0 (20240628 - Build 24612 - WIN64)
FME(R) 2022.1.3.0 (20220928 - Build 22630 - WIN64)
ESRI: ArcGis Pro 3.3.1
The 2022.1 versions throws warnings but it does the job..
+31- Influencer
The BADNEWS message usually appears when you have the ‘Log Debug’ option turned on. Unless you are having specific issues, I would turn that off. These messages can generally be ignored, unless you are working directly with Safe to debug.
+3- Contributor
The BADNEWS message usually appears when you have the ‘Log Debug’ option turned on. Unless you are having specific issues, I would turn that off. These messages can generally be ignored, unless you are working directly with Safe to debug.
Of course. I turned this option on after trying to solve the problem in normal mode.
But hopefully the debug option would clearify why the writer does not work.
+3- Contributor
Update on this topic:
This solved my problem:
Reinstalled FME (2024.1) and ArcGis Pro (3.3.1)
Changed language & Rewgion settings to English (US) only keeping my Norwegian language for the correct keyboard settings
FME
Esri ArcGIS Compatibility = Esri ArcGIS Pro:
Python scripting = Esri ArcGIS Python 3.11
+28- Enthusiast
Thanks folks, it’s was a great feedback, it shows that our community is alive.. Unchecking “Log Debug” was able to solve the error.