Project won't save - Storyline 2

Try ctrl+alt+del and kill the process and see if auto recovery saves you.  Otherwise it is already lost, sorry

Darryl, we've had a small group of users report this behavior in Storyline 2.

We're trying to get to the bottom of the problem, and there are a few common themes that we've noticed thus far:

• The problem seems to happen more often with project files that have been upgraded from SL1 to SL2 than with files that have been created from scratch in SL2.  Can you confirm this?
• The problem seems to happen more often with project files that contain videos (even unused Screen Recordings) than with project files that contain no videos.  Can you confirm this?
• When the problem occurs within a given project on a given machine, it seems that the specific machine is forever unable to perform a Save, Save As, or Import against the project in question.  However, when moved to another machine, the file may perform normally.  Can you confirm this?
• This Knowledge Base Article doesn't seem to help.  Can you confirm this?

If the above is confirmed (or even if it's not, for that matter), we'd love it if you could send us 3 things:

1. The SL2 .story project file that is giving you problems.
2. The backed-up SL1 .story project file before it was upgraded to SL2.
3. A set of Storyline 2 Error Logs.

We look forward to hearing from you.  Thanks!

Hi Simon! 

I was attempting to follow up on your case, but I am still not seeing one for you.

Michael - this is something that our support team, engineers and QA teams are working to understand. It has not been something that there is a 'generic' fix for and you are welcome to work with support on this as well.

Hi Michael,

Yes, we've shared all the case numbers and project files with our QA team. As I mentioned earlier, there are a few different error messages and set ups that we're seeing - so it's difficult right now to say that they're all the same - but they are being investigated together. I do see that your case was shared with our QA team, and until we have additional information to share our support engineers would not reach out again on your case unless you emailed them with updates. As for the other case number you shared, I don't see a case associated with that one and it looks to be at least one number too long. Can you check that again or if you can share the co-workers name I can try to track it down that way? 

There are a few of us who moderator the forums (myself included) to reply, assist with troubleshooting and provide updates. Our QA and Engineering teams don't often have time to get into the forums to reply, so there may only be a handful of us that you hear from here. Please know that we're in communication with them regularly and sharing updates as they occur in this thread or from our support engineers who are testing files in the case. 

Well, I've had some success in the last two weeks. I did a little research on how I could get applications to perform better and found something created by AMD that seems to really improve Storylines' performance and I never had a save issue since I started using it. It's called Ramdisk and it''s free. It's not the ideal way we want to run Storyline, but it seems to work.

First I installed and reviewed the instructions from AMD on how to set it up.
Bassically it takes your Ram and allocates a portion of it for specific use and calls it a ramdisk. I have 8GBs of ram, the program is limited to 4GB allocation in freeware mode. I didn’t want to allocate that much anyway so I set 2.5 GB’s up for the Ramdisk.

Next I uninstalled Storyline 2 and did a forced Location install of the program to the ramdisk using the instructions provided by articulate:
http://www.articulate.com/support/storyline-2/how-to-change-the-installation-location-for-articulate-storyline-2

After the install I copied over my project 600MB project to the ramdisk and I still had 1.25Gbs left on the ramdisk. Plenty of room for the project to grow.

During my edits I noticed the projects published 3x faster, saved about 2x faster and I never had a lockup or save error.

Only draw backs I could see is that my system slowed down for any other tasks which is likely due to the reduced available ram for the system. If you use it, I would suggest that when you’re done using storyline that you copy your project to your normal save location. The ramdisk will save the stoyline app and files in a ramdisk.img that can be unloaded/loaded at anytime, but will start with your windows if you don't unload it before shutting down.

Hi all,

Storyline 2 Update 4 was released Friday, which included the following fixes:

• Fixed issue where a project file couldn't be saved due to "Store must be open for this operation" error
• Fixed issue where temp files weren't purging, which could prevent project files from saving
• Fixed issue where Quizmaker '09 quizzes couldn't be imported with Flash Player 16 installed

To install the latest update for Articulate Storyline 2, use the download link in your product activation email, or download the latest installer here. Updates are free for existing Storyline 2 licensees.

Yay.. what a lovely program we paid 700 bucks for...

Ended the program. It recovered, but won't let us save.

This is a SERIOUS bug, Articulate. The whole file is a lost cause, and half a day of work isn't able to be saved.

Hi Darryl,

I don't know if you  have already - but can you connect with our Support engineers so that they can help you pull more system information and event logs to help narrow down the problem you experienced? 

I'll do that now, thanks.