Hi,
For some time, I used the following approach to open a KML dataset (both in Desktop for development, and in Server for operational use, version 2020.1.0.1, both running on Windows (server) OS):
- Create a public parameter "INPUT_FOLDER"
- Create a public parameter "INPUT_FILE"
- Add a KML Reader for a specific KMl file to the workbench, which defaults to a public parameter "SourceDataset_OGCKML"
- Make this a private parameter, and change the definition to: "$(INPUT_FOLDER)\$(INPUT_FILE)"
I then use either UNC or local paths in the INPUT_FOLDER to point the reader to the correct location.
Last week, we started migrating to 2021.2.4, which I installed on my workstation (windows). For the sake of completeness I think I should mention we are targeting an FME server running in a docker container on a linux host.
This approach stopped working, with the message :
2022-03-19 14:58:52| 0.8| 0.0|INFORM|Loaded module 'OGCKML' from file 'C:\Program Files\FME\2020.1.0.1\plugins/KML21.dll'
2022-03-19 14:58:52| 0.8| 0.0|INFORM|FME API version of module 'OGCKML' matches current internal version (3.8 20200115)
2022-03-19 14:58:52| 0.8| 0.0|FATAL |KML: Cannot open dataset `C:\TestData\kml\msg_kml_samples\Bunker Ports.kml'
2022-03-19 14:58:52| 0.8| 0.0|FATAL |KML: Error initializing readerOddly enough, this error happens on both the window FME Server and with Desktop.
Even more confusing is the fact that when I download the workbench from the FME server, it does run when I do this for the first time, it fails running it a second time (see attached logfiles).
I have tried to add a new KML reader to the workbench. When I use a specific file, this works. When I apply the approach outlined above and point it to the existing private parameter, it fails again.
I do not understand what is going wrong, and I'm running out of options to try. Can anyone please assist me here?