Corrupt file - getting to be a serious issue now!!!

May 18, 2016

Hi there,

This has happened to me twice now in the past few weeks - I go to access a module I've created (one was a few years old, one a few weeks old) and it tells me the file is corrupt and won't open. 

I've tried all the suggested solutions - keeping the name simple, working of my local drive - and this still seems to happen every now and again. This time however it's really getting to be an issue as I've now lost weeks of work. 

The only saving grace is I've been able to find an older version of my module in my temp files (there were 2 - one was corrupted and the other wasn't), but it's such an early version it isn't going to save me that much time, I'm basically back to square one. 

I have an output file in SCORM 1.2. I tried importing the corrupted file into a new project, but it says that the file is being used/I don't have permission to access it - not that it's corrupt. 


Please help - this is really urgent!!! I also can't attach the original story file, so have attached the published file. 

4 Replies
Leslie McKerchie

Hi Wendy!

Sounds like you are having issue across your projects, which may mean there is a software issue.

Are you utilizing the latest update to Storyline 2, which is now Update 8? This would repair your software as well.

If you are on the latest update, please follow the troubleshooting steps for a repair in this article to fix unexpected or erratic behavior in Articulate Storyline 2.

Mark Shepherd

Hi Wendy:

Corrupted data in Storyline can be a tricky and frustrating process if it is not caught early.

That being said, it IS possible to work around damaged or corrupted files in Storyline 2.

Try this approach, and let us know how this works for you:

1. In the latest update (Update 8, released in May 2016) of Storyline 2, create and save NEW Storyline (*.story) Project using a comparable filename similar to your corrupted project.

This new project will serve as a CONTAINER to hold the CONTENTS of your corrupted project.

In most cases, this should also serve to reset and effectively PURGE your project once its contents are loaded into the container.

2. Using the File > IMPORT function, ADD ALL of the SLIDES from your corrupted Project.

3. Once done, RE-SAVE this Project under a new, UNIQUE filename, and if necessary, backup, just in case.

If you are lucky, this new project should now be uncorrupted and relatively issue free moving forward, while still maintaining the functionality of what you had previously.

Bear in mind that issues can come from multiple angles/vectors, and for a variety of reasons, such as loading too much content on a slide, making a slide and its associated triggers overly or too complex, and a number of other issues that can be difficult to track.

Note also, that not all projects can be rescued in this manner, which is why it is so critical to do multiple micro-incremental saves of your work, so you can roll-back to a previous version, just in case.

For me, the primary clue that informs me my project is corrupt is when the editor crashes, usually when I am trying to modify a key visual slide element or change a trigger that is part of a complex series of interactions.

Hope this helps!

-Mark

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