Project invalid or corrupt and cannot open, early version of storyline

Is there a fix for this?

Do we know why this is happening?

I've spent two days putting my eLearning together and tried to finish it off today, however, got the error message 'project invalid or corrupt and cannot open, early version of storyline'.

I've tried restoring from a previous version and I've tried importing, tried changing the name, tried everything.

I'm hoping there is a fix or a remedy, as I do not really want to have to spend another two days doing it again.  I have other elearn's to do and deadline's to meet.

Please help.

Steve

4 Replies
Emily Ruby

Hello Steve,

Welcome to the community. Sorry you are having issues with your file. You'll want to check the following which could have caused file corruption:

  • Work on your local drive (your C: drive).Working on a network drive or a USB drive can cause erratic behavior, includingfile corruption, loss of audio, and other unexpected behavior. 
  • You should also make sure the directory path to your project files and your published output is less than 260 characters(for example C:\Articulate).
  • Avoid using special characters, accents or symbols in your file names 

You said you tried importing the file, but you may want to try importing the slides one by one. If this works, you may be able to see if there was one slide in particular that was corrupted, and hopefully not the whole file.

Steve Thomas

Hi Emily,

I tried everything possible and nothing worked.

Emailed support and got the same stock reposnse.

I appreciate that these thigns are out of your control, however, it is remarkably frustrating when spending days/hours building and eLearn and then for it to be corrupt, almost drove to madness.

I gave up in the end and did them again, waste of a weekend :-(

Is there going to be a fix in place to stop this from happening again?

Are your technicians aware of the issue?

Steve

Emily Ruby

Hi Steve!,

Sorry to hear you were still having issues.  Unfortunately, once a .STORY file becomes corrupted, it's no longer recoverable. It is also very hard to determine the root cause of the file corruption. 

But I would advise to go over any steps that support had sent out as options, and see if you can implement a back up file recovery system that may help with any future issues. Do you have an IT team who could set something up?