Skip to main content
  • EN

Hi.

I originally had some issues with 2019.0 om my home pc with a home license. It crashed every time I added a Tester or a TestFilter transformer: https://knowledge.safe.com/questions/90340/fme-20190-problems.html

These problems were solved in later builds, and neither 2019.2 nor 2020.0 crashes like this anymore.

 

However, I just accidently ran into other similar problems with both 2019.2 and 2020.0 (and even 2018.1) on the same pc.

Now it's the transformers AttributeFilter and AttributeValueMapper that makes FME crash immidiatedly.

And I noticed that the Sorter transformer doesn't provide any attributes for the sort value either.

Luckily both versions work on my office pc, but I would very much also like FME to work properly at home.

 

Are there any information I can provide that'll help find the source of my problems ?

I did check the "Improve FME by reporting ...", but I suspect it doesn't work when FME crashes.

The pc in question is Windows 10 Pro version 1903 build 18362.720.

Thanks.

Add ParameterFetcher to the list :-(

@lifalin2016 Since this is a persistent problem with your FME installations (as per your previous report), you probably need to follow the steps in General Troubleshooting | Gathering System Information and then file a support case with your FME provider.

@lifalin2016 Since this is a persistent problem with your FME installations (as per your previous report), you probably need to follow the steps in General Troubleshooting | Gathering System Information and then file a support case with your FME provider.

Thanks Mark.

I noticed something peculiar.

The PythonCaller works in 2020.0, but it uses the dialog design from a previous versions, not the new design with the code immidiatedly available.

It got me thinking that it might be a cross-version issue, i.e. 2020 is forced to use older code, that may or may not work in 2020 ?

If so, how to determine and remedy it ? I have 2020.0 and 2019.2 (and 2018.1 for test) installed.

@lifalin2016 Since this is a persistent problem with your FME installations (as per your previous report), you probably need to follow the steps in General Troubleshooting | Gathering System Information and then file a support case with your FME provider.

Support case submitted

@lifalin2016 Since this is a persistent problem with your FME installations (as per your previous report), you probably need to follow the steps in General Troubleshooting | Gathering System Information and then file a support case with your FME provider.

I created a small screen-capture video of what I experience: https://1drv.ms/u/s!AoKimG4hP7_ZiaVR_Gq0ido2uV889g?e=eaCLzD

@lifalin2016 We had an similar issue were it chrashed when simply using a creator and a pythoncaller. On the computer we also hade ARCGIS installed and there was a system environment variable set to PYTHONPATH = C:\\Python27\\ArcGIS10.5\\Lib

Removing or redirecting this to another directory solved our problem.

@lifalin2016 We had an similar issue were it chrashed when simply using a creator and a pythoncaller. On the computer we also hade ARCGIS installed and there was a system environment variable set to PYTHONPATH = C:\\Python27\\ArcGIS10.5\\Lib

Removing or redirecting this to another directory solved our problem.

Thanks serenon.

There are indeed multiple setups that may trip FME. Mine was another, which was solved during the support case.

I'm utilizing FME Shared Folders, and apparently the file "fmesuite.fmx", which contains the definitions for all the standard transformers, had been copied from the FME_HOME/transformers folder to the shared transformers folder by mistake.

The problem is, that this file is version dependent, so being shared, it was read by FME in any version, and crashed several standard transformers depending on which version was running.

 

Removing the file in its shared location solved the problem.

 

Reply


Community Stats

30,194
Posts
114,615
Replies
37,857
Members
Terms & ConditionsCookie settings
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.