Forum Discussion
Help! Desperate plea! Can anyone open/publish this STL file?
Can anyone open this STL file? I get the error of "This project is invalid or corrupt and cannot be opened. It may have been created in an earlier version of Storyline."
I have never seen this error before. Changing the file name does not work. I backed up a version and still no luck.
It contains quite a few GIFs, so I wonder if that's the issue? If anyone can open this...can you please send me the SCORM 1.2 package?
Katie
Hello Katie,
Sorry to hear about your project file.
I took a look at it and it does appear to have gotten corrupted. This article explains common causes as well as tips on how to reduce the risk of encountering this issue.
If you were recently working on your project file when the incident occurred, 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.Hope this helps!
Sadly, that project is not in my temp folder.
Does Storyline hate GIFs? I have quite a few transparent GIFs in this project…could that have contributed to the corruption? I’ve been using STL for years and have never had an corrupted file. And this is the first project I have used GIFs in….so I think they are related.
Thoughts?
K
Hi Katie,
We're not seeing other users report any issues with using GIFs in their projects so we believe this incident may be isolated. We encourage you to open a case with our support team here so we can investigate what happened with your project file as well as identify how to prevent this from happening to your files again.
your file got corrupt while writing
storyline stops writing after the first step (export the media library)
there is the whole internal xml structure missing
@articulate: this is an unsolved problem since more than 8 (!!!) years
Update - correction: not after writing Media Library, but while writing Media Library
@articulate: if this statement from your CTO is meant seriously, this should be your number one bug to fix
Articulate doesn't like cloud storage. Keep your files on your computer and store a copy in the cloud. I have seen this several times with my files and other people in my office.
@articulate:
the problem is not that the files become corrupt - this can happen in cloud directories where other programs have write permissions at the same time.the problem is that storyline does not check the result* of the "save" command and and tried again
if it's not possible to save a correct .story file the user has to be informed !!!
* a technical validation of a .story ( = .zip) file should be done under 1 sec
