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?
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
Was the workspace originally created in an earlier version of workbench and now opened in a newer version? If so, please try upgrading the writersto 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 ticketwith the workspace and log file attached.
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
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!