Is my Store open?

Hi all... 

Just wondering if anyone's received a...

       The project file could not be saved.

       Store must be opened for this operation.

...error message?  Just started popping up today...

Working on a good dell latitude, 3 GB ram, using Win 7, 32-bit, 16-days to go on the 30-day trial copy, w 83 GB of hard drive space free... Storyline file is 333 MB in size.

Michael

83 Replies
Daniel Brigham

Rebecca and Diane: Same thing happened on the latest project I was working on. And like you, I'd been working with it for 60 days or so before the issue appeared. I opened a new SL file and imported all the stuff. So far, so good.

I suspect the latest update may have something to do with it. Sorry about that hassle. We all abhor losing work. --Daniel

aditya sarangi

Add me to the list of victims too.

It happened to me right now, and i lost about 4 hours of work. Other files are working just fine.

I was working with 2 SL files together, and hit save on one, and hit open on the other one, and bang. the error popped up.

Rebooted my machine, made some more changes to the file and the save works. 

Leslie McKerchie

Hi aditya! Sorry to hear that you experienced some difficulty.  The resolution for the last case, for John that was mentioned above, was that he did a repair (as shown in this article) and the behavior went away.  Not sure if that would work for you as well.  If you continue to have difficulty amid your own troubleshooting, feel free to put a case in so that our support team can work with you. Thanks so much and have a great day!

Heather Penningroth

Peter Anderson said:

Hi Anna, 

In addition to working locally, here are a few other suggestions from Payal's case:

If your Storyline software is not working properly, a simple repair may fix the problem.  Please review the following article to learn how: 
http://articulate.com/support/kb_article.php?product=st1&id=zibo784o5b2e 

In addition, please try to delete the Storyline project logs and temp files by following the instructions below: 

1. Right-click on the Windows start button and click Explore 
2. Type the following in the address bar and hit return: 
%USERPROFILE%\AppData\Local\Articulate\Storyline 
3. Delete the project logs in this folder 
4. Right-click on the Windows start button again, and click Explore 
5. Type the following in the address bar and hit return: 
%temp%\articulate\storyline 
6. Delete the temp files in this folder 

Restart your machine, then test Storyline again. 

If the issue persists, can you check if you still encounter the issue when working on a new project in Storyline? 

If the issue only occurs in one particular project, you may need to troubleshoot the issue further with this Storyline file. Try importing the slides from this project to a new Storyline file, and see if this helps improve Storyline's performance. Here's how to import slides from one Storyline project into another: 
http://community.articulate.com/tutorials/products/importing-from-another-storyline-project.aspx 

Hope it's helpful, and thanks for submitting the case. 


#3 above - I don't have project logs in the folder, but I do have export.log. I'm guessing I should leave that alone?

James Brandwood

Leslie McKerchie said:

Hi Heather! Actually, this thread is a bit dated and there may be a better solution for you.  Can I get you to submit a case with your .story file so that support can look at your particular issue? Thanks!


LOL how do I sumbit the .story file if I can't save it?

I just got this error message and was hoping to find a solution here but it seems there isn't one that will rescue my work.

I had just saved my work, did about 5 mins more, saved again (I save often given all the crash probs with Storyline) and got this error. It's weird because i've been working on this file for months and just came back to make one or two changes following it's UAT. While working on this file I did open a storyline file from the netwok drive to reference a slide trigger. I didn't make any changes or save it, I just closed it. I'm guessing that is what has caused this error even though it is a different instance of Storyline.

Fortunately I can save the file after closing it and then opening it again straight away.

I  have to say, when it comes to weird and wonderful save errors Storyline takes the cake

Anna Porter

Has anyone figured out yet what will really work here?  I have been having nothing but problems with this file and this error is killing me! :(

I even tried the old "Heather" fix except I get hung up on #1: Right-click on the Windows start button and click Explore .  When I right click on the start button I get two options: Properties & Open Windows Explorer.  Not "Explore." and when I type
%USERPROFILE%\AppData\Local\Articulate\Storyline  into just the search bar in "Search all programs and files" I get a list of files that are empty.

Help!!

Leslie McKerchie

Hi Anna! Sorry to hear that you are still having difficulty with this. Is this still the same large file that you mentioned previously in this post and in your Windows Media question? I'm not sure how big your course is, but here are some best practice tips in this thread.  If you are having so many issues with this one file, you may want to try to import into a new project to see if that helps (that's the one thing I did not see you mention).

Emma Dugan

Leslie McKerchie said:

Hi Anna! Sorry to hear that you are still having difficulty with this. Is this still the same large file that you mentioned previously in this post and in your Windows Media question? I'm not sure how big your course is, but here are some best practice tips in this thread.  If you are having so many issues with this one file, you may want to try to import into a new project to see if that helps (that's the one thing I did not see you mention).


This is what I did to get around the issue, and it worked. Thanks!

Edward Crane

I just received this message for the first time today. It happened after I accidentally launched a Storyline project while one was already open. I've learned in the past that having two projects running at the same time is problematic (not sure if there is a "best practice" in this regard). Luckily and will not have lost much work. 

I think one thing you could do to try to save your work is to open another Storyline project (yes, I know, it goes against what I just said) and copy and paste slides from your existing project into another project, then save that project. Of course, if you get the same error message, you are in the same boat.

My Articulate mantra (really, for any software product): Save early and often. 

I would like to request and auto-save function be installed e.g. the recovered files that MS Office has.

Destery Hildenbrand

Just a quick note on this error. Ran into the same thing today, not able to save. I was able to publish the file, which was helpful to use as a guide to ensure I had a record of all the changes I made. Not the best but I know its hard to remember changes or exact steps and locations of things when doing it a second time, this was the best of a bad situation for me

Hopefully a fix can be worked out soon to avoid the store all together. : )

Richard Knudson

Hi everyone,

I just got this error message yesterday and it prevented me from saving a file a colleague had created. I tried a number of different things including saving the file as a new name or to a new location, but none of that worked.

What actually worked was to close Storyline and then change the file name through Windows Explorer. After this, I reopened the file in Storyline, hit the save button and got no error message. I then made the needed changes and saved again with no error message.

I am not sure if this is a real fix, but it worked for me so it might be worth a try.