I have Streamline 360 and used to be able to Translation/export to word for translation purpose. However I could not do it anymore this morning, instead I received this error message: "Exception has been thrown by the target of an innovation." See attached. Anyone idea what has happened?
I'm sorry you're running into this error! Our team has taken note of it and can recreate experiencing the Exception has been thrown by the target of an invocation when exporting a text-heavy Storyline 360 file to Word.
Current workarounds:
Split the project into multiple parts by doing a Save As on the original .story file to reduce the number of slides
Export and translate the translation documents and then import them into the original .story file
Or, closing all Office applications can help
So sorry for the trouble, and I'll keep this discussion updated on any more changes!
However I don’t think it is the file size that triggered the error message. I tested the same function on a SL file with only one slide, here is what I got, another different message: Have you heard the same complaining from others about this issue?
The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain confidential, trade secret and/or privileged material. If you are not the intended recipient(s) of this message, or the employee or agent responsible for delivery of this message to the intended recipient(s), do not review, retransmit, disclose, disseminate, use, or take any action in reliance upon, this information. If you received this transmission in error, please contact the sender and destroy all printed copies and delete the material from all computers. In connection with our business, Ortho Clinical Diagnostics may collect and process your personal data. For further information regarding how we use this data, please see our online privacy notice at https://www.orthoclinicaldiagnostics.com/en-us/home/privacy-policy
The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain confidential, trade secret and/or privileged material. If you are not the intended recipient(s) of this message, or the employee or agent responsible for delivery of this message to the intended recipient(s), do not review, retransmit, disclose, disseminate, use, or take any action in reliance upon, this information. If you received this transmission in error, please contact the sender and destroy all printed copies and delete the material from all computers. In connection with our business, Ortho Clinical Diagnostics may collect and process your personal data. For further information regarding how we use this data, please see our online privacy notice at https://www.orthoclinicaldiagnostics.com/en-us/home/privacy-policy
Thanks for reaching out, and thanks for getting a case started. I see my teammate, Gerald, has replied back with confirmation of the bug you're running into. I'm sorry you're hitting this roadblock as well!
Take a look at the workarounds I mentioned above and see if they help at all!
Thanks for your reply. I did try the workarounds above but no dice. I think the mammoth file is the problem. Had to divide it into mini-scenes and export in bits, then put back together in Word. Good times!
when will this be properly fixed? or is this another case of Articulate passing the time and cost back on to it's users as usual. I have spent hours on this today and yesterday.
I have split my project in to 3 separate pieces and outputted 3 separate translation docs. Obviously some of the items repeat - from the master slides.
Do I need to try to combine them now into 1 word document?
How do I do this? - will it cause issues with stuff being imported back into the original file?
Or do I keep the 3 docs separate and load them back into the original file one at a time?
Obviously with removing scenes when separating the project - they all ended up being scene 1, 2, 3 in the original they are numbered differently - will this cause an issue with reimporting the translation - the work around does not explain how to get the translation back into the course.
Thanks for reaching out and sharing your questions and concerns surrounding this issue with Word translation. I'd be happy to walk through each of your questions:
When will this be properly fixed?
We're careful about testing new updates to make sure we don't put other features at risk, and I don't want to commit to a date before we have a fix finalized. This conversation is linked to our report so that we can share updates with you here when they are available.
Do I need to try to combine them now into a 1-word document?
No. You want to keep the individual translation files.
Do I keep the 3 docs separate and load them back into the original file one at a time?
Yes. You want to import the 3 translation documents back into your original .story file. Since you're using your original .story file, this should eliminate any concerns with the order of your project.
In addition, there is a specific setting that can also affect publish to Word and export translations to Word.
This setting is called "Beta: Use Unicode UTF-8 for worldwide language support"
You can access this setting using these steps:
In Windows, open Settings
Click Time & Language
Click Language
On the right side under "Related Settings" click Administrative Language Settings
Under the Administrative Tab click "Change System Locale" (requires admin rights)
Ensure that the box labeled "Beta: Use Unicode UTF-8 for worldwide language support" is unchecked
I have checked the "Beta: Use Unicode UTF-8 for worldwide language support" setting and it was already unchecked so no change there - but thank you for the rest of the help
I wonder if part of the problem is that it is trying to use/connect to microsoft one drive? every time I try to output the translation doc, about half way through, a micorsoft one drive window opens asking me to set it up - I do not use this feature.
Thank you for these extra details! This could be causing the issue. In the OneDrive settings, you should be able to Disable this PC, making sure the window doesn't appear.
We're on it, and assuming the final testing phase goes well, a fix for this will be released in the next update. We'll let you know as soon as that's ready!
This feature fixes the issue where the error, 'Exception has been thrown by the target of an invocation' appeared when exporting a text-heavy Storyline 360 file to Word.
To take advantage of this new feature and other fixes, make sure to update Storyline 360 in the Articulate 360 Desktop App. Here are the steps!
15 Replies
Hi Tong,
I'm sorry you're running into this error! Our team has taken note of it and can recreate experiencing the Exception has been thrown by the target of an invocation when exporting a text-heavy Storyline 360 file to Word.
Current workarounds:
So sorry for the trouble, and I'll keep this discussion updated on any more changes!
Thanks for getting back to me!
However I don’t think it is the file size that triggered the error message. I tested the same function on a SL file with only one slide, here is what I got, another different message: Have you heard the same complaining from others about this issue?
Thank you!
[cid:image002.jpg@01D6756C.B2A6C540]
Tong Wang
Sr. Technical Writer
Training Development & Performance Support
Ortho Clinical Diagnostics
100 Indigo Creek Drive
Rochester, NY 14626 USA
Cell: 585-469-4798
tong.wang@orthoclinicaldiagnostics.com
www.orthoclinicaldiagnostics.com
The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain confidential, trade secret and/or privileged material. If you are not the intended recipient(s) of this message, or the employee or agent responsible for delivery of this message to the intended recipient(s), do not review, retransmit, disclose, disseminate, use, or take any action in reliance upon, this information. If you received this transmission in error, please contact the sender and destroy all printed copies and delete the material from all computers. In connection with our business, Ortho Clinical Diagnostics may collect and process your personal data. For further information regarding how we use this data, please see our online privacy notice at https://www.orthoclinicaldiagnostics.com/en-us/home/privacy-policy
Hi,
Maybe you can diagnose it easier if I send you the file that caused the error message? It is not large in size. Please see attached.
Thank you!
Tong Wang
Sr. Technical Writer
Training Development & Performance Support
Ortho Clinical Diagnostics
100 Indigo Creek Drive
Rochester, NY 14626 USA
Cell: 585-469-4798
tong.wang@orthoclinicaldiagnostics.com
www.orthoclinicaldiagnostics.com
The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain confidential, trade secret and/or privileged material. If you are not the intended recipient(s) of this message, or the employee or agent responsible for delivery of this message to the intended recipient(s), do not review, retransmit, disclose, disseminate, use, or take any action in reliance upon, this information. If you received this transmission in error, please contact the sender and destroy all printed copies and delete the material from all computers. In connection with our business, Ortho Clinical Diagnostics may collect and process your personal data. For further information regarding how we use this data, please see our online privacy notice at https://www.orthoclinicaldiagnostics.com/en-us/home/privacy-policy
Hi Tong!
It doesn't look like we've received your attachment. Would you mind sending it privately? We'll let you know when we receive it!
Hi, I am having the same issue with trying to export to Word - seeing the same error message as you did.
Did you ever resolve this? I would appreciate any advice!
Hi Francie,
Thanks for reaching out, and thanks for getting a case started. I see my teammate, Gerald, has replied back with confirmation of the bug you're running into. I'm sorry you're hitting this roadblock as well!
Take a look at the workarounds I mentioned above and see if they help at all!
Hi Ren,
Thanks for your reply. I did try the workarounds above but no dice. I think the mammoth file is the problem. Had to divide it into mini-scenes and export in bits, then put back together in Word. Good times!
Francie
when will this be properly fixed? or is this another case of Articulate passing the time and cost back on to it's users as usual. I have spent hours on this today and yesterday.
I have split my project in to 3 separate pieces and outputted 3 separate translation docs. Obviously some of the items repeat - from the master slides.
Do I need to try to combine them now into 1 word document?
How do I do this? - will it cause issues with stuff being imported back into the original file?
Or do I keep the 3 docs separate and load them back into the original file one at a time?
Obviously with removing scenes when separating the project - they all ended up being scene 1, 2, 3 in the original they are numbered differently - will this cause an issue with reimporting the translation - the work around does not explain how to get the translation back into the course.
Hi Lizzie,
Thanks for reaching out and sharing your questions and concerns surrounding this issue with Word translation. I'd be happy to walk through each of your questions:
When will this be properly fixed?
We're careful about testing new updates to make sure we don't put other features at risk, and I don't want to commit to a date before we have a fix finalized. This conversation is linked to our report so that we can share updates with you here when they are available.
Do I need to try to combine them now into a 1-word document?
No. You want to keep the individual translation files.
Do I keep the 3 docs separate and load them back into the original file one at a time?
Yes. You want to import the 3 translation documents back into your original .story file. Since you're using your original .story file, this should eliminate any concerns with the order of your project.
In addition, there is a specific setting that can also affect publish to Word and export translations to Word.
This setting is called "Beta: Use Unicode UTF-8 for worldwide language support"
You can access this setting using these steps:
See this peek for more info:
Disabling Unicode UTF-8 for worldwide language support
I have checked the "Beta: Use Unicode UTF-8 for worldwide language support" setting and it was already unchecked so no change there - but thank you for the rest of the help
I wonder if part of the problem is that it is trying to use/connect to microsoft one drive? every time I try to output the translation doc, about half way through, a micorsoft one drive window opens asking me to set it up - I do not use this feature.
Hi Lizzie!
Thank you for these extra details! This could be causing the issue. In the OneDrive settings, you should be able to Disable this PC, making sure the window doesn't appear.
If that doesn't do the trick, I'd recommend connecting with a Support Engineer for additional 1:1 troubleshooting.
When will this be fixed please!!!!!
Hi there, Jessica!
I'm so sorry this bug is impacting your work.
We're on it, and assuming the final testing phase goes well, a fix for this will be released in the next update. We'll let you know as soon as that's ready!
Hi all!
I'm so excited to share that we've released Storyline 360 (Build 3.49.24347.0) which includes Enhanced Word Translation!
This feature fixes the issue where the error, 'Exception has been thrown by the target of an invocation' appeared when exporting a text-heavy Storyline 360 file to Word.
To take advantage of this new feature and other fixes, make sure to update Storyline 360 in the Articulate 360 Desktop App. Here are the steps!