Skip to main content
  • EN

Hi list.

I have a workspace, that fails when running. It fails in an Emailer, that I just added last week. The relevant excerpt from the log file is shown here:

2020-11-30 17:38:49|   5.6|  0.0|STATS |Emailer_CATCHER (TeeFactory): Cloned 0 input feature(s) into 0 output feature(s)
2020-11-30 17:38:50|   6.0|  0.4|ERROR |Python Exception <ModuleNotFoundError>: No module named 'fmepy_emailer'
2020-11-30 17:38:50|   6.0|  0.0|FATAL |PythonFactory failed to load python symbol `fmepy_emailer.Emailer'
2020-11-30 17:38:50|   6.0|  0.0|FATAL |Emailer_CALLER (PythonFactory): PythonFactory failed to close properly
2020-11-30 17:38:50|   6.0|  0.0|ERROR |Emailer_CALLER (PythonFactory): A fatal error has occurred. Check the logfile above for details
2020-11-30 17:38:50|   6.0|  0.0|ERROR |Emailer_CALLER (PythonFactory): A fatal error has occurred. Check the logfile above for details

The Python scripting is set to 3.7+, and the Emailer is completely standard, added in the current version.

What's wrong, and is there a remedy or work-around ?

Cheers.

 

Hi @Lars I Nielsen​,

When you go to Tools > FME Options > FME Packages, can you confirm that you see Emailer in the list? I noticed that these errors can occur when the package is removed without removing the transformer from the workspace.

 

Adding a new Emailer should download it from the Hub or you can re-download it from the FME Hub directly. It might be worthwhile to check out the comments as well on the Hub page as there's been some discussion on this error with regards to using the Emailer with Server or Task Scheduling software.

 

Emailer-package

Hi @Lars I Nielsen​,

When you go to Tools > FME Options > FME Packages, can you confirm that you see Emailer in the list? I noticed that these errors can occur when the package is removed without removing the transformer from the workspace.

 

Adding a new Emailer should download it from the Hub or you can re-download it from the FME Hub directly. It might be worthwhile to check out the comments as well on the Hub page as there's been some discussion on this error with regards to using the Emailer with Server or Task Scheduling software.

 

Emailer-package

Hi Jovita.

FME Packages, eh? Ok, a new thing to learn about.

It's present, but says (Update Available), so I'll update it, and see if it fixes the issue.

After the update the version is 2.1.3

Hi Jovita.

FME Packages, eh? Ok, a new thing to learn about.

It's present, but says (Update Available), so I'll update it, and see if it fixes the issue.

After the update the version is 2.1.3

Well, the 32 bit version didn't show any emailer. I then opened a new workspace, added the Emailer, and now it is present under packages.

Do both bit versions share their packages ? I guess not.

Hi @Lars I Nielsen​,

When you go to Tools > FME Options > FME Packages, can you confirm that you see Emailer in the list? I noticed that these errors can occur when the package is removed without removing the transformer from the workspace.

 

Adding a new Emailer should download it from the Hub or you can re-download it from the FME Hub directly. It might be worthwhile to check out the comments as well on the Hub page as there's been some discussion on this error with regards to using the Emailer with Server or Task Scheduling software.

 

Emailer-package

The issues I ran into is, that FME Desktop installations don't share packages.

Why not implement FME Packages like NuGet package, i.e. references, that gets the package downloaded whenever a workspace is opened in Workbench, or run by the the fme.exe engine ?

Now, every single installation needs to maintain its own set of package, or face the cryptic error message that I encountered.

Especially when the old emailer transformer, that always worked, has been retired.

The issues I ran into is, that FME Desktop installations don't share packages.

Why not implement FME Packages like NuGet package, i.e. references, that gets the package downloaded whenever a workspace is opened in Workbench, or run by the the fme.exe engine ?

Now, every single installation needs to maintain its own set of package, or face the cryptic error message that I encountered.

Especially when the old emailer transformer, that always worked, has been retired.

@Lars I Nielsen​, glad to hear you got the Emailer working again! I believe there are some restrictions at the moment that tie the packages to the build of FME if I read into it correctly.

 

In the meantime, there's an Idea on the Option for shared package paths that you can upvote and add your suggestions to the discussion, or feel free to post a new idea as well to help inform our product team.

Reply


Community Stats

30,418
Posts
115,549
Replies
38,226
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.