Bit of an EMERGENCY - Translation Export in Windows8

Hi Ashley,

I lost the business since it was a very rushed project and I was not able to help because of having this issue.  I haven't needed to use it since then, but continue to look forward to a fix. I have not heard back from any Storyline support or developer with a resolution or work-around.

Thanks!

Tammy,

I'm sorry to hear you lost the business. I took a look at the case and see that it was still with our team and being reviewed by QA as there have been inconsistent results in recreating the behavior. Going back through your case, I don't see if there was an indication if you were able to complete the repair of Storyline and re installation of Office? 

It is definitely frustrating. I had to open SL2 from Windows 8, right mouse click and selected "run as Administrator". Once back in desktop top mode I opened the story file I needed the translation from. I spent far too many hours trying all the other methods and trouble shooting. 

Thanks Shawn for sharing that here and I'm glad it worked for you to use that method. 

Should your installation of Storyline work only, or completely in Administrator mode, you may wish to check this out: https://technet.microsoft.com/en-us/magazine/ff431742.aspx

Hi Ashley,

So, I actually had just upgraded from SL1 to SL2 right before I had this issue. I also upgraded my Office suite just a few weeks prior so it was a fresh installation. It is not currently an issue since I don't have work that needs a translation, but I don't have confidence in the feature so I'm reluctant to take on work where I'll need it.

There is a predicable pattern with the issue that I'm not sure is being considered in the troubleshooting. It's interesting to me that it works fine the 1st time you run the export, then crashes for each subsequent attempt. This happened to me in SL1 and SL2 and it happened exactly the same way for my husband.

I tried Shawn's workaround by testing the same file I had attempted to export for the client. I tried it first by running the FILE as administrator with no luck. I tried again running SL2 as an administrator with the same result.

This seems to be a common issue. Maybe it doesn't have a larger impact because not everyone uses the translation feature, but it is a glitch for sure that should be seriously investigated.

Thanks!

Tammy

Hi Tammy,

Thanks for sharing that here - although it's been reported by a few users here it's  not something that our team has been able to replicate. I know you've been working as a part of a support case, but if you'd like we can continue to take a look at your file there and let us know the exact steps you go through to replicate this so that our team can take a look. 

I have experienced the same issues as Tammy mentioned. First time it works, then doesn't subsequently. I had used this feature in SL1 and it worked fine. Once it worked in SL2, then didn't anymore. I looked up and followed suggestions at that time  (working locally, on desktop, short filename, clear logs, run as admin) and ONCE, right after installing an SL2 update, was able to get it to work. Now, it doesn't again (even after going through suggested fixes again).

I hope a solution can be found as it was a handy feature.

Hi Catherine,

Thanks for reaching out here and as you'll see I mentioned to Tammy our team hasn't been able to recreate it yet, so we'd want to take a look at your file and find out more about the set up and steps you're going through to see this. Can you reach our to our team here? 

Thanks Ashley,

I did, but interesting discovery as I prepared my support report. I decided to trim my story file down in size first. I deleted a bunch of scenes/slides/question bank. I tried Export for Translation with the small file and IT WORKED.

I went back right away to my original file and IT WORKED too. I wonder if others try to export very small, simple files to clear the blank error message would also help.

Happy I got my file, although I'm curious still about what's going on here.

Thanks,

Catherine

Hi Catherine,

Thanks for the update and I'm glad its working! For the original file, did you not remove anything from there? Did you do anything else before trying to do the export again? 

Hi Ashley:

No, I didn't delete anything from the original before trying again (after
the little one worked). And, I didn't do anything else, simply opened and
exported it right after the little one worked. Strange, but true.

Thanks, Catherine

Fingers crossed that it not working was just a fluke? :-) 

It may just be that it needed a reset with a shut down of Storyline and or your computer. Without being able to consistently recreate it, it's hard to say what may have caused it. 

I was having the same issue today.  The translation export would fail and the error message pop-up was blank.  Word wasn't open, but I did have a few other apps running (Firefox, excel, etc).  I closed EVERYTHING.  Still no help, so I opened up Windows Task Manager (CTRL-ALT-DEL) and looked at the Processes tab.  I had a few MS Office apps running even though I couldn't switch to them in user mode.  So I clicked "END TASK" on them and then tried the export again and.....SUCCESS.

Thanks Steve - it seems that those steps help a number of users to ensure an other office programs are shut down to prevent any issues with the export. 

Hi All

I've had this problem for quite some time now.  I can only export to translation with just the one column, not the "reference" column.  So I'm resigned to a workaround ...

As I need the English text to refer to, once I've exported the word doc, I copy the column for translating and paste it at the end - voila! - I get my extra reference column.

Hope this is some help to someone - it only takes a couple of seconds to add the extra column.

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.