This project is invalid or corrupt......

I updated Storyline due to the latest release.  I then attempted to open a file I had been working on just previous to this release and now I receive the error message - "This project is invalid or corrupt and cannot be opened.  It may have been created in an earlier version of Storyline."

Please let me know if there is a fix here, I'm under a time constraint and don't need this headache with this course.

117 Replies
Jeff Willison

Our problem was fixed a long time ago by deleting a font we had gotten on
google fonts. Apparently SL didn't like that font. When we got rid of
it-everything saved fine. It was Oswald in our case but it may be a font
that is corrupted, look in your fonts and see if you have any that you may
be using that are corrupt. That's all I know-hope this helps.

Leslie McKerchie

Thanks for sharing Jeff :)

Prardhana - I cannot access or import your file.

Unfortunately, once a .STORY file becomes unusable, it's no longer recoverable.

When creating, editing, or publishing a Storyline project, we recommend working from your local hard drive (typically your C: drive). Working from a network drive or a USB drive can cause erratic behavior, such as file corruption, an inability to save changes you've made to your project, and loss of resources.

 Here's a helpful article for you.

John Bellotti

The motherboard fried on the other computer and I was able to salvage the hard drive and transfer the information to the new computer. All the files seem to work from the hard drive except the Articulate files so it almost seems like they needed something from the old computer for them to work.

Deepak Mohanty

Hi,

I have a course which I had created in Storyline 2, so for me there is no migration issue from SL1 to 2. But I still get similar error that the file is corrupt and so on. And I asked my company IT guy to do whatever possible to recover that 1 hr long e-learning module which was supposed to be updated on our LMS the earliest. Now, it's certainly a pain to redo everything from scratch. 

I believe this bug needs to be resolved the earliest. Or going by the old formula which is certainly relevant - to keep multiple copies of the file at different location before we update anything in the original.  :(

Ashley Terwilliger

Hi Deepak,

I'm sorry to hear you ran into a corruption issue with your .story file. 

However, there may still be a working version of your project in your temp files. Here's how to check:
 
1) Open this folder in Windows Explorer:
 
%appdata%\Articulate\Storyline
 
2) Scan the contents of this folder for a file that starts with the name of your project. If you find one, copy it to your desktop. If you find more than one, copy the latest version to your desktop.
 
3) Change the file extension of the copy on your desktop from *.tmp to *.story.
 
4) Double-click the file to open it in Storyline.
 
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.
 
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: https://www.dropbox.com/help/11/en.
 
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.
Sri Harsha Kotamarthy

Hello Ashley, 

Sorry If I'm posting the question on old thread. Googled and landed on this page.

I'm working on Articulate Stroyline 2.0 and got this error message "This project is invalid or corrupt and cannot be opened. It may have been created in an earlier version of Storyline. 

All my project is ready and suddenly the file got corrupted is there any auto-saved available and please guide me how to get back my project. 

Please reply me.. Waiting for your help.... !

Thanks, Sri Harsha Kotamarthy (Technical Writer, India)  

Ashley Terwilliger

Hi Sri,

No apologies necessary - you're welcome to pop into old threads. If you're using Storyline 2 you may want to try the steps here to follow and see if there is another copy of your file in the temp folders:

1) Open this folder in Windows Explorer:
 
%appdata%\Articulate\Storyline
 
2) Scan the contents of this folder for a file that starts with the name of your project. If you find one, copy it to your desktop. If you find more than one, copy the latest version to your desktop.
 
3) Change the file extension of the copy on your desktop from *.tmp to *.story.
 
4) Double-click the file to open it in Storyline. 
 
Additionally you could look at importing the existing file into a new project file as described here. Sometimes I find that is effective when receiving odd error messages or opening an instance of Storyline first and then trying to open the file from within there. 
Leslie McKerchie

Glad to hear that you were able to recover your file Sri!

Unless we get down to the bottom of what caused your corruption, it would be difficult to say what the long-term solution would be. 

I would advise that if you run into any difficulty again that you work directly with our support team so that we can try to identify the root cause of the issue.

At the same time, I'm sure we all hope it does not happen again to warrant this need.

Andy Steele

i have just had the same experience and while it is nice to have a community try to find work-arounds, this is an issue and needs to be fixed. Comments from staff such as "I'm sure we all hope it doesn't happen again" are not good enough - unless the bug is identified and fixed, it will happen again. I'm sure you won't be putting the warning "Please note, projects are prone to corruption at any stage and may be unrecoverable" on the purchase page or that Storyline 2 is unstable. My 3 day project is now unrecoverable and has to be rebuilt.

Ashley Terwilliger

Hi Andy,

I'm sorry you've run into this issue and error message. I know that our team has continued to investigate things such as this, but since the way in which users see that message has not been consistent it's difficult to have pinpointed the particular issue needed to be fixed. If you'd like to connect with our team and share your .story file as a sample and the steps you went through just before the error message that would be helpful in tracking down the root cause of such. You can send the file along privately here to our team.