The file 'Storyline' is being used by another process

Dec 30, 2014

Hello. I get this error quite often on a project I am working in SL2. I have never seen this error before and never in SL1. It usually happens when I open the file first time in the morning with no other programs running and, of course, loading from the local drive only. Storyline will load, but not the project. I am usually able to open the project from there using the Browse function (bottom left).

40 Replies
Ashley Terwilliger-Pollard

Thanks Nate for confirming those elements. It is something that our team has been looking into, but it's  not consistent or always reproducible to determine a root cause. If you've been able to consistently reproduce it we'd want to find out a bit more information so I'd invite you to work directly with our Support engineers. If you do choose to connect with them, can you let me know the case number so that I can follow along? 

Ashley Terwilliger-Pollard

Hi Hanneke, 

What update are you on and what update or version was the file created with? This discussion is quite a bit older, so I'm not sure if the same steps apply in your case.

Let us know a bit more detail on where your files are stored normally, how you're accessing them, version of Storyline being used, etc. and I'm happy to help with other troubleshooting ideas! 

Noel Sapp


This issue seems to be resolved based on the reply from @Nate Herrema below. After moving the working file FROM the server that uses automatic backup syncing TO my local desktop, I have not experienced this issue. 


January 17, 2020 and this is still happening in Storyline360. This just started for me yesterday morning when opening the working file from the previous day. When opening, I get the "The file [filename] is being used by another process or you do no have the proper security permission to access this resource. Make a copy of your project file then try to open the new file."

Same thing happened just now. Copying and renaming the copy allows me to open the new file, but this is getting silly. I can't give my client files that they may not be able to open.

FOUR years??

Ashley Terwilliger-Pollard

Hi Noel,

Sorry to hear you ran into such trouble, but Nate to the rescue! Working on files from a network/shared drive is known to cause some odd behavior such as the error message you saw, and could ultimately results in corruption. 

To avoid it, I'd always recommend working on local project files as described here. Once the file is saved and closed, you can then move it to a backup storage service. 

Noel Sapp

Just to follow-up, Nate's comment pointed right to my problem. We do use a backup system that syncs working files. Copying the file to my desktop and working from that has not reproduced this issue. Just I need to add another step to work flow as this file is not automatically backed up until it is copied to the server.

Thank you again.

Katie Riggio

Hello Cynthia,

Great move to also reach out to our Support team

I see that Philam recently recommended the How to Fix Unexpected or Erratic Behavior in Storyline 360 steps. 

In the meantime, Noel raised a good point: If you are using a backup system that syncs working files, disabling the syncing or saving the files to another folder on the C: drive should do the trick.

Let us know how you go. We'll be right here! 😊

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