I get an error message (see attached screenshot) whenever I try to either export for translation or import a translated course in Word. I get a similar error when publishing in Word.
I already uninstalled and reinstalled Storyline 2, but it did not make a difference.
Using: Articulate Storyline 2, update 11. Word 2016. Windows 7 Enterprise. 64-bit operating system.
Can we take a look at this .story file and the translation file you've got? You can send them along to our Support Engineers here, and then they'll also be able to take a look at your system settings.
This email may contain information that is privileged or confidential. If you are not the intended recipient, you may not disclose, copy, distribute or use this e-mail or its attachments.
We'll want to see the translation document for the same project so that we could take a look at trying to import it back in as well. Since it looks like you responded via email attachments are also not posted to the ELH page. You'll need to visit this page and using the “ADD ATTACHMENT” button at the bottom of the forums reply window upload your project. If you’d prefer to not share in the public forums you’re always welcome to share with our Support Engineers here. They’re available 24/7 to assist!
Also, when you respond via email it'll includes your signature here in ELH. You are welcome to visit the forum discussion and click on the "edit" below your post to remove that information. No worries on our part - just in case you don't want your information publicly!
While I don't have a solution to share from Raquel's scenario, we're happy to help! A few questions to start:
What version of Storyline and Word are you using?
If you're able to share the .story and translation files with us for testing, that would be gold! You can send it privately to us by using this link. We'll let you know what we find, and will delete it after having a closer look.
Let me know, and we'll explore next steps from there!
Apologies, it's been busy times and we've had to have other staff do the initial imports as an increasing number of our devs and ID's have run into this same issue.
Imports/exports fail using both SL360 and SL3 Imports/exports work using SL2 In all cases using Windows 10, Office 365/Word 2013
It doesn't appear to be related to the translation file (.doc) or any particular .story file but rather the linkage between office/word & storyline. The error comes up as soon as any word doc is clicked from the import dialog, and happens as soon as 'OK' is clicked int he export dialog. Office and SL360/3 have both been uninstalled/reinstalled numerous times, but to no avail, this is still occurring.
Not sure if any of this helps, I can't show it with dummy files as I can't export word files, and am not authorized to share client materials, but here's the dialog that comes up on import... (for reference, the icon in the dialog on export is the exclamation in a blue circle).
8 Replies
Hi Raquel,
Can we take a look at this .story file and the translation file you've got? You can send them along to our Support Engineers here, and then they'll also be able to take a look at your system settings.
It appears that regardless of the Story file I use, the program behaves in the same manner.
I’m including one of the Story files and a Word document that that my supervisor exported for translation (they’re not for the same project).
RAQUEL HERNANDEZ
Technical Support Training Specialist
1 760-744-5240 Main
1 760-304-7280 Direct
1 800-733-2823 Technical Services
1 760-471-4296 Fax
[cid:image003.png@01D2AC4F.89D1D630]
1940 Diamond Street
San Marcos, CA 92078
USA
www.hunterindustries.com
This email may contain information that is privileged or confidential. If you are not the intended recipient, you may not disclose, copy, distribute or use this e-mail or its attachments.
Hi Raquel,
We'll want to see the translation document for the same project so that we could take a look at trying to import it back in as well. Since it looks like you responded via email attachments are also not posted to the ELH page. You'll need to visit this page and using the “ADD ATTACHMENT” button at the bottom of the forums reply window upload your project. If you’d prefer to not share in the public forums you’re always welcome to share with our Support Engineers here. They’re available 24/7 to assist!
Also, when you respond via email it'll includes your signature here in ELH. You are welcome to visit the forum discussion and click on the "edit" below your post to remove that information. No worries on our part - just in case you don't want your information publicly!
@Ashley - Was this ever solved? Our team is experiencing this issue and we can't find a fix.
@Ashley - Was this ever solved? Our team is experiencing this issue and we can't find a fix.
Hi there, Jay!
While I don't have a solution to share from Raquel's scenario, we're happy to help! A few questions to start:
Let me know, and we'll explore next steps from there!
Apologies, it's been busy times and we've had to have other staff do the initial imports as an increasing number of our devs and ID's have run into this same issue.
Imports/exports fail using both SL360 and SL3
Imports/exports work using SL2
In all cases using Windows 10, Office 365/Word 2013
It doesn't appear to be related to the translation file (.doc) or any particular .story file but rather the linkage between office/word & storyline. The error comes up as soon as any word doc is clicked from the import dialog, and happens as soon as 'OK' is clicked int he export dialog. Office and SL360/3 have both been uninstalled/reinstalled numerous times, but to no avail, this is still occurring.
Not sure if any of this helps, I can't show it with dummy files as I can't export word files, and am not authorized to share client materials, but here's the dialog that comes up on import... (for reference, the icon in the dialog on export is the exclamation in a blue circle).
Hi Jay! I'm opening a case for you so we can get this sorted out as soon as possible. You'll hear from one of our Support Engineers soon!
This discussion is closed. You can start a new discussion or contact Articulate Support.