Skip to main content
Solved

MULTI_WRITER was not specified error: Why do I need it? How do I resolve?

  • December 18, 2023
  • 6 replies
  • 486 views

jspratt
Participant
Forum|alt.badge.img

I'd like to understand what this error means in the following context and how I might go about resolving it.

 

I have a workspace that works perfectly fine if I run using cached features up to transformers just prior to a FeatureMerger then run from the FeatureMerger to a writer. However, when I try to run the entire workspace it results in an error that aborts the translation at the writer. I've also tried many other methods of joining these 2 streams and all are resulting in the same error output. 

MULTI_WRITERNo MULTI_WRITER_TYPE{*} or MULTI_WRITER_TYPE{3} was specified

It seems like I need both streams to be ready at the FeatureMerger at the same time but I have not been able to gain control over execution order or block passthrough features through a variety of attempts. The goal is to read from both a CAD model and a DB, then compare the two datasets on a unique key, then write an SQL statement to a text file or SQLExecutor. I've only attempted this with the text file writer while the SQLExecutor was either disabled or disconnected from the stream. 

 

Here is a snippet of the workspace up to the FeatureMerger:

FMEWorkspaceSnippetAnd the remaining downstream:

FMEWorkspaceSnippet_2

Best answer by nampreetatsafe

Hi @jspratt​! I'm sorry you encountered this issue. This looks like it's related to an issue that was identified recently with linked custom transformers. From your workspace screenshots, it looks like you might be using linked customer transformers. The fix is included in the latest available official release. Once installed, you'll need to open the .fmx file for the custom transformers with the new version of FME and re-save it. Let us know if that does the trick. If not it might be worth submitting a support case and providing your full log file and workspace if possible.

View original
Did this help you find an answer to your question?

6 replies

nampreetatsafe
Safer
Forum|alt.badge.img+12
  • Safer
  • Best Answer
  • December 23, 2023

Hi @jspratt​! I'm sorry you encountered this issue. This looks like it's related to an issue that was identified recently with linked custom transformers. From your workspace screenshots, it looks like you might be using linked customer transformers. The fix is included in the latest available official release. Once installed, you'll need to open the .fmx file for the custom transformers with the new version of FME and re-save it. Let us know if that does the trick. If not it might be worth submitting a support case and providing your full log file and workspace if possible.


gisbradokla
Enthusiast
Forum|alt.badge.img+16
  • Enthusiast
  • February 28, 2024

This did not work for me. I now need to roll back my fme to build 23619 to match my flow build.I am getting warnings about the wb being newer than my server.


jwarren
Contributor
Forum|alt.badge.img+5
  • Contributor
  • December 9, 2024

I’m getting the same error, but do not have any custom transformers 

UPDATE

Even more weirdly, the workspace is running on a Schedule and the error has randomly gone away by itself in the middle of the night…


gisbradokla
Enthusiast
Forum|alt.badge.img+16
  • Enthusiast
  • December 13, 2024

i have an automation that runs every 20 seconds. after running nearly 1200 times on flow i get the failed status on 825 of them. but 385 complete successfully. Why would the same workspace not find a multi writer and then find it? 


jnknnn
Contributor
Forum|alt.badge.img+5
  • Contributor
  • March 21, 2025

I encountered this same bug after updating to 2024.2.3. It happens both in flow and form. As for others, it is also inconsistent for me. I have batch workspace that is launching multiple workspaces, only difference being list of values that is passed as a parameter to SQLExecutor and after some processing these features are sent to featurewriter. Weird thing is that in flow about 90 % of the jobs complete but the rest fails at the same error as op. I also have another batch job with similar logic that fails 100 % of the time in both form and flow.

Feature writer setup:
 

Censored dataset path is fanout like this:
$(tmp_folder)/resultdata/anotherfolder/gpkg/data_@Value(attribute).gpkg

I think it is related somehow to the fanout and/or writing simultaneously to multiple featuretypes inside same featurewriter. @Value(attribute) is used here to control in which geopackage features are grouped. I tried to change batch processing so that there is only one group of @Value(attribute) and it works so somehow the group proessing get messed up. However, this is not feasible because that would generate over 10000  jobs. This setup worked in fmeserver and desktop 2021.


jnknnn
Contributor
Forum|alt.badge.img+5
  • Contributor
  • March 24, 2025

 

nampreetatsafe I did some additional testing and added AttributeKeeper that selects all attrbutes before FeatureWriter and now it works?! This seems like a bug still.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings