I'm trying to export the translation file from a rather big SL3 file. At the very end, I get a blank error message/window and MS Word doesn't open to show me the file. See attached file.
Any similar experience? Any setting I'm missing? In SL3? In Word?
Is there a way to export the translation file out without an error?
My colleague's version is in SL3, update 2: 3.2.13213.0 and it worked fine when trying to export. I'm currently using SL3, update 1: 3.1.12115.0. I have Word 2010.
I managed to get the translation file by "tricking" Word, by forcing Windows to close, prompting Word to display a pop-up about saving the file, cancelling Windows' shut down sequence, saving the file and opening the file to make sure everything was fine.
Please note that the day before, I was able to export translation files. I unfortunately ran into this issue the next morning, probably due to SL3 prompting me that an update was available.
On a sidenote, I feel like it's not a normal behavior that a specific function become "broken" when an update is available. Like I said, everything worked fine until SL3's update went live the next day. Is it something frequent or maybe just a rare occurence of a function becoming "corrupted"? I noticed that from 3.1 and 3.2, the Export Translation function went from simply "Export file" to "Export file in [file format]", now offering 2 text formats.
Thanks for all those details, it looks like you've been through a lot of troubleshooting and I really appreciate you letting us know.
To address your last point question- I wouldn't expect anything to break because you have a pending update. An update won't affect your software until you physically install it.
I'm glad you found a useable workaround, but lets see if we can pinpoint the cause of the issue so you don't have to keep running through that!
Are you seeing the same error happening with any other file, or just that one in particular? If it's just that one file, can you share it here so I can do some testing? You can add it as an attachment right to a comment in the thread.
Are you seeing the same error happening with any other file, or just that one in particular? If it's just that one file, can you share it here so I can do some testing? You can add it as an attachment right to a comment in the thread.
Unfortunately, I cannot share the file due to business reasons. My explanation is the best I can offer at the moment.
To answer your question: As I mentioned, the day before the update, I worked on 2 other SL files which I was able to export the translation. When I got the issue on a 3rd SL file the next day, I did retry to re-export the translation Word files for the 2 previous SL files to see if the problem was due to SL3, Word or the SL file itself; the issue occured as well, as if SL3 itself got glitched by the time it received its "signal" to announce the update. Please also note that I didn't notice anything strange with SL3... and the update hasn't been installed yet. All other functions seem to work as intended.
In short, everything worked as intended the day before, with any file, regardless of size, and it glitched the next day, when the update went live.
Thanks, JC. I haven't had any luck recreating this problem, and I still need your help.
Have you installed the latest update of Storyline 3 yet? If not, I'd recommend doing that first.
After installing the latest update, let us know if you still see an error when you export for translation.
Finally, I understand you not being able to share your file publicly, but you also have the option to send to us privately here. Our team will even sign a NDA, if you'd like.
JC can you tell me please how you "tricked" the system? I'd like to try it. I'm getting an error message on my export translation effort (the rpc server is unavailable (HRESULT: 0x800706BA) ) and I'm hoping your "trick" will help. I've tried everything I know. THANKS
9 Replies
Hi JC,
What update of Storyline and Word are you using? You can check in Storyline by going to the Help tab and clicking on About Articulate Storyline.
If you're on the latest update can you share a copy of the .story file here with us?
Hey JC!
That's definitely odd, let's get to the bottom of it.
I have a few questions to help narrow down the cause:
Let me know and we'll go from there!
My colleague's version is in SL3, update 2: 3.2.13213.0 and it worked fine when trying to export. I'm currently using SL3, update 1: 3.1.12115.0. I have Word 2010.
I managed to get the translation file by "tricking" Word, by forcing Windows to close, prompting Word to display a pop-up about saving the file, cancelling Windows' shut down sequence, saving the file and opening the file to make sure everything was fine.
Please note that the day before, I was able to export translation files. I unfortunately ran into this issue the next morning, probably due to SL3 prompting me that an update was available.
On a sidenote, I feel like it's not a normal behavior that a specific function become "broken" when an update is available. Like I said, everything worked fine until SL3's update went live the next day. Is it something frequent or maybe just a rare occurence of a function becoming "corrupted"? I noticed that from 3.1 and 3.2, the Export Translation function went from simply "Export file" to "Export file in [file format]", now offering 2 text formats.
Hey JC!
Thanks for all those details, it looks like you've been through a lot of troubleshooting and I really appreciate you letting us know.
To address your last point question- I wouldn't expect anything to break because you have a pending update. An update won't affect your software until you physically install it.
I'm glad you found a useable workaround, but lets see if we can pinpoint the cause of the issue so you don't have to keep running through that!
Are you seeing the same error happening with any other file, or just that one in particular? If it's just that one file, can you share it here so I can do some testing? You can add it as an attachment right to a comment in the thread.
Thanks again!
Unfortunately, I cannot share the file due to business reasons. My explanation is the best I can offer at the moment.
To answer your question: As I mentioned, the day before the update, I worked on 2 other SL files which I was able to export the translation. When I got the issue on a 3rd SL file the next day, I did retry to re-export the translation Word files for the 2 previous SL files to see if the problem was due to SL3, Word or the SL file itself; the issue occured as well, as if SL3 itself got glitched by the time it received its "signal" to announce the update. Please also note that I didn't notice anything strange with SL3... and the update hasn't been installed yet. All other functions seem to work as intended.
In short, everything worked as intended the day before, with any file, regardless of size, and it glitched the next day, when the update went live.
Thanks, JC. I haven't had any luck recreating this problem, and I still need your help.
Have you installed the latest update of Storyline 3 yet? If not, I'd recommend doing that first.
After installing the latest update, let us know if you still see an error when you export for translation.
Finally, I understand you not being able to share your file publicly, but you also have the option to send to us privately here. Our team will even sign a NDA, if you'd like.
JC can you tell me please how you "tricked" the system? I'd like to try it. I'm getting an error message on my export translation effort (the rpc server is unavailable (HRESULT: 0x800706BA) ) and I'm hoping your "trick" will help. I've tried everything I know. THANKS
Hi Sylvia,
You can also try reaching JC directly by clicking on their profile and using the Contact Me button!
If you continue to run into issues with exporting translation, feel free to connect with our support team, and they can lend you a hand!
Thanks Ren! Great idea.
This discussion is closed. You can start a new discussion or contact Articulate Support.