The process cannot access the file because it is being used by another process

Did this ever get a real resolution? I'm facing the same thing. 

Hi Angie,

I can't say what the specific issue was for Shanavaz, but I did look at his case and he was able to resolve it with as he mentioned disabling the .net framework. It's not something we'd recommend since Storyline uses the .NET framework. 

If you're still having difficulty you could look at trying to uninstall and reinstall Microsoft .NET Framework 4. Here's how: 

1) Go to Start > Control Panel > Programs > Programs and Features. 

2) Uninstall Microsoft .NET Framework 4. 

3) Download and install a fresh copy of Microsoft .NET Framework 4: 
https://www.microsoft.com/en-us/download/details.aspx?id=48130 

4) Reboot your system and test again on a newly created project file, saved on your local drive. See if you can replicate the same issue. 

If you'd like to work with our Support team on this issue they'd also be happy to take a look at what's happening on your side. 

I have been having the same issue currently. I have uninstalled and reinstalled the program.  It does not allow me to pull up the file.  If I can't get it then it is hours and hours of work down the drain for a large project that I am working on.  I had the same issue about a year ago with a different computer and company and had no resolution (lost all of it) so I am very worried.  What are some other new options for me?

Hi Hannah,

Are you unable to open a particular Storyline file, or the program as a whole? If it's just one file that won't open do you see a particular error message? If it's just that one file and you're receiving a message about corruption, you may be able to find a copy of that file in your temp folder. Here's how to check: 

1) Open this folder in Windows Explorer: %appdata%\Articulate\Storyline 

2) Scan the contents of this folder for a file that starts with the name of your project. If you find one, copy it to your desktop. If you find more than one, copy the latest version to your desktop. 

3) Change the file extension of the copy on your desktop from *.tmp to *.story. 

4) Double-click the file to open it in Storyline. 

If you can't open Storyline as a whole, and you've already gone through the steps above - let's have you work directly with our Support Engineers so that we can take a look at what's happening. 

Ashley,

I find that the file will open after a restart, for some reason that clears the error.  It is very annoying though.

Hi Ari,

I'm glad a restart helps and gets you a working file again! 

Have you checked into the other troubleshooting steps earlier in this discussion such as:

• Working on local project files
• Importing into a new .story file
• Repairing Storyline

Also, does it only happen on this one file, or all files?

Hi, same issue here. Working on a macbook with Parallels and Windows. 

My solutions was via regedit. You find a good explanation here: https://kb.parallels.com/en/122981

Hope this helps.

Hello. Does anyone have a solution for this issue? Myself and my entire department is now experiencing this issue. We exclusively work on files from our hard drive, never a networked location. We are on Windows 7 and Storyline 2 Update 13: 1804.2716. All of our files can't just suddenly become corrupt. Is there a regedit as noted above (the article is no longer available).

Hi Kim,

Sorry to hear your entire department is coming across this issue! I've opened a case on your behalf with our support engineers where you'll hear from someone on the team soon.

They'll do everything they can to determine what's causing that error to come up!

This issue has suddenly manifested since yesterday. Alarming, considering the number of projects I got to get out the door by EOFY.

I think the autosave must be glitching because when I do go to save there are already a number of extra copies in my folder (XX2, XX3, etc) when I get the "The process cannot access the file..." message.

Sorin Lascu's link isn't working anymore, and maybe it is a Parallels / Windows issue but it's freaking me out.

Any clear cut solutions? I only did a complete refresh install of Storyline to the latest version last week.