Skip to main content
Solved

Job termination due to version difference on micro level

  • October 9, 2019
  • 4 replies
  • 13 views
helmoet
Forum|alt.badge.img+8

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

I searched in our systems and I don't see this DLL fail to load before except in the case where it had been quarantined by a virus scanner. Could that be the case here?! Another reason could be the FME license type. Is it possible that the two systems are using different licenses?

I can't imagine it's a conflict with a DLL from another product with the same name (as has sometimes happened). Do you have multiple FME versions installed on that system?

You could try using a tool like Dependency Walker which might highlight what the issue is, although I tried it on my functioning version and still got warnings, so I don't know how useful it will be.

If nothing here helps, then I would file this as a support case and ask our team to check with the developers.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

helmoet
Forum|alt.badge.img+8
  • helmoet
  • Author
  • 195 replies
  • October 9, 2019

Oh, forgot to tell, SpatialRelationshipFactory.dll have the same date/version/size etc on both servers.

erik_jan
Contributor
Forum|alt.badge.img+22
  • erik_janContributor
  • Contributor
  • 2179 replies
  • October 9, 2019

Nothing about SpatialRelator in the change logs for these versions (2017.1.1.*).

I would send a question to www.safe.com/support

mark2atsafe
Safer
Forum|alt.badge.img+56
  • mark2atsafeSafer
  • Safer
  • 2554 replies
  • Best Answer
  • October 9, 2019

I searched in our systems and I don't see this DLL fail to load before except in the case where it had been quarantined by a virus scanner. Could that be the case here?! Another reason could be the FME license type. Is it possible that the two systems are using different licenses?

I can't imagine it's a conflict with a DLL from another product with the same name (as has sometimes happened). Do you have multiple FME versions installed on that system?

You could try using a tool like Dependency Walker which might highlight what the issue is, although I tried it on my functioning version and still got warnings, so I don't know how useful it will be.

If nothing here helps, then I would file this as a support case and ask our team to check with the developers.

FME Evangelist to the Rich and Famous!!
mark2atsafe
Safer
Forum|alt.badge.img+56
  • mark2atsafeSafer
  • Safer
  • 2554 replies
  • October 9, 2019

I searched in our systems and I don't see this DLL fail to load before except in the case where it had been quarantined by a virus scanner. Could that be the case here?! Another reason could be the FME license type. Is it possible that the two systems are using different licenses?

I can't imagine it's a conflict with a DLL from another product with the same name (as has sometimes happened). Do you have multiple FME versions installed on that system?

You could try using a tool like Dependency Walker which might highlight what the issue is, although I tried it on my functioning version and still got warnings, so I don't know how useful it will be.

If nothing here helps, then I would file this as a support case and ask our team to check with the developers.

Also check the properties of spatialrelationshipfactory.dll to see what the permissions and security settings are.

FME Evangelist to the Rich and Famous!!

Community Stats

32,079
Posts
121,811
Replies
39,714
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.