Opening file via "recent project"

I've noticed that nearly every time I try to open a presentation via the start up screen's "recent project" section, it always tells me that the file is being used by another process or user. 

When I go to the file location and click on it, most of the time it won't give me this error.

I know that no one else is using the file, so that's not it. Even when I restart Storyline, and for that matter the computer itself, it always throws up that error message. When opening via the file's location gives me that error, the only other way around it is to change the file's location, which is horribly inconvenient. This error occurs when the file is both on the server or on my local HDD, so I don't think it's a server issue.

Is this a problem for anyone else? If so, is there a chance at a fix?

(And while I'm at it, PLEASE make actual "slow" animations!)


3 Replies
Ashley Terwilliger

Hi Darryl,

You mentioned changing the file's location solves the issue - and it leads me to believe you may be hosting this file on a network, shared or USB drive? You'll want to follow these guidelines for working on your .story files or else you could experience odd behavior, loss of resources or file corruption:

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

If your file is behaving oddly, you may want to try importing it into a new Storyline file as described here. 

Darryl Benson

As my previous post stated, this happens if I work off the server OR my local C drive.

My directory path is low... it's on the desktop.

There are no special characters, accents, or symbols in the file names.

This happens to every Storyline file, so importing them into new files doesn't seem like it would be the smartest idea....

Ashley Terwilliger

Hi Darryl,

If you've been moving the files from your server to your local drive, and opening from both places - that could have caused the issue. Are you able to replicate this behavior on a new file that you created on your local drive?

Also since you mentioned it's occurring on every file, I'd want to confirm that you're using the most recent update of Storyline (update 5) and I'd also suggest conducting the repair of Storyline detailed here.