The file 'Storyline' is being used by another process

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).

35 Replies
Ashley Terwilliger

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? 

Hanneke Portier

Receiving the same error message. I can open some files and not others. Rebooting, changing names, import in new project and saving to desktop is not working. We have to wait for our local IT service to do the update.

It is not right to have to install an update to be able to use the same file. Very disappointing.

Ashley Terwilliger

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

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??