6 Replies
Daniel Brigham

Welcome, Erica: This error does happen. What helped me save two hours' of work was to open a new Storyline file, and import the files you are currently working on and can't save. You should be able to save the new SL file.

That worked for me. I then deleted the corrupt SL file (i.e. the one that isn't letting you save). --Daniel

Ashley Terwilliger

Hi Erica and welcome to Heroes!

Daniel shares the same suggestion I would have about importing into a new Storyline file, but granted it will only import up until your last save. 

You'll also want to check the following things while working on new projects to prevent future corruption:

  • Work on your local drive (your C: drive). Working on a network drive or a USB drive can cause erratic behavior, including file 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.
sandie coco

I just encountered this for the first time. Luckily I am programmed to hit Ctrl S often. I left the unsavable project open, launched another instance of Storyline and imported the slides. Then I was able to copy the slides I had added/modified and paste them into the new storyline project. Since it hadn't been that long since my last save, it was only a few slides that I had to copy/paste.