I keep getting the attached error message when I attempt to export a translation file from a module I created in SL3. I save the file to the local "c" drive every time.
I think I have solved the problem. In Windows 10, I assigned Word 2016 as a default app for opening documents. Seems to works OK now. Never occurred to me that this needed to be done, but I am using Parallels desktop on my Mac. Also, I opted to have Word 2016 running (open) while the translation occurred. Not A PC guy, so that may have been the problem.
This seems to be the most up-to-date thread on this topic. I'm getting this same empty error message when trying to export for translation. The only difference is that I am using Storyline 2. Has anyone found a work-around? I'm on Windows 10, recently uninstalled and reinstalled SL2, working from my local drive, with Word closed. No go. Any help is greatly appreciated.
And have no fear here! After deleting and then recreating those objects, we were able to create an exported translation file ready for download in your case. Let us know what you think!
8 Replies
Hey there Mark. How's Word running for you these days? Is it running when you try to generate the export .doc?
Does doing a simple reboot help?
And lastly, has the translation export worked for you previously?
Thanks for the extra details!
Hey Crystal,
Word is running fine. I generally do not have it running while I generate the export.
Reboot, as well as, uninstall & re-install does not change things.
I have never attempted to export before.
Hi Mark!
Would you be able to share your .story file so that we could take a look?
...or I could open another thread and see that you're probably good to go :)
I think I have solved the problem. In Windows 10, I assigned Word 2016 as a default app for opening documents. Seems to works OK now. Never occurred to me that this needed to be done, but I am using Parallels desktop on my Mac. Also, I opted to have Word 2016 running (open) while the translation occurred. Not A PC guy, so that may have been the problem.
Thanks for coming back around to give us an update, Mark!
Hi...
This seems to be the most up-to-date thread on this topic. I'm getting this same empty error message when trying to export for translation. The only difference is that I am using Storyline 2. Has anyone found a work-around? I'm on Windows 10, recently uninstalled and reinstalled SL2, working from my local drive, with Word closed. No go. Any help is greatly appreciated.
Thanks,
Scott
Really sorry about that error message, Scott.
Smart move to also open a case with our Support Engineers! I saw that my teammate, Jose, isolated the issue to corrupted objects. While it's hard to nail down the root of corruption, these pro-tips can help mitigate the risk!
And have no fear here! After deleting and then recreating those objects, we were able to create an exported translation file ready for download in your case. Let us know what you think!
This discussion is closed. You can start a new discussion or contact Articulate Support.