Problem with the translation export in Storyline

Hi Byron,

Currently this is by design that Storyline files need to be created, edited and published to a local drive and is not considered a bug by our team. If you need to work in a collaborative environment there is a suggested workflow here, and if you'd like to see future support for working on a network or server drive, I'd suggest sharing those thoughts as a feature request. 

Thanks Ashley

Thanks for helping me understand.  I did encounter some further issues working locally, but am able to fix this through an import in a new file as above,

Even so I would still consider it a bug when something partially works and fails with an empty error message. maybe the error message could state 'Storyline files need to be created, edited and published to a local drive ' as I was not aware or made aware of this whilst working, and through sporadic progress assumed this is meant to work.

I'll enter working from a remote drive as a feature request.

Thanks

Byron

Thanks Byron for sending it in as a feature request, and I'm glad to hear the import and working on your local drive is allowing you to continue on your project. 

I would like to know if support has narrowed down the cause of this issue.  I have followed every suggestion here, but the export is still failing with no error.  

I can open a support file, but I'd prefer to just see the results of previous support issues.  

Thanks!

Hi Terry,

This thread is a bit longer, and there were a number of different issues, the most recent being that Byron wasn't working with local project files. If you could tell us a bit more about your set up, or what's occurring we can narrow down the issue that you may be experiencing 

Thanks Ashley - I will open a new support file.

T

Hi all,

Just had more failures, and wanted to report that tried Anthony's suggestion, and it worked perfectly, first time. All other suggestions have failed.

Christine/Articulate - is it possible for you to investigate why this may still be happening, even with the latest SL update? Anthony's suggestion seems to be very specific, so might it point to the cause of this, and after further investigation on your end suggest a fix and/or routine that needs to be put in place in coming versions?

Thanks.

Hi Bruce,

Reading back through this thread, I see that myself, Christine and Leslie took a look at the different cases where users shared files, and it was either file specific or system specific, so it wasn't something that our team was able to reproduce on new files. I took a look at Terry's case, which is the most recent one here and it seems that she may have been trying to save the .doc file to a network drive, which is similar to a few other users in this thread. She shared that she resolved the problem after confirming she was saving locally.

If you're able to consistently reproduce the issue while working on all local project files, we'll be happy to take a look again. You can share the files here in the forums or connect directly with our Support engineers. 

Anthony's suggestion worked one time for me, twice it didn't, working locally after importing the storyline content into a new storyline file works every time in my situation.

There seemed to be more issues when the network file is set to sync and always be available offline.

Regards

Byron

Hi

I too am having an issue exportig files to word for translation. This is from a file I built over a year agoat which time I was able to export the files to word for translation, no problem. I have now come back to the same .story file as a new language is required and get the same, less than helpful, error mesdsage.

Was this issue ever resolved?

Jeremy Miles

Hi Jeremy,

Throughout this thread it seems that each user's case was a bit different so it's hard to narrow it down to one specific issue. You may want to check into the following items to start with, and then we're always happy to take a look at your file:

• What update of Storyline are you using? We're currently on update 5.
• Are you working on your project files as described here?
• You'll want to check that you haven't modified any of the column IDs or headers and are following along with the translation processed detailed here.
• You mentioned you're having issues in a file created in an older version of Storyline, have you tried a brand new file to see if the behavior persists?
• Has anything else changed in terms of your set up: i.e. Word version, file location, etc.?

After you have been able to check into those elements, please let us know how the translation process is working.

Thanks Ashley

As suggested I have tried exporting a more recent created project and that works fine. I'm pretty sure I upgraded Storyline since I last exported files from the project in question. Does this help in pinning down the source of the problem?

Thanks

Jeremy

Hi Jeremy,

It certainly sounds like it may help in pinpointing the issue.

There are a couple of things that come to mind, but first I think it's a good idea to tackle possible corruption of the file first.

I recommend importing the slides from the original course into a new file in Storyline. If you haven't already tried this, it may help:

Importing from Another Storyline Project - E-Learning Heroes

If you still have trouble, please consider sharing your .story file here so we can take a look at this. If you're not comfortable sharing the file here, or if the file is larger than 20 MB, please let us know. We can discuss other options for sharing the project.

Please let us know how it goes!

Christine

Hi Christine

I have followed your instructions and made a new version of the course by importing all slides into a new file. I still get the same problem.

I'd like you to have a look at the file and see if you can identify the cause of the problem but it is a large file (56Mb). Can you recommend the best way to get the file to you securely?

Thanks

Jeremy

Hi Jeremy,

I also wanted to let you know that we released Storyline Update 6 last week, and you can view the information here in regards to what fixes were included. Do you know what update of Storyline you're using?

Also, if you'd like to send the file to us directly you can upload it to this form. On the second page you'll be able to provide a description and attach the .story file. To ensure it's assigned to me instead of one of our support engineers you'll want to enter the following exactly as written at the start of the description:

::ashley::

I'll let you know when I receive it and begin to review it.

Thanks!

Hi Everyone,

I've found that sometimes just using the "SAVE AS" function and creating a new story file has cleared this issue for me in the past. I've always just assumed that something was corrupt with the story file and that the "save as" essentially made a fresh story file and voila problem fixed.

Give that a try and see what happens.

Cheers

Hi Jose & Christine

Good idea Jose, but didn't seem to work for me.

I have changed laptops since writing the original program. When I went back to the old laptop (which is running the same version of Storyline as the computer that is giving me problems (5.14012405) - I could export the test as a word document no problem. Whemn I repeat the procedure on the new laptop - the problem re-appears.

Both PCs are running on Windows and both have MS office installed so I'm not sure why I should be unable to export successfully from my newer laptop.

Any thoughts appreciated

Jeremy

Hi Jeremy,

Have you tried repairing the installation of Storyline as described here? You'll need to go through each step, but since it works on another computer with the same set up, I suspect that something occurred with the installation on the new laptop.

Please let us know how it behaves after checking into those repair steps. If you're still having difficulty, we'll want to take a further look at your files and set up through a support case.

Encountered this error on my current project, and Anthony Fitzgerald's solution on Page 2 worked for me. Strange!

Yes, same issue in 2014. I'll log a case number.

I also tried exporting to a new file and making the file name really short but it didn't work. It only happens with one file.

Thanks Danielle - and I see your case (#00420479 for my reference) so we'll follow along as well. 

HiDanielle,

Iwas checking in on your case today and I see that Cleo shared the following:

MayI ask what version of MS Word are you using?

Do you encounter the same issue with a new file or is the issue filespecific?

I tested your file and I was able to export successfully using my StorylineUpdate 6.

To troubleshoot the issue further, please try to download a new copy of theStoryline Update 6 installer, then try to run repairs to your MS Word. Then tryto follow the instructions in this link.

Pleasefeel free to let Cleo or I know if you continue to have difficulty

I am having the same problem exporting the translation document using Storyline 2. I am using the latest version of SL 2.  I have entered a problem report with Articulate, but I have not be contacted from an engineer yet. I have tried all the suggestions expect for uninstalling Storyline. I am unable to edit the User Account Control (probably an IT restriction). And when I downloaded the slCleanup.bat file it was flagged as malware and Windows recommended I do not use it.

Any suggestions would be appreciated. I am under a deadline and I need to send the course for translation in the next few days.

Jim

Hi Jim,

Do you have a case number to share here so that I could follow up on your issue? Our team was off a few days last week due to the Christmas holiday so that may be a part of the delay in responding to your case. If you submitted it well before the holiday and didn't hear anything, please also look in your junk/spam folder for an email from Support@articulate.com