Error publishing Storyline project

Apr 07, 2016


I am getting this error when I try to publish my project:

If I export the project to a new file, it publishes fine with no issue, however, the player features are lost once the project is exported. Once I add the player features of the original project, I start getting the error. It looks like the problem is in the player but I have no idea how to go around that. Any suggestion is greatly appreciated.

I am also attaching the error report.


6 Replies
Christie Pollick

Thanks for your response, Suha, and for letting us know that the troubleshooting steps unfortunately showed no improvement. I'd actually like to recommend that our Support Engineers take a look at your error report to see if they are able to offer additional suggestions based on their analysis. 

I will go ahead and set you up in a case momentarily and you will be receiving a confirmation email to that effect very shortly. I plan to follow along with their progress and will share updates here for others who may come across this post in the future seeking assistance. :)

Christie Pollick

UPDATE here for anyone following along with Suha's case... After additional review of her file, our Support Engineer Karla shared the following:

"Thanks again for sending your file and allowing us to review it. 

You're correct in saying that the issue is with the Player, I was able to replicate it. It appears that there may be corruption in the Player and you may need to recreate it. 

File corruption is unpredictable, and there's no straightforward way to determine what causes it. Common causes are environmental (disk errors, power outages, improper shutdowns), viruses, failed Windows updates, and even file size (i.e., very large files have a higher risk of corrupting). 

Consider these preventative measures to protect your project files: 

1) Save and publish projects on your local hard drive. Working on a network drive or external USB drive can cause erratic behavior due to latency. 

2) Save incrementally. If your app has an AutoRecovery feature, take advantage of it. If not, save a new version of your project every hour or so with a new file name each time. If a file becomes corrupt, you'll still have a working version available. 

3) Install Dropbox. Snapshots of changes in your local Dropbox folder are kept for 30 days. If a file is damaged or deleted, you can restore a previous snapshot:

4) Don't leave the app open and unattended for long periods of time. Some users have reported file corruption after leaving their apps open overnight. It's possible that a malware scan or disk backup could run because the machine is idle, making your app vulnerable to crashing. 

Let me know if you need anything else!"

Hope that helps! :)

This discussion is closed. You can start a new discussion or contact Articulate Support.