Hi.
I just installed 2019.0 (build 19238), and tried to open an old workspace, which made it crash FME.
After some work, I narrowed it down to a replicable error, where I open a blank workspace, and just try to add the Tester transformer. This alone makes FME crash.
I tested whether my setting FME to use Python 2.7 was a factor, but it also fails with Python 3.7.
Please advise.
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.
Great to hear!
- Andrea
Well, something seems to be working now 
I upgraded my home computer to Win 10 Pro, and installed 2019.1. And now FME doesn't crash when I create a new workspace and add a Tester (or TestFilter) transformer.
It still crashes when I try to open the original old workspace that crashed 2019.0 however, so all's still not well, and I will look into that soon.
Cheers.
Well, something seems to be working now
I upgraded my home computer to Win 10 Pro, and installed 2019.1. And now FME doesn't crash when I create a new workspace and add a Tester (or TestFilter) transformer.
It still crashes when I try to open the original old workspace that crashed 2019.0 however, so all's still not well, and I will look into that soon.
Cheers.
Hi @lifalin2016,
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
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.
TEST 2019.fmw
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.
TEST 2019.fmw
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.
TEST 2019.fmw
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.
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.
Hi @lifalin2016,
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
Hi @lifalin2016,
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
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.