It could be related to low disk space, triggering aggressive cleanup tasks. Could you doublecheck that?

Hello, thank you for your response. Yes we checked that - I forgot to write it down here. There is enough space and also the critical cleanup is set up to check disk every 5 minutes and every translation crashes in first second. So I think it is not the reason.

I see you registered a case with our support team. That's good. I think this is the sort of error message we should look into immediately. I searched through our systems and I see no report of this error message before, so whatever the cause it looks like it is unique.

Does this happen on the workspaces installed with Server? For example the ones under the Samples repository. Or is it only on workspaces that you've published to the Server?

Hi Mark, it is happening both on our own workspaces and also on Samples installed with Fme Server.

Here are some screenshots from the web UI - workspace austinDownload:

Error in Result Data is the same:

Hey I had the same problem! It resolved (for a reason I can't explain) when I add the log parameter into my FME Desktop before publishing. Now everything is OK.

Hello, I think that this works in FME Desktop. But I think it has no influence on how the workspace works on FME Server.

OK, I was wondering if there was something in the workspaces causing a log location override, but that doesn't seem to be the case. I think we'll have to wait for the support experts to get back to you. They'll probably know more about it than I. But it's hard to see beyond a permissions issue.

The problem was in priviliges. The owner of the "jobs" folder was "root" instead of "fmeserver". After changing this the server works fine now. But we do not know what caused this confusion in priviliges. Probably the upgrade.

Thanks to the Safe support team!