Corrupted project file: does it happen far to often or is it just me?

I had an issue with a corrupted project file a couple of weeks ago. Fortunately I was able to open the project file, I just couldn't edit and save it. So I copied all the slides to a clean new file and things worked fine.

Now I'm having the same issue with a modified version of that same course, but this time I can't even open the project file. :(

The first time it happened I read Articulate's recommendation we not host our project files on a remote file-sharing service. Kinda an absurd expectation in 2017, but OK. So I started working with local files only, then copied them to Dropbox after saving (and closing Storyline) just to have that redundant copy. Nonetheless I still got a project file corruption error on the local file and now I'm really stuck because I can't get the file open at all. I'll try pulling down my last version from Dropbox but aside from that I don't know what to do. This project is literally on the 1-yard line from completion. :(

Am I just having bad luck or is Storyline 360 just not reliable enough for a production environment?

11 Replies
Ashley Terwilliger

Hi Chris, 

With the latest .story are you seeing an error message or it's just not opening? I know that working off a local drive can be difficult for some, but the latency associated with files on an network or shared drive are what can cause the issue. 

There are some other general tips about file maintenance here.  

If you're seeing this happen to each and every file though, I'd wonder if there isn't something else happening. I see that you started a support case - and our team is seeing some higher volumes today - but I'll go ahead and let them know that you reached out here too so that we can get you an answer soon! 

matt thorne

There were several threads on this within the last few weeks. A lot of us had good luck finding the temp file in the %AppData% folder, renaming it and moving on.

It does seem as though there have been a rash of these lately. Hard to believe that at this point in the product's lifecycle that it just randomly corrupts files and that it still requires files to be stored locally. Also...what constitutes local? Google Drive, OneDrive, Dropbox and many others use a locally cached copy that sync up to their cloud server in the background. Why should any Articulate product care if there is a process syncing the file...particularly if the product is using a .tmp file to do the actual work out of?

File and overall application stability has ALWAYS been my major complaint with Articulate products. When they work (which is the vast majority of the time) they are great. But...when they decide not to...it can be maddening.

Shouldn't stability be an on-going goal of the development team? As old as the product is now, shouldn't these kinds of issues have been long ago squashed?

 

Chris Wirick
matt thorne

There were several threads on this within the last few weeks. A lot of us had good luck finding the temp file in the %AppData% folder, renaming it and moving on.

I had no luck finding the temp files as instructed. I'm a Mac guy generally. Though I've used Windows for many years I don't often dig into its plumbing (it's scary in there). How exactly do I find this folder?

Ashley Terwilliger

Hi Chris,

Here's how to look for your temp files: 

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. 

As for the Mac - have you disabled the shared profile between the  Windows and Mac world? That could be the piece that is causing corruption. Here are some other best practices for working with Storyline on a Mac. 

matt thorne

on a Windows box, you'd go to \Users\<username>\AppData\Roaming\Articulate\Storyline

There you'll find a plethora of .tmp files. Look for one that contains the name of your actual .story file. It will also probably have a numeric string at the end of the file name. 

Sort by date/time and when you find the most recent .tmp file, copy it out somewhere safe and change the extension from .tmp to .story. You should be back in business with minimal content loss.

Good luck!