My files every now and they pop up with the error:
"the file XXXX' is being used by another process or you do not have the proper security permissions to access this resource"
Our IT Dept spent and hour last time trying to figure out how to open it and still that wasnt an ideal solution. Anyone know how to hard reset Storyline?
When I copy and rename the file it says "The project is invalid or corrupt and cannot be opened. It may have been created in an earlier version of Storyline."
I see that this thread goes a couple of years back, and unfortunately I am finding it because I am having this issue- constantly! Has there been a fix for this? I never had this issue in Storyline 2, but with Storyline 3 it is constant. Yes, I just copy over the file and rename it but when it happens constantly it becomes an obstacle for efficiency.
I've seen this error frequently appear when backing up projects to a shared drive like OneDrive or Dropbox. You should be able to stop the sync when saving the project, which would eliminate the error message.
This does NOT fix the root problem. The original file is still not openable. All this does is create a copy of the original so you can work on it on your local machine. The problem with this approach is if you work on a network drive as I do with multiple people working on the same file, you run the risk of overwriting people's changes.
This problem is extremely frustrating and it has been going on for more than 2 years now. When will the folks at Articulate find a solution?
Thank you for sharing the details of what you're experiencing! I wanted to share an article that might be helpful for your specific scenario, as we don't recommend working with .story files on a network drive:
I understand how this affects your workflow, especially when working with multiple people on the same project. I’ll continue to share your frustrations with our team as we evaluate how files are saved.
I faced the same error today and tried various options mentioned in the comments, however, none of them worked for me.
At last I figured that my windows security is playing a role in this error. There is an option in windows security to keep your folders safe from being any changes made which is called Controlled folder access option. Please disable it and try, it should work for you!
This happened to me today. Instead of going to my computer folder and then trying to open the Storyline file there, I instead went directly into Storyline and browsed for the file. I don't know why this worked, but it did the trick.
Just encountered this issue, very frustrating! Figured out that I left two blank spaces at the end of my course title which was causing the error. I removed those spaces and it published without any issues.
Sorry to hear you ran into this snag. Thanks so much for sharing what workaround helped you! I'm sure it will help others that come across this thread!
64 Replies
Thank you for this way around it. It has been frustrating have copy and rename the file every time I close and re-open it.
When I copy and rename the file it says "The project is invalid or corrupt and cannot be opened. It may have been created in an earlier version of Storyline."
I decided to revert to an earlier version on the course and that seems to do the trick.
I see that this thread goes a couple of years back, and unfortunately I am finding it because I am having this issue- constantly! Has there been a fix for this? I never had this issue in Storyline 2, but with Storyline 3 it is constant. Yes, I just copy over the file and rename it but when it happens constantly it becomes an obstacle for efficiency.
Hello Sara!
I've seen this error frequently appear when backing up projects to a shared drive like OneDrive or Dropbox. You should be able to stop the sync when saving the project, which would eliminate the error message.
Let me know if this is a possibility!
This does NOT fix the root problem. The original file is still not openable. All this does is create a copy of the original so you can work on it on your local machine. The problem with this approach is if you work on a network drive as I do with multiple people working on the same file, you run the risk of overwriting people's changes.
This problem is extremely frustrating and it has been going on for more than 2 years now. When will the folks at Articulate find a solution?
Hi, Wendy.
Thank you for sharing the details of what you're experiencing! I wanted to share an article that might be helpful for your specific scenario, as we don't recommend working with .story files on a network drive:
I understand how this affects your workflow, especially when working with multiple people on the same project. I’ll continue to share your frustrations with our team as we evaluate how files are saved.
Hi Calamity Jane,
I faced the same error today and tried various options mentioned in the comments, however, none of them worked for me.
At last I figured that my windows security is playing a role in this error. There is an option in windows security to keep your folders safe from being any changes made which is called Controlled folder access option. Please disable it and try, it should work for you!
I'm glad that you were able to identify the culprit, Shyam. I appreciate you popping in to share and welcome to E-Learning Heroes. 😊
This happened to me today. Instead of going to my computer folder and then trying to open the Storyline file there, I instead went directly into Storyline and browsed for the file. I don't know why this worked, but it did the trick.
Hi Kasie-Marie,
Thanks for sharing what worked for you! Others in the community with the same issue will surely find this helpful!
Just encountered this issue, very frustrating! Figured out that I left two blank spaces at the end of my course title which was causing the error. I removed those spaces and it published without any issues.
Hi Patrick,
Sorry to hear you ran into this snag. Thanks so much for sharing what workaround helped you! I'm sure it will help others that come across this thread!
Same like Patrcik Lynch: A blank was the problem for me also..