Storyline Translation Export to Word Not Working

Thanks Catherine for sharing that update and the steps you went through. We'll include that in the report that we have filed with our team as they continue to investigate the issue. 

Thanks Catherine for your update. I feel your pain and frustration, seems
we have been on the same journey to solve this issue.

After my exhaustive Google searches I could not find a viable fix for this
issue.
Seems to be an inherit clipboard bug which has been in the last number of
Window OS and/or Office releases.
Have repro'd this on Win XP, 7, 8, 10 and with Office 2010, 2013, 2016.

One other strange thing to add to the mix is if I set up a brand new PC
with nothing else installed except Office and Articulate, it will continue
to work for a period of time, then eventually the export will stop working
with the usual blank error message. I've noticed this happens after a big
windows auto-update... hmmmm seems fishy.
So moral of the story is to turn off automatic updates, however that's not
really great on a personal desktop for security reasons.

My only workaround is to set-up a virtual image that has just office and
articulate installed, with automatic updates turned off, and also I have
snapshot saved so I can just reload it clean.
It solves all my issues, except running in Virtual can be a lot slower,
especially for large Courses.

Ashley please keep us updated if your teams track this bug down.

Cheers,
Anthony.

Got a problem? Odds against you? Call The Localizer!
http://www.thelocalizer.com/

Hi Anthony,

Thanks for sharing the workaround set up you're using here - as although it's not ideal, it's not one I've heard so I can share it with our QA team for them to continue their investigation. 

We'll keep folks updated here once there is any additional information to share, so thanks again for your patience and sharing the inventive ways you're continuing to work with this set up. 

Hello,

I need Heeelp :( 

I have the same problem I can't export translate file .doc.

However I have no problem with the export to the file .XLIFF.

I m' following the guide and i had always the same problem.

Should I send the file to support team ?

Thanks for you return.

Hi Aida,

Thanks for reaching out here and I'm sorry to hear you've run into difficulty. It sounds like your following the guidelines to work locally so that's a good first step - and can you also confirm that you're using the latest update of Storyline 2 Update 7? As you'll see mentioned earlier, this is something that our team is aware of, and we're happy to take a look at your file as well to determine if there are any other causes or if it matches the known issue. If you'd like to send it along to our Support Engineers here we're happy to take a look. 

Hi all,

I wanted to provide an update here, as Storyline 2 Update 8 was just released, and included a number of fixes which you can see in the release notes available here. The item you all may be particularly interested in is how it fixed an issue where exporting text to a Word doc for translation wouldn't always work. You can download the latest update here, and after downloading and installing the latest update you’ll want to republish any existing content to ensure that the updates and fixes are applied.

Let us know if you have any questions, either here or by reaching out to our Support Engineers directly.

Wow, excellent, I would love to know how it was fixed, as PowerPoint handout export has a similar issue by the way :-)

Anyway I still have some clients using Storyline 1, so I have to still use that version on their projects. Is there any plan to include this fix in an update to Storyline 1? Pretty please ;-)

Cheers,

Anthony.

Hi Anthony,

As to how they fixed it - no idea, and not sure it's something we could share!  I also don't know the status of any fixes being rolled back into Storyline 1 as well - but perhaps they just need to be convinced to upgrade to Storyline 2? ;-) 

I Updated to the newest version of Storyline on Friday, and just noticed that I also am having the same problem, with the same window with no message. I am running Windows 7, WORD 2016. 

Hi Frances,

Do you have one of your .story files that you're able to share with us? 

This is the one I was using, but I also tried it on a brand new 1 slide file with just 1 textbox. And I had the same issues.

Frances Rampey
Senior Course Technologist
[http://go.reliaslearning.com/rs/reliaslearning/images/reliaslogo

Hi Frances,

Responding via email does not include your attachments here in the forums. You'll want to visit this page and use the "add attachment" button at the bottom of the reply window. 

If it's of any help, I had this problem and solved it by ensuring that Word is the default app for all relevant file types.

The only way to do this properly (on Windows 10) is to follow these exact steps:

Go to 'Windows Settings'

Select 'System'

Select 'Default apps'

Select 'Set defaults by app' option (not any other - it doesn't work any other way)

It will then take a moment to find all apps on your system.

From the list it generates select the version of Word installed.

Click the 'Set this program as default' option.

Click OK.

Close everything down and restart.

And I bet your problem is solved.  Mine was.

Thanks for popping in to share D and welcome to E-Learning Heroes :)

I recently encountered this very error (strange blank popup message and no actual translator file returned), and I believe I've found the cause and resolve.  It was only while shutting down Storyline and while shutting down my computer that additional messages started popping up that helped paint the picture.

Here's what's going on: Storyline is copy/pasting your presentation's text into a Word file, and Word's spell-check and grammar-check are losing their minds over the "errors" they're seeing and trying to fix.  The message chime you hear part-way through the translation effort is a message from Word that it's giving up on your file.  This is why Storyline users are receiving only a partial file of their whole presentation (if they get one).

How to fix it: go into Microsoft Word (or other application that manages .doc files), and over to the options/settings/controls for spell-check and grammar-check (in Word 2013, it's in 'Proofing,' and don't forget to clear check-boxes in the 'Settings' button on 'Writing Style').  Disable them all.  Storyline will have no problem turning out a translate file.

Hi Noel,

Thanks for sharing these steps here - I've seen a few different causes of the translation to Word failing, so it's always good to know other examples and solutions for users. 

I am experiencing the same issue. I have tried all suggested fixes and repairs of SL. any suggestions?

I'm sorry you're hitting that roadblock, Shawn! I see that you've also reached out to our Support Engineers in a case- that was the perfect move 😊

Your case has been escalated and someone will be reaching out to you soon to get this resolved. 

I'll be keeping an eye on your case, too! 

This worked for me. Thanks a bunch!