Have you ever received the following error message?
This project is invalid or corrupt and cannot be opened. It may have been created in an earlier version of Storyline.
The team member that received the message was working in the file, attempted a save, and Storyline2 crashed, and upon attempting to reopen, the error message shared above is what the original user and other users receive.
If you have seen this error message, were you ever able to recover your file? If so, can you share how?
I'm so sorry your team member is having this issue with their Storyline file! There's a chance it could be corrupt beyond recovery. However, there may still be a working version of that project in your team member's temp files.
To check, have them:
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.
Because the issue happened after Storyline 2 crashed, I would also suggest having your team member run a repair on their software following the steps for their version of Windows provided in this article to prevent future erratic behavior.
1 Reply
Hi Bob,
I'm so sorry your team member is having this issue with their Storyline file! There's a chance it could be corrupt beyond recovery. However, there may still be a working version of that project in your team member's temp files.
To check, have them:
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.
Because the issue happened after Storyline 2 crashed, I would also suggest having your team member run a repair on their software following the steps for their version of Windows provided in this article to prevent future erratic behavior.
This discussion is closed. You can start a new discussion or contact Articulate Support.