Forum Discussion
Corrupted Temporary FIle - Oh no!!!
I have been working on my Storyline all day when it just died, usually in this situation I can open the file again and it shows what it has recovered, but its saying locked by another process and to copy and paste it and open it that way. But this doesn't recover anything! I have found the temporary file but it says it is corrupted! It is a whole days work, please help. I would greatly appreciate help of any sort.
unfortunately when it gets locked it does not autorecover, I have not found a way around this.
This is not good... so the whole day's work is lost. :(
Hello Paul!
Sorry for the trouble! We definitely want to work with you to see if we can find a working version of your project. Can you first look to see if you have a version in your temp folder?
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.
I've also started a case on your behalf to have our Support Engineers work with you directly to make sure this doesn't happen again! You should've received an email confirmation for the case. Feel free to reply if you have additional questions!
I have the same problem. Two months of work gone down the drain!!!
Working fine one day, not the other. Tried to install previous version (updated a week ago - meanwhile the file was working fine) and still same error. Tried to save file, rename it with a .story extension. Nothing! Both version of files same problems. Last version of Articulate or new, same problem.
In the list of files worked recently the file appears without an image. Other files appear with image and work ok. Including some worked yesterday and that today work.
The working files are in an external SSD as I need to work on more than one laptop. Tried all the various laptops and it's the same on all. I do not see any file in %appdata%\Articulate\Storyline on the C: disk of the main laptop I work with.
I am considering changing authoring tool. It's one of the most unstable software I ever used and it's a continuous struggle. I cannot save tenth of files with different names and the SSD I work with is of good quality and I do not have a problem with anything else. It's always this software that cause problems.
If you can help I would appreciate, otherwise I will propose we change authoring tool.
Thanks
A very frustrated professional user
I get your frustrations, have you reached out to Articulate as they may be able to help. It is odd that both files on the same drive are corrupted, however working from an external drive is not a great idea as latency is one of the main causes of corruption.
Do you have backups? All my files are backed up every 30 minutes so I do not lose any work as well as weekly backups. Have you tried copying the files off the drive onto the laptop?
Unfortunately we have a very peculiar security issue here and we are forced to use multiple laptops (3 in my case) as we cannot have all the software one need in one (i.e. graphic design sw and other cloud based apps) and need to work in different locations but cannot move the laptop. SSD is a pain but it's the only way to have files to come with the developer, not the devices.
Before we were forced to continuous savings of files and transferring was leading to confusion on which version was which and the SSD solution is not ideal but the only workable solution.
I am going to try the other method you kindly suggest. Will report back.
I am not sure where any autobackup files go. I cannot locate any folder for that in programfilesx86.
Yes I opened a case with Articulate support cause this is really a big one for us.
Thanks a lot for the help!
Copied file on desktop and lunched it from there. Same error
Launched*
Hello And B,
Thank you for letting us know that you reached out to the support team as well. I can see that Lianne is currently taking a look and you should be hearing from them soon.
