Hi @zzupljanin, I'm sorry to read about this - how inconvenient! This is definitely not normal behaviour. If you are still experiencing this issue there is some additional information that would prove very useful to diagnose the root cause:
- What type of FME Server architecture do you have? (e.g. Express, Distributed Database, Active/Passive)
- Have you performed any post-installation configurations? (e.g. Change Hostname, Change Database, Configure for HTTPS/SSL)
- What version and build of FME Server do you have? (e.g. 2017 Build 17291)
The fmeserver.log is often very useful to analyze for any errors. It is located in <FMEServerSystemShare>\\resources\\logs\\core\\current – and the <FMEServerSystemShare> defaults to C:\\ProgramData\\Safe Software\\FME Server\\.
Ideally, restart FME Server and perform the steps to reproduce the error before collecting the fmeserver.log file.