Hi, We have a workspace that runs fine on our FME Server testing environment yet crashes on our user acceptance environment. It crashes on version incompatibility, like described in the article at https://knowledge.safe.com/articles/363/workspace-fails-on-fme-server-fme-version-incompat.html.
Granted, we use FME Server build 17650/win64/2017.1.1.0 and FME Desktop build 17652/win64/2017.1.1.1. that would be a cause for not running a workspace due to compatibility issues.
However, this baffles me: FME Server version is the same, workspace is the same, what else could cause this behaviour?
I narrowed it down to the workspace below, which is basically a SpatialRelator comparing two box-like area's. Our testing environment runs it just fine, and concludes in the log:
2019-10-09 12:23:30| 0.3| 0.0|INFORM|Loaded module 'SpatialRelationshipFactory' from file 'D:\Prog\FME\FMEServer\Server\fme\plugins/SpatialRelationshipFactory.dll'
2019-10-09 12:23:30| 0.3| 0.0|INFORM|FME API version of module 'SpatialRelationshipFactory' matches current internal version (3.8 20170315)
2019-10-09 12:23:30| 0.3| 0.0|INFORM|Emptying factory pipeline
Our user acceptance environment is however very strict, and for the same workspace it concludes:
2019-10-09 12:00:37| 0.1| 0.0|WARN |Library 'D:\Prog\FME\FMEServer\Server\fme\plugins/SpatialRelationshipFactory.dll' was found but could not be loaded. Ensure that all the dependent modules exist for this library
2019-10-09 12:00:37| 0.1| 0.0|ERROR |This FME edition does not recognize the `SpatialRelationshipFactory' factory. Please ensure that the current platform supports this factory, the factory name is spelled correctly, and that you have installed all required plug-ins
and terminates the job.
Workspace:
Yeah, true, it's not an AreaOnAreaOverlayer but it is a SpatialRelator, however, using an AreaOnAreaOverlayer does not produce a crash.
Any ideas?
Best answer by mark2atsafe
View original