Can't Save Storyline 2 Project

I've searched the forum but I couldn't find my answer.  I have been creating a course in Storyline 2 and I've just finished updating all my scratch audio and narrations.  When I go to Save or Save As.. I get an error

" The Project File cannot be Saved.  Cannot access a disposed object.  Object name: 'StoryPackage'. "

I can preview and publish but I can't save?  I haven't tried exiting without saving because I'm an old Storyline 1 user and I'm leery that I will lose my edits.  This is the first time with the new Storyline 2 that I've had an issue.  I remember during the release notes there was something listed about AutoRecover, does this work?

What should I do?

Thanks,

Spencer

43 Replies
Emily Ruby

Hello Spencer!

Sorry to hear that you are experiencing this issue. This is a known issue that is currently being investigated by our Support team. The best thing to do is to share your information with the support team, and we will be adding updates on the forum as we get them.

 

Auto recovery will work if you have already saved the file once. After that it will auto recover at the intervals you set up in Storylines properties. The default is 10 minutes.

You can follow along with the current open thread here for more information.

Stephana Gaudin

I am having this issue as well. I recently updated to Storyline 2 and so I have the latest version. 

What are the steps to fix this? I imported an old presenter (powerpoint) file into storyline 2 and have been working on it all day... saved about 3 hours ago, but won't save now. 

Any help?

Jenn Barnett-Russell

Has there been any update on this? I honestly get a lot of errors when saving Storyline files but this is a new one. I just worked on a file for over an hour of design and color scheming but the file would not save due to this error.  After a lot of attempts and reading these posts I closed the file assured that it would recover, it did not.  There is no point in even uploading the file that it tried to save as it is just 1KB and shows a message of "This project is invalid or corrupt and cannot be opened."

Leslie McKerchie

Hi Jenn!

Are you utilizing the latest update, which is Update 7?

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.
 
Also, be sure to always create, edit, and publish projects on your local hard drive. Working from a network drive or a USB drive can cause erratic behavior due to latency, such as file corruption, an inability to save changes, and loss of resources. See this article for details.
Mia Anderson

I have the latest update that was just sent out and I am now getting this issue.   It looks like this issue has been going on for quite some time.   I was able to use the previous version saved and only lost minor work, but that is not an acceptable work around.

I get errors all the time, especially after I do an update. 

Leslie McKerchie

Hi Mia!

You are welcome to reach out to our support team here if you are continuing to see errors. They can have you pull logs and check some additional items to get to the root of what may be happening with your setup.

I wanted to share the following in case helpful as well:

File corruption is unpredictable, and there's no straightforward way to determine what causes it. Common causes are environmental (disk errors, power outages, improper shutdowns), viruses, failed Windows updates, and even file size (i.e., very large files have a higher risk of corrupting).
 
Consider these preventative measures to protect your project files:
 
1) Save and publish projects on your local hard drive. Working on a network drive or external USB drive can cause erratic behavior due to latency.
 
2) Save incrementally. If your app has an AutoRecovery feature, take advantage of it. If not, save a new version of your project every hour or so with a new file name each time. If a file becomes corrupt, you'll still have a working version available.
 
3) Install Dropbox. Snapshots of changes in your local Dropbox folder are kept for 30 days. If a file is damaged or deleted, you can restore a previous snapshot: https://www.dropbox.com/help/11/en.
 
4) Don't leave the app open and unattended for long periods of time. Some users have reported file corruption after leaving their apps open overnight. It's possible that a malware scan or disk backup could run because the machine is idle, making your app vulnerable to crashing.
Christine Lopez

It's a little frustrating.  Project won't save.  Your support team is asking that it be uploaded.  Since I can't save, that's not possible.  As a new user, I'm so disappointed to see that this is such a large problem.  I've not heard back.  I'm trusting that you will provide assistance.  Please advise.  

Alyssa Gomez

Hello Christine,

So sorry to hear you're having trouble saving your project - I know that's frustrating. I can see that you're working with Victor in Case #00984907 and that he recommended creating a folder on your Desktop called "Articulate Project" and trying to save your current project in that folder.

I'll continue to follow along with your case and share updates here as they are available!

Kelly Taylor

Hi guys,
I had this issue today, but I found that the common thread was when I was working from a .storylinetemplate file and hadn't saved it as a new .story document before commencing any work.
I know this may not be entirely helpful to everyone's situation, but just a little hiccup I found myself.