Hello @annafor​ what is the error? Are you receiving it from the app's web page or after submitting the job via the app? I'd suggest reviewing any file resources and connections the workspace may be using and ensuring that other users have access.

We also have a troubleshooting guide for FME Server Apps that may help: https://community.safe.com/s/article/FME-Server-Troubleshooting-Server-Apps

Hello @mattmatsafe​

From the app's  web page i get "FAILURE" as a respons. The log file contains warning messages but I am uncertain that those warnings should make the skript fail. I have attached the log file.

Thanks @annafor​, the log file abruptly ends, which indicates the engine running it is likely crashing. Which is very unusual, since it runs successfully as a standalone job. Do other .shp files cause the error or just this one? I haven't seen that warning before, I'm wondering if the .shp file may be corrupt.

I would recommend taking a deeper look at the other log files, especially the <FMEServerSystemShare>\\resources\\logs\\core\\current\\fmeserver.log, to see if there is more information, but this may require a case creating a case.

Hi @mattmatsafe​, attached is a part of the log file from <FMEServerSystemShare>\\resources\\logs\\core\\current.

We have tested different cases and found the following:

Fail:

1. Script/server apps where a user uploads a .shp file (a temporary folder is created here: FME_SHAREDRESOURCE_SYSTEM/temp/upload) and the script contains custom transformers which is based on python.

Success:

1. Script/server apps where a user uploads a file. (No python in the script)
2. Script/server apps with a UNC path to a .shp and the script contains custom transformers which is based on python.

We use python 3.8+. This is our Startup Python Script:

global TIME_START

from datetime import datetime

TIME_START = datetime.now().strftime('%Y-%m-%dT%H:%M:%S')

LOG_LIST = G]

Do you have any ideas?

Hi @annafor​ , have you tried setting the Python compatibility to 3.8? This can be set for the workspace in FME Workbench under workspace parameters > scripting > Python Compatibility. If that works, you can also set 3.8 as your preferred python interpreter for future workspaces by going to Tools > FME Options > Translation.

Hi @mattmatsafe​, yes we have set the Python compatibility to 3.8 in the workspace!

Ok, thank you @annafor​ . I would suggest reaching out to your partner to take a closer look at this. If they are unable to determine why the engine is crashing, they can always create a support case with us to help investigate.