Can't open newer or older versions of Storyline or Storyline 2 files

May 27, 2016

Isn't this supposed to be backward compatible?  I can't open files (created/modified last week or last year), even after updating to the latest version of Storyline.  Greatest concern is it is happening on 3 different files, that were created and modified by 2 different users (we can't open each other's file either).


7 Replies
Christie Pollick

Hi, Sarah -- I also wanted to mention with respects to the corruption noted in the error message you shared, there is a chance it could be dealing with files corrupt beyond recovery. 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.

Here is another post on a similar topic that you may want to review, and in order to avoid corruption in the future, please see this article: Follow These Tips to Reduce Your Risk of Corrupting or Losing Project Files. 

Please let us know if you are all set or still need more help! :)

Christie Pollick

Hi, Sarah -- Thanks for your reply and first, I wanted to note that when you reply to a forum notification via email, the details in your signature are displayed publicly here in the post. If you would like to remove those details, you will need to click here to be taken to the post itself and then use the EDIT button beneath your reply to remove those details. 

I also wanted to confirm what steps were taken with which version, if I can. If you are trying to open Storyline 2 content in SL1, that will not be possible. However, if you are upgrading from SL1 to SL2 and cannot open your files, may I ask if you are working on a network drive, which can cause corruption or erratic behavior as described here?

And have you tried importing the file into a new file and have you gone through these troubleshooting steps to see if you find improvement? 

If those options do not do the trick, our Support Engineers may need to review your system logs to better determine the root of the issue, and you would be able to connect with that team via the form shared here

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