+4Hello
Wondering if anyone else has run into these issues when installing FME Flow 2024.1? We’re testing an in-place upgrade process on a development system using the express installation.
Engine name isn’t being updated correctly. We changed the configuration per this post, and appears to resolve the issue .
Also noticing a problem in the “Start FME Server” / "Restart FME Server” workflows. Command line is reporting an error that seems related to the FME Database.
+10Hi
I did some testing regarding the batch file error and have come to this conclusion:
“FME Flow Database” is a dependency of FMEFlowAppServer to run. Because of that, “FME Flow Database” is started alongside the FMEFlowAppServer start call, which is why when “FME Flow Database” is exclusively called, you are getting the error stating that it is already started.
You can disregard this error, and your FME Flow instance should work perfectly fine even if this message is appearing.
+4
