The project "Storyline" is locked by another process (Help!)

Hi David,

Thank you for contacting Articulate community. 

As of August 16, 2018, Storyline 3 is on Build 3.5.16548.0. Please see to it that the current version is applied. If the issue remains after applying the latest version you may refer to Ashley's post here for further help. 

Alternatively, you may also send us a copy of your .story file to allow us to perform some analysis and test on our end. 

Looking forward to getting a response from you soon. 

Hey Ron,

Thank you for the quick response!

I've uninstalled, and then reinstalled the Storyline 3 software a few times during my troubleshooting process. 

I've attached a .png of the current Storyline 3 Build. 

The .story file is attached.

Hi David, 

Thank you for uploading the requested files.

I was able to launch the Module_3_Distribution_Center.story file on my end with no errors. So that brings us closer in identifying the potential bottleneck for this scenario. 

Apart from performing a clean install of Storyline, we can also give these recommendations a go.

• You must create a local copy of the .story file on your local directory (C:) If the file is automatically saved on any in-cloud services such as Dropbox, Google Drive, One Drive 
• Copy and rename your .story file in File Explorer, and then open the new file from there

Good luck! Keep me in the loop for any development. 

As Ron says duplicating the file and opening the copy will unlock it

Hey guys,

I really appreciate your assistance. I have gotten farther with this file then before but I am still encountering a similar error when trying to save the file. 

I am attempting save the file directly on my desktop (C:) 

Take a look at the 2 error messages I recently received, the first 1 happen when I first opened the file, crashing program.

The second attachment is a screen shot of my entire Storyline 3 as I attempted to save the .story file. 

The file path its displaying is not the location I am attempting to save on, as I am simply saving the file onto my desktop.

Thank you so much for all of your help thus far!

David

Hi David,

Thanks! I appreciate you explaining how it would help us out in finding the correction for this incident. 

If you can provide the following information, that will help us track down what’s happening and figure out the best way forward.

• Have you tried turning off your endpoint antivirus? Your security protection must have marked the .story file as a threat, prompting the file to be quarantined in the temp folder. to release the .story file from quarantine you need to either stop the AV by turning it off or by adding the target file on the white list. 
•  Let's try to disable UAC
• Using the 'Save As' option, create a new file name and point the .story file to the desktop location 'C:\Users\xxxx\Desktop'

Give it a go and let me know your feedback. 

That was it!

Once I turned off the endpoint antivirus the .story file no longer had any issues opening or saving and I am able to resume my work! I also learned about msconfig.

Storyline 3 operating smooth.

Thank you for troubleshooting this issue! The real problem had nothing to do with Storyline 3 having corrupt files or anything, like my initial concern.

Your product and service is top quality!

David

Hi David,

Thank you for allowing us to take advantage of your time and patience. 

Have a good one!