Skip to main content
  • EN

Hi,

When I try to open a workflow file that has a PostGIS reader or writer FME Workbench crashes immediately, without any dialogs or crash logs. This happens whether I open the file by double clicking, right click "Open with...", drag and drop the file or "File > Open".

Similarly, if I try to open a PostGIS table in the data inspector it crashes too.

I can open the database and its tables in PGAdmin so I know the database is up and running.

I've just updated to the official release of FME Desktop 2018 on Windows 10 (I've previously been using the beta versions without issues).

Thanks,

Aiden

Hi @aprice,

There is a similar question here https://knowledge.safe.com/questions/64781/fme-2018-rc1-crashes-when-opening-workspace.html

@MitaAtSafe did write a interesting document about the Error - Crash in FME Workbench:

https://knowledge.safe.com/articles/894/troubleshooting-an-fmeexe-crash.html

Thanks,

Danilo

Hi @aprice,

There is a similar question here https://knowledge.safe.com/questions/64781/fme-2018-rc1-crashes-when-opening-workspace.html

@MitaAtSafe did write a interesting document about the Error - Crash in FME Workbench:

https://knowledge.safe.com/articles/894/troubleshooting-an-fmeexe-crash.html

Thanks,

Danilo

Hi Danilo,

 

 

I read both of those before raising this and neither is any help in this case unfortunately.

 

 

The first one references removing the FME 2018 Beta, I've tried downgrading to 2017.1.2 and that didn't fix the problem.

 

 

The second asks you to check whether the issue arises from the readers or writers by opening the dataset in Data Inspector, which I did and the inspector subsequently crashed. This page goes on to tell you to inspect the logs but there are no logs written because the crash occurs before translation.

 

 

Thanks,

 

Aiden.

 

 

Sad to hear about this. I can advise that we have a working theory as to what is going on and will have to involve you in the hunt. (I think support is already in touch). In short, we suspect something us up with the Python installation on your computer or the way we are interacting with it...but we'll work to confirm that.

Sad to hear about this. I can advise that we have a working theory as to what is going on and will have to involve you in the hunt. (I think support is already in touch). In short, we suspect something us up with the Python installation on your computer or the way we are interacting with it...but we'll work to confirm that.

Hi Dale,

 

I can confirm that you're right, changing back to the default FME Python interpreter fixes the issue. Is it perhaps an ImportError exception because of a missing Python library?

 

 

Thanks,

 

Aiden

 

 

Hi Dale,

 

I can confirm that you're right, changing back to the default FME Python interpreter fixes the issue. Is it perhaps an ImportError exception because of a missing Python library?

 

 

Thanks,

 

Aiden

 

 

Very likely. We'll be in touch next week to dig in deeper.

 

 

Reply


Community Stats

29,719
Posts
112,923
Replies
37,370
Members
Terms & ConditionsCookie settings