Hello,
please help me! During translation I can read error message "ERROR |MULTI_WRITER: No MULTI_WRITER_TYPE{*} or MULTI_WRITER_TYPE{NULL} was specified" -> whats wrong please?
Page 1 / 1
According to the information you have provided, which is minimal...it seems like you don't have a writer specified in the workspace.
You could try and start with a new empty workspace and copy the older workspace objects into it.
According to the information you have provided, which is minimal...it seems like you don't have a writer specified in the workspace.
You could try and start with a new empty workspace and copy the older workspace objects into it.
2016-09-04 19:48:52| 11.0| 0.0|INFORM|MULTI_WRITER: multi_writer_id `NULL': Started outputting features
2016-09-04 19:48:52| 11.3| 0.3|ERROR |MULTI_WRITER: No MULTI_WRITER_TYPE{*} or MULTI_WRITER_TYPE{NULL} was specified
2016-09-04 19:48:52| 11.3| 0.0|STATS |Stored 1 feature(s) to FME feature store file `D:\\projekty_CS\\BVS\\moje_data\\FME_zavazne\\doplneni_atributu_pred_importem_kanal_3_log.ffs'
2016-09-04 19:48:52| 11.3| 0.0|INFORM|FME Session Duration: 11.6 seconds. (CPU: 9.7s user, 1.2s system)
2016-09-04 19:48:52| 11.3| 0.0|INFORM|END - ProcessID: 8264, peak process memory usage: 300924 kB, current process memory usage: 89836 kB
MULTI_WRITER: No MULTI_WRITER_TYPE{*} or MULTI_WRITER_TYPE{NULL} was specified
Program Terminating
Translation FAILED.
I cant understand why, but workspace stopped to work after some small changes
Unfortunately I have specified several writers in workspace :-/
in that case I think you better send a support request to Safe.
Yes, we'll definitely need the workspace. Do send it in to support@safe.com -- along with the the complete log of your run as well.
Which writer you have used?
Which writer you have used?
I have this same issue now on 2023..1 619.
The workspace has previously worked for 3 yrs. I added a new custom transformer and it started this behavior.
The custom transformer is a required change.
I have an xlsx writer and a mssql non spatial writer in the workspace.
Has this issue been resolved?
Hey
Was the workspace originally created in an earlier version of workbench and now opened in a newer version? If so, please try upgrading the writers to see if that resolves the issue.
If that’s not the case, which one was the new custom transformer that you added and is it linked or embedded? There was an issue in FME 2023.1 where custom transformers were failing to write in linked mode, which has been resolved in build 23639+. The fix requires you to open the custom transformer(.fmx) file, and re-save it with the new version.
If neither of these applies, you may want to consider submitting a support ticket with the workspace and log file attached.
Hope that helps!
Emma
I am stuck on flow ver 2023.1 build 619 so I am not willing to install anything else until I upgrade to 2024 which I don’t want to do until someone at safe and ESRI give me direction on how much vm it will require to run both servers on one vm and maintain performance for both
I have put this request on every support ticket I have created
the workbench could have been built in an earlier version but I completely rebuilt it in 2023.1 the other day the custom transformer is embedded and I have saved it in 2023.1
i do have a support ticket
Hi
We couldn’t find a support ticket associated with the custom transformer issue you mentioned.
We’d like to further investigate and figure out what’s going on here with your workspace. If you could provide the following, that would be a great start:
- Your workspace
- Your logfile
- The name of the transformer that caused the issue
Alternatively, If you’d prefer to create a support ticket with this information, our team would be happy to assist you!
Emma