Error Message - Project could not be saved / other process

May 25, 2012

Hi all, 

I have received an error message several times today that looks like screenshot below.  It reads, "The project file could not be saved.  The process cannot access the file [file directory node] because it is being used by another process." I can't think of another process that could possibly be using the .story file I am trying to save.

  I have tried saving with different names and in different locations.  I have tried opening another instance of storyline and opening this file.  Nothing seems to work, and at this point a lot of effort will be lost if I just close.  Any suggestions?  

45 Replies
Julie B.

Hi Nevin,

Did you have the same again? cold you solve this?

I thought my question would seem really odd or dumb but kind of happy to read you post it before me.

I have exactly the same message

'it is being used by another project' each time I open and try to save the SL project.

Let make it really simple: I open a story file, do not even change or touch anything but want saveit again, or to rename it, or to save it on another place......this message appears.

I dont see nothign that would be used or running as I have not even done anything ..!

I need help too now

Peter Anderson

Hi guys,

That's the kind of message I've seen show up when working from a network or USB drive. What drive are you working from? You might also want to ensure that your file path is less than 260 characters and doesn't contain any special characters. Let us know if that might be the case, and if not, would you mind submitting a case so we can take a closer look into it? Thanks!

Nevin  Katz

Yes, it seems to be somewhat of a "fake" error message at times, as I notice that the timestamp of the files reflect my most recent save, and when I open them, they do have my changes.   It does seem to restrict the file name I am saving it under.   My workaround is to change the filename and open it up in another instance of Storyline to make sure all my changes are there.   I have tried multiple file paths and short file names - neither of them seem to work.  Once I get through this project I'll probably submit a case on this.  In the meantime, I hope my workaround helps people.

Peter Anderson

Hi Nevin, 

Please do submit a case when you get the chance, including the link to this url for the details, so we can help figure out why you're getting the error messages. You'll also have a chance to do a screencast during the case submission process, and if you could replicate the error, that would be really helpful too. Thanks!

OneDay Interact

Hi, we have the same problem as Nevin Katz and a few others have experienced: when saving the project we got the error mesage ""File could not be saved.  COM-object that is separated from its underlying RCW cannot be used." . No idea what that means. 

The file was saved though, two out of three times. 

Is this is a bug that you're looking into? 

Thanks in advance, Brit 

Peter Anderson

Hi Brit,

If the steps in this article dont help eliminate the error message from popping up, it would be really helpful if you could submit a case. And during the case submission, you'll get a chance to record a screencast replicating the exact steps you take to get the message, which will help us pinpoint the root cause. Thanks!

David Chronister

This message has been bothering me for the past month! It seems that even when I save it to the local drive, it still is giving me the same message. Sometimes it will actually save the file, other times it gives me this exact message. People are saying this is a network issue. But in my case, this is happening on any local drive as well.

Becky Barch

I just started receiving this message in the last week or so. This file has always resided on my local drive. Sometimes it will save the file but most of the time I get the "The process cannot access the file "C:\...." because it is being used by another process. I've tried renaming the file, saving it in a different location.

Any suggestions?

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