+6I have a decelorator in my routine but it is failing with the message below. It looks like it is failing within the transformer.
@Tcl2 -- failed to evaluate expression `if { {Limit Features Per Second} == {Per Feature Delay} } { rename Decelerator_delay Decelerator_Waiter; } else { rename Decelerator_maxpersecond Decelerator_Waiter; };' -- can't rename to "Decelerator_Waiter": command already exists
Any ideas how I can get it going?
Thanks
+50I can't seem to reproduce that error message, but I agree with @david_r, if you can post your Decelerator settings here that would allow us to get a better idea of what going on.
The Decelerator requires a number for the delay and number of features per second parameters, maybe that's happening here? It can be derived from an attribute but it has to be a number.
+6I can't seem to reproduce that error message, but I agree with @david_r, if you can post your Decelerator settings here that would allow us to get a better idea of what going on.
The Decelerator requires a number for the delay and number of features per second parameters, maybe that's happening here? It can be derived from an attribute but it has to be a number.
Thanks for posting the screenshot, the settings look perfectly normal to me.
Can you try deleting the transformer from your workspace and then inserting it again?
+18Have you used an attribute for the Maximum Features per Second setting?
If so, Is that attribute in all cases a valid integer.
If not, that could cause this issue.
I would recommend an AttributeVallidator transformer to check if the value is of type Integer before handing the attribute to the Decelerator.
+6Thanks for posting the screenshot, the settings look perfectly normal to me.
Can you try deleting the transformer from your workspace and then inserting it again?
+6Have you used an attribute for the Maximum Features per Second setting?
If so, Is that attribute in all cases a valid integer.
If not, that could cause this issue.
I would recommend an AttributeVallidator transformer to check if the value is of type Integer before handing the attribute to the Decelerator.
+18Have you used an attribute for the Maximum Features per Second setting?
If so, Is that attribute in all cases a valid integer.
If not, that could cause this issue.
I would recommend an AttributeVallidator transformer to check if the value is of type Integer before handing the attribute to the Decelerator.
What version of FME are you using?
+6What version of FME are you using?
+18Hi @sebkingsley -- sorry to see that you have somehow stumbled into a situation that would seem to be impossible. So we have a bug on our hands. The "good" news is that it has stayed that way for you. Could you send your workspace in to support@safe.com and reference this posting in your note?
The error is due to somehow there already being a "Decelerator_Waiter" function in place in FME's internal Tcl subsystem. I check how this is written and do not see how it is possible for this to happen. So that is why your original workspace is so important for us to be able to look it.
So please send it.
And after you do...a most probable workaround would be to rename the Decelerator transformer to have a different name. Then it will be trying to rename the function to YourName_Waiter instead. And I suspect it would work then. But please send us the broken workspace first! Thanks and sorry.
+6Hi @sebkingsley -- sorry to see that you have somehow stumbled into a situation that would seem to be impossible. So we have a bug on our hands. The "good" news is that it has stayed that way for you. Could you send your workspace in to support@safe.com and reference this posting in your note?
The error is due to somehow there already being a "Decelerator_Waiter" function in place in FME's internal Tcl subsystem. I check how this is written and do not see how it is possible for this to happen. So that is why your original workspace is so important for us to be able to look it.
So please send it.
And after you do...a most probable workaround would be to rename the Decelerator transformer to have a different name. Then it will be trying to rename the function to YourName_Waiter instead. And I suspect it would work then. But please send us the broken workspace first! Thanks and sorry.
I have a support ticket opened under C136804.
It was raised through the online chat yesterday.
I submitted the workspace through that.
If you still need it via the email address as well please let me know.
I will try the work around as well.
Thanks
Seb
+6Hi @sebkingsley -- sorry to see that you have somehow stumbled into a situation that would seem to be impossible. So we have a bug on our hands. The "good" news is that it has stayed that way for you. Could you send your workspace in to support@safe.com and reference this posting in your note?
The error is due to somehow there already being a "Decelerator_Waiter" function in place in FME's internal Tcl subsystem. I check how this is written and do not see how it is possible for this to happen. So that is why your original workspace is so important for us to be able to look it.
So please send it.
And after you do...a most probable workaround would be to rename the Decelerator transformer to have a different name. Then it will be trying to rename the function to YourName_Waiter instead. And I suspect it would work then. But please send us the broken workspace first! Thanks and sorry.
Further update.
I tried the workaround and get the same type of message.
2018-05-18 08:53:59| 1.4| 0.0|ERROR |@Tcl2 -- failed to evaluate expression `if { {Per Feature Delay} == {Per Feature Delay} } { rename Staller_delay Staller_Waiter; } else { rename Staller_maxpersecond Staller_Waiter; };' -- can't rename to "Staller_Waiter": command already exists
+6Hi @sebkingsley -- sorry to see that you have somehow stumbled into a situation that would seem to be impossible. So we have a bug on our hands. The "good" news is that it has stayed that way for you. Could you send your workspace in to support@safe.com and reference this posting in your note?
The error is due to somehow there already being a "Decelerator_Waiter" function in place in FME's internal Tcl subsystem. I check how this is written and do not see how it is possible for this to happen. So that is why your original workspace is so important for us to be able to look it.
So please send it.
And after you do...a most probable workaround would be to rename the Decelerator transformer to have a different name. Then it will be trying to rename the function to YourName_Waiter instead. And I suspect it would work then. But please send us the broken workspace first! Thanks and sorry.
I have found that everything works, including the decellorator up to the point I drop the excel writer on the canvas. Then the decelorator fails.
I hope that helps with the diagnosis.
+1Hi, I'm having the same issue with FME(R) 2018.0.0.2 (20180414 - Build 18301 - WIN64). As a workaround I used a SystemCaller with the command: timeout /t 10 (for a 10 second decelerator). For FME Server running on *nix, use the command: sleep 10 (for 10 seconds as default).
+6Hi, I'm having the same issue with FME(R) 2018.0.0.2 (20180414 - Build 18301 - WIN64). As a workaround I used a SystemCaller with the command: timeout /t 10 (for a 10 second decelerator). For FME Server running on *nix, use the command: sleep 10 (for 10 seconds as default).
It was a conflict with the Excel writer on my workspace. Once I deleted the excel writer it worked fine.
Safe have apparently fixed it now though.
+18It was a conflict with the Excel writer on my workspace. Once I deleted the excel writer it worked fine.
Safe have apparently fixed it now though.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
