When you published the workspace, did you specify Job Submitter as the service or Data Download?
Data downloader. But as I specified in my question, the script in FME server does not have problem creating other geopackage files for polygons except for points that are created with vertexcreator in the script. I tried to use Coordinatesystemsetter to specify the coordinatesystem but without any success.
Okay, just to make sure: FME Server can actually access those Excel files, right (it's just that in the workspace the file paths indicate they're stored in somebodies Windows user profile)
Are you getting any error messages in the job log?
Yes FME server can access those Excel files (drag and drop). But the problem lies when I want to write to a geopackage in FME Server. The vertexpoints that area created in the script wont be created in the Geopackage file. I have attached the logfile.
Yes FME server can access those Excel files (drag and drop). But the problem lies when I want to write to a geopackage in FME Server. The vertexpoints that area created in the script wont be created in the Geopackage file. I have attached the logfile.
Please ignore error messages like "Value of field 'info1' has 26 characters, whereas maximum allowed is 6." I have tried to change it without any success of writing to the geopackage file.
@Hans van der Maarel have you had the time to read the logfile?
When I read the logfile I find something weird. When the script is writing to the geopackage file for my vertexpoints the logging looks like this:
Does anyone know why its adding featuretype namn_adresser_koordinater00 and namn_fastigheter_koordinater00? Why the 2 "00" in the end. I just dont understand it. My feature types are called namn_adresser_koordinater and namn_fastigheter_koordinater.
Hi,
The problem with this issue was a difference in versions between workbench and server. I have FME server version 2020.3 and FME workbench 2020.2. However the new excel columns that I added in the reader in FME workbench 2020.2 is not compatible with FME server version 2020.3. The solution was to upgrade my FME workbench to 2020.3 (same version as FME server).