When exporting a Storyline 360 file, I receive an error message advising an error has occured and storyline needs to close. When clicking on the coding of the error, I receive the following error message (see attached).
I've tried to export both with Word and XLIFF, with no luck.
Sorry, you're having trouble getting your Storyline 360 courses published! I’d love to help you troubleshoot the issue!
Testing this out on my end, I was able to successfully export the course translation to both Word and XLIFF without an error message. Everything was working normally!
Just some clarifying questions:
Which version of Storyline and which version of Word are you using?
Do you see this error with all projects or just this specific one?
Are you seeing that error message when previewing or publishing the entire course to web?
Are you working and saving locally? Working on a network drive or an external USB drive may cause erratic behavior due to latency.
If that doesn’t do the trick, you can share your project file with us in a support case or in this discussion. Either way, we’ll take a look and share our findings with you!
Looking at the error message, it appears that there is a character that can't be properly exported when the XLIFF file is being created. The hexadecimal character being referenced in the error message is 
It may look something like the following in your course: �
You'll need to find that character or look for something odd and out of place and then remove it to see if that fixes your problem.
While you wait to hear back from the Articulate team, you can try the following to see if you can find and correct your problem. It's a bit tedious but it should work:
If you can't see anything obvious, next steps would be to make a copy of your course and then step by step, delete parts of the course to see where the problem might be.
1. If you have multiple scenes, delete a scene, and then export the XLIFF file. If it's successful, then you know the problem was in the last scene deleted.
2. Once you isolate it to the scene, you will then go to that scene and delete the last slide and then export the XLIFF file. If it fails, delete the next slide. Once successfully published, you will know which slide caused the problem, which would be the last slide you deleted.
3. Once the slide is isolated, you can then re-create the slide and delete the original slide with the the problem. Note: If you can't see the problem character on the slide you're re-creating, it would be best not to copy and paste from the original and instead re-create by hand.
2 Replies
Hi Learning & Development
Sorry, you're having trouble getting your Storyline 360 courses published! I’d love to help you troubleshoot the issue!
Testing this out on my end, I was able to successfully export the course translation to both Word and XLIFF without an error message. Everything was working normally!
Just some clarifying questions:
If that doesn’t do the trick, you can share your project file with us in a support case or in this discussion. Either way, we’ll take a look and share our findings with you!
Hope this helps!
Looking at the error message, it appears that there is a character that can't be properly exported when the XLIFF file is being created. The hexadecimal character being referenced in the error message is 
It may look something like the following in your course: �
You'll need to find that character or look for something odd and out of place and then remove it to see if that fixes your problem.
While you wait to hear back from the Articulate team, you can try the following to see if you can find and correct your problem. It's a bit tedious but it should work:
If you can't see anything obvious, next steps would be to make a copy of your course and then step by step, delete parts of the course to see where the problem might be.
1. If you have multiple scenes, delete a scene, and then export the XLIFF file. If it's successful, then you know the problem was in the last scene deleted.
2. Once you isolate it to the scene, you will then go to that scene and delete the last slide and then export the XLIFF file. If it fails, delete the next slide. Once successfully published, you will know which slide caused the problem, which would be the last slide you deleted.
3. Once the slide is isolated, you can then re-create the slide and delete the original slide with the the problem. Note: If you can't see the problem character on the slide you're re-creating, it would be best not to copy and paste from the original and instead re-create by hand.
Good luck!
Thor