Well, it's most likely very easy to reproduce. Just enter an invalid server name for an existing service. That's what failed in my case, they retired a very long-running server name.
Sorry that you have encountered this issue.
For these problems have you been in contact with our support team or with your Safe Partner?
If you have not, would you be able to submit a problem report to us on the support team?
Please include information about the background map definition as well as send us the FMEReport.html after running the bat file attached to this article, so that we can understand your system environment.
We would like to reproduce the issue so that we can resolve it.
Thank you!
Andrea
Ah. It seems my background map definition (which erred) caused the crash.
It would be nice if FME didn't crash whenever some underlying detail like background maps erred.
And as an added investigation, I downloaded the 2020 beta (x64), created a new workspace with one Creator with one Inspector connected, and ran it. It crashed FME !
Well, now I have a working workspace, that crashes FME when trying to open the inspector application after it's run is done. And this is on my company laptop, that hasn't given me issues before.
The workspace simply runs thru all FMW files, extracting the FME version from the embedded command line. You can easily run it with a different path to some workspace files.
It errs on 2019.1.1.0 build 19617.
Please advise.
Glad to hear that the upgrade to FME 2019.1 is working for you with new workspaces.
We would like to see if we can reproduce the behaviour with the old workspace. Perhaps there is something inside of the workspace that is causing the crash. Are you able to share the workspace? If you cannot share it on the forums, please submit it via our report a problem form.
- Andrea
好吧，现在似乎有些东西在工作了：-）
我升级了我的家用电脑以赢得10 Pro，并安装了2019.1。现在FME没有'；当我创建一个新工作区并添加一个Tester（或TestFilter）transformer时，它不会崩溃。
当我试图打开导致2019.0崩溃的原始旧工作区时，它仍然会崩溃，所以所有'；情况仍然不太好，我很快会调查的。
干杯。
Great to hear!
- Andrea
我和黛比在线聊天，她也提到了同样的事情。是的，测试版（b19570）确实有效。所以在官方版本发布之前我们应该一直这样。非常感谢。
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 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
我'；我正在测试它，正在启动Workbench，打开一个新的工作区，并尝试添加一个测试人员。每次都是这样。我只是试着添加一个TestFilter，但是现在它由于引用qt\u workbench.dll而崩溃了；。我有QGIS 3.4.6 x64安装在机器上，它广泛使用Qt5，它没有'；t碰撞。
我突然也遇到了Adobe Illustrator和Garmin Express的问题。重新安装Express解决了这个问题，使用32位版本的AI而不是64位版本可以工作（保存到web）。在Express事件中，这个错误也暗示了一些与Qt相关的东西
至于FME崩溃，Windows生成了几个AppCrash文件，所以我'；我在这里附加这些（一个用于32位，一个用于64位）。
fme\u 2019\u appcrasks\u 20190512.zip
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.
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.
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.
In this case it's FME version 2018.7.35 Build 18568. Windows 10 x64 build 1803.
Have reported through ESRI support (as they manage support issues with the extension) but thought I'd add mention that I'm seeing the same behaviour here.
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
嗨@lifalin2016，
我也看到另一个用户在Windows 10 1803上遇到崩溃。但我可以'；我不敢肯定那是不是'；巧合的是，你们都在1803年；我现在用的是windows10pro1809。我无法再现您或其他用户报告的崩溃。
如果可能，我'；我建议你试试Windows更新，看看能不能解决这个问题
请问您的Windows 10版本是什么？我'；我正在调查；这是1803年的更新'；我的电脑坏了。
请问您的Windows 10版本是什么？我'；我正在调查；这是1803年的更新'；我的电脑坏了。
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 ?
从事件日志中找出此错误消息：
Navn på；程序med fejl:fmeworkbench.exe，版本：2019.7.36.19238，tidstempel:0x5c9d7fb3
Navn på；modul med fejl:Qt5Core\u fme.dll，版本：5.11.2.0，tidstempel:0x5bac0970
Undtagelseskode:0xc000005
对于skydning med fejl 0x00000000001e38b8
过程id 0xef0
程序启动程序0x01d4f9dd70b99208
程序id:C:\Program Files\FME 2019\fmeworkbench.exe
模块id:C:\Program Files\FME 2019\Qt5Core\u FME.dll
报告id:56253910-c0b1-4798-b643-3c1f31935626
Fuldt navn på；program med fejl:
program med fejl的相对程序id:
--
看起来我的机器有Qt5Core\u fme.dll问题。对此有什么特殊要求吗？
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.
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.
I tried to replace build 19238 with 19236 (RC), but it changed nothing :-(
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.
Is there a way to generate some low level crash info feedback to Safe ?
我无法在PC上重现build 19238（Win64）的问题。
请尝试重新安装FME。如果没有'；不工作，你'；您可能需要联系安全支持部门。
It kinda defeats the purpose to install on a different computer, doesn't it ? ;-)
Can't reproduce that here, first thing I would try is re-installing and/or trying it on a different computer.