Is my Store open?

Jun 06, 2012

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
Anna Porter

Hi Peter:

Thanks for the speedy reply.  I did go through the "repair" operation but strangely enough at the end I got a message from Installshield that the program might not have downloaded properly.  Not sure what to make of that.

Checked the appdata and temp files.  Not much there but deleted it.  Will try again.  Just frustrating as I had just finished the 6th redo of a video for software simulation and lost it!

Jeanne Bernui

I just got this error message for the first time today, and I have been using Storyline pretty extensively the past several months.  Will try the repair as outlined above, and hope that it helps!  Frustrating to lose work!  I tried copying it to a new file, still gave me the error message.  It was a brand new file that I just started working on today, so I guess it's good that I only lost about 30 minutes of work.

Trisha Johnson

HI all. I'm having this issue too and just lost all of my work for the past hour. Rebooting is not the best option since I'll lose my work but I'll give it a try.

Also note that I noticed another issue just before this one. When I tried to "undo" something, I was taken to a different slide in the course. The slide I was taken to had no relation to the current slide I was working with and I hadn't touched the slide it brought me to in a couple of hours. I was not able to "undo" what I had done.

Cynthia Klassen

Hi,

I have been getting this message intermittently and I've been putting up with it (but losing valuable time).

I'm getting quite frustrated.

Has anyone found a solution to this?

I have 3 different .story files that I've been working on since November and it happens to all of them at some point. There is no rhyme nor reason. I can go for days without the error, and then suddenly, when I'm least expecting it, it pops up again.

I try to save frequently but because my files are so large and the save takes so much time I don't save as frequently as I would like to, therefore I end up losing time when the error happens.

I've uninstalled/reinstalled and that hasn't fixed the problem.

Are there any peramanent solutions to this?

Thanks,

Cynthia

Christine Hendrickson

Hi Cynthia,

First, if you haven't already done so, make sure that your project files are all local.

  • Work on your local drive (your C: drive). Working on a network drive or a USB drive can cause erratic behavior, including file corruption, loss of audio, and other unexpected behavior. 
  • You should also make sure the directory path to your project files and your published output is less than 260 characters (for example C:\Articulate).
  • Avoid using special characters, accents or symbols in your file names.

Additional information regarding "Naming Files, Paths, and Namespaces" in Windows operating systems can be found in the following Microsoft article.

Also, what method did you use to uninstall and reinstall Storyline? If you haven't already, please try following the steps outlined in the following support article:

Unexpected or erratic behavior in Storyline

If the problem continues, please let us know.

Thanks!

Christine

Cynthia Klassen

Hi Christine, Thanks for your quick reply. I think this will help me.

  • I am working locally.
  • My path name is not too long.
  • But ... I did have a special character in the name of my project "Safety & Security". I have removed "&" from the entire path and hopefully I won't see the error again.

Have a great weekend,

Cynthia

Christine Hendrickson

Hi Cynthia,

Thanks very much for getting back to me! Sorry to hear that you're still running into this.

Were you able to try the steps in the article I linked, as well? 

If the issue continues, it may be best to go ahead and submit a support case with us. 

Submit a Support Case

Please be sure to include a description of your issue. Please also include the URL for this thread in the form. Also, please share the case number with me. You're welcome to do so here, or in a private message. This way I can follow the progress of the case and update this thread.

Thanks, Cynthia!

Christine

Christine Hendrickson

Good morning Cynthia. I hope you had a great weekend!

I was able to find your case (#00329923 for my reference). I see that Miker is currently testing the files you attached to the case. He should be in contact with you soon.

I'll keep an eye on the case progress and try to follow up with you here if I see any updates. 

Thanks!

Christine

Julian Stubbs

I have just experienced the same issue this morning. I am working on a large file (122) slides and it takes ages to save, so I've not been saving as often. Now it says:

 The project file could not be saved.

 Store must be opened for this operation.

I really don't want to close the file and restart as I'll lose an hours work.

Grrrrh.

Christine Hendrickson

Hi Julian,

I know you posted this an hour ago, but hopefully this may still be an option that will save you some time:

Importing from Another Storyline Project

Now, you should be able to import most of the content into the new file. Hopefully all you'll have to do is bring over the content manually that wasn't saved.

I know it's not a fun process, but I wanted to suggest this just in case it could possibly save you some time.

Al Smith

I started having the same problem last night.  At the time it wasn't critical as I had just saved to my USB.  I assumed the problem was because I had 4 Instances of Storyline open and one of the instanced had a lock on the system IO.  Well, today it happened again 3 hours into my project, and I only had 1 SL instance open.  Having to do the copy and paste as well.

Christine Hendrickson

Hi Al,

You're saving to a USB, but you're not running it off of the USB, correct? Just want to make sure, sometimes that can make a big difference. You can certainly store a copy of the projects on your USB drive, but try to work with the files locally, if possible.

  • Work on your local drive (your C: drive). Working on a network drive or a USB drive can cause erratic behavior, including file corruption, loss of audio, and other unexpected behavior. 
  • You should also make sure the directory path to your project files and your published output is less than 260 characters (for example C:\Articulate).
  • Avoid using special characters, accents or symbols in your file names (this includes spaces and underscores).

Additional information regarding "Naming Files, Paths, and Namespaces" in Windows operating systems can be found in the following Microsoft article.

Thanks!

Chris Wall

Just ran into this one today for the first time. Trying to put the finishing touches on a course that needs to be published tonight, and there's that message:

The project file could not be saved.

Store must be open for this operation.

Everything had been going swell. Nothing out of the usual going on on my PC.

I was able to get out of the file and only lost 10 minutes of work or so, but still... that error message looks to me to be one that Articulate put in their code, and that a very specific condition or set of conditions associated with saving a file are causing it.

Anyhow, re-opened the file, made some changes, saved the file successfully, but then, when I was attempting to change a character, Storyline locked up solid. I had to use Task Manager to shut it down, and then Storyline locked up Task Manager as I tried to shut it down.

Here's my question: do I need to worry about my Storyline file being corrupted now that this has happened? Do you guys have any sort of file check utility that I could apply to my files to ensure that everything in the file is copacetic?

This discussion is closed. You can start a new discussion or contact Articulate Support.