Can't reproduce that here, first thing I would try is re-installing and/or trying it on a different computer.

It kinda defeats the purpose to install on a different computer, doesn't it ? ;-)

I was unable to reproduce the issue with build 19238 (Win64) on my PC.

Try re-installing FME. If that doesn't work, you'll probably have to contact Safe support.

So I tried to install the 32 bit version too, and it shows the exact same symptoms. It's not even only related to the Tester transformer, the TestFilter transformer does the same thing. I sampled most of the transformers before and after these two in the alphabetically sorted list, and none crashed FME.

It may very well be something on this computer, but FME needs to run on it, and I can only perform the install, and report the error. What else can I report? It's a Win10 x64 with Home Edition and 32 Gb RAM and lots of HDD.

Try the instructions here: https://knowledge.safe.com/articles/714/general-troubleshooting-gathering-system-informati.html

Eventually: https://knowledge.safe.com/articles/692/a-guide-to-interpreting-the-system-information-bat.html

I tried to replace build 19238 with 19236 (RC), but it changed nothing :-(

So I finally got something to work. I copy'n'paste'd all transformers to 2019 except for Tester's. I then replaced these with PythonCaller's that did the same testing. This worked.

But then it wouldn't load my custom Python based transformers, even though I switched the compatability to Python 2.7, and even though they're located in my shared folders. Only when I copied the transformer to the "Workspaces" (shared) folder would it find (and use) it.

And then the Data Inspector crashed, after Visual Preview crashed.

Hmmmmm.

Hi @lifalin2016, Sorry to see that you've been having some issues with FME 2019. Just curious, were you able to get this issue resolved yet? If you haven't yet done so, please follow the link david_r shared, and use the bat file provided to gather some system info, and send it to us through this form: https://www.safe.com/support/report-a-problem/. We will investigate this further.

Alas no.

But I did encounter a similar error with a couple of other programs on the same machine, errors I haven't seen before. So it may be a Windows (update?) problem.

The machine is running on Windows 10 Home. Is that a problem ?

Cheers.

Dug this error message out from the event log:

Navn på program med fejl: fmeworkbench.exe, version: 2019.7.36.19238, tidsstempel: 0x5c9d7fb3

Looks like my machine has a problem with Qt5Core_fme.dll. Are there some special requirements for this ?

I've looked into the Windows Update angle, and it seems that what worked nicely before March 10 now fails. I can see that multiple updates of Windows 10 version 1803 has been installed since then. What versions of Windows 10 has FME 2019.0 been tested against ?

What is your Windows 10 version, if I may ask? I'm currently looking into whether it's the 1803 update that's messing up my computer.

What is your Windows 10 version, if I may ask? I'm currently looking into whether it's the 1803 update that's messing up my computer.

Hi @lifalin2016,

I have the same problem as @lifalin2016, same behaviour and error message on in the event viewer - though I'm using the FME workbench bundled with ArcGIS the Data Interoperability extension.

Faulting application name: fmeworkbench.exe, version: 2018.7.35.18568, time stamp: 0x5be5204f
Faulting module name: Qt5Core_fme.dll, version: 5.9.2.0, time stamp: 0x59da53d2
Exception code: 0xc0000005
Fault offset: 0x0006cce8
Faulting process id: 0x2a44
Faulting application start time: 0x01d50739f98ca8e9
Faulting application path: C:\Program Files (x86)\Esri\Data Interoperability (x86)\fmeworkbench.exe
Faulting module path: C:\Program Files (x86)\Esri\Data Interoperability (x86)\Qt5Core_fme.dll

It seems my second computer, which fails to run FME 2019, is a slightly newer build compared to my office computer, that runs FME 2019 just fine. Both run Win 10 version 1803, but builds 17134.706 and 17134.285 resp.

And I tried to install the 32 bit version, but it also fails, mentioning "fmeprompter.dll" instead of "Qt5Core_fme.dll" as in the 64 bit version.

I suddenly also had problems with Adobe Illustrator and Garmin Express. Reinstalling Express solved that, and using the 32 bit version of AI instead of the 64 bit worked (save to web). In the event of Express, that error suggested something related to Qt as well.

The way I'm testing it, is starting Workbench, open a new workspace, and try to add a Tester. This crashes FME the same way every time. I just tried to add a TestFilter instead, and now it crashes with a reference to qt_workbench.dll". I do have QGIS 3.4.6 x64 installed as well on the machine, which uses Qt5 extensively, and it doesn't crash.

Hi @lifalin2016, are you able to install and try the latest FME 2019.1 beta? Do you still have the same behaviour?

I have the same problem with FME desktop 2019 installation. Only I can't even get the workbench application to start without giving an error. I uninstalled 2017 version and installed 2019. Other installs of 2019 worked on my personal computer.

FME Workbench has stopped working

Problem event: APPCRASH

Fault module: qt5network_fme.dll

Windows server 2012 R2 64 bit

Hi @sondickerson,

Sorry to hear that you're encountering this issue. We have had another user report this to us (same faulting module: qt5network_fme.dll) and we were able to find the issue and resolve it, it is related to the underlying framework FME uses for the GUI (Qt).

Are you able to install and try the latest FME 2019.1 beta? You can install this into a separate directory to test it out. If that works, we have also put the fix into the next FME 2019.0.x which should also resolve this issue.

Please let me know if FME 2019.1 beta has the same behaviour or not.

- Andrea

I had an online chat session with Debbi and she mentioned the same thing. Yes, the beta version (b19570) did work. So that should keep us til the official version gets released. Thanks very much.