I am trying to save my Storyline Project, but when I try to save it on my local drive I get the following error message: The project could not be saved. One or more errors occurred."
What are these errors, as it is not telling me?
Any assistance on this would be greatly appreciated.
Eek! Sorry, you're running into those errors (we're working on making the text there more descriptive!) but it would help to know what version/update of Storyline you're using? You can check by going to the "Help" Tab -> "About Articulate Storyline".
Also, you mentioned trying to save locally which is what we always recommend. Was the file previously saved to a network/shared drive? Have you also checked the general best practices here to prevent odd behavior that ultimately leads to file corruption?
I always try . importing a file into a new local .story file too - that often resolves any of those errors.
Hello - I have the same problem since yesterday. And it affects every project file. It has become impossible for me to save anything, even a new empty project doesn't save.
Saving to the desktop, fresh log-in or a fresh install of Storyline also didn't solve this issue.
On another machine there is no problem with the same files. Colleagues can open and save the same project files.
Most times it reads "The project could not be saved. One or more errors occurred."
Sometimes it says it could not find "System.Diagnostics.Debug. Version=4.0.0.0, Culture=neutral, PublicKeyToken=..."
I'm sorry to hear you're experiencing this error when attempting to save your project!
I went ahead and opened a support case on your behalf, so our engineers can help troubleshoot the issue with you. You should hear from our team soon via e-mail.
Thank you for reaching out, and I'm sorry you're running into errors when trying to save your project!
Are you working from a local hard drive? We don't recommend working with files on a network drive as it can cause erratic behavior. If it's a local drive and syncing with a service such as OneDrive or Dropbox, it can cause a similar effect as a network drive, as Michael mentioned above.
I have had an issue for awhile the efficiency of my work is greatly affected. I am working with Articulate Support. I am just curious - I am 1 of a team of 4 and all of them have been upgraded to Windows 11. I am the only one that is having issues.
I see that my teammate Luiza was able to identify you were being affected by a known issue. Our apologies for any inconvenience this may have caused. You’re in great hands. We’ll send you an update through the support case that you created as soon as we have new information.
Ok, so I see a lot of people having this problem (as do I this evening). But what is this "known issue" and more important, how do I resolve this issue?
Sorry to hear that you are encountering a similar issue. Just to give you a background of it, using Intel 11th Generation Core series processors or later causes a memory leak that affects the performance of Storyline 360. You can reach out to our support team here to confirm if you are being affected.
We are still working on a fix, and you can check out the document below for a possible workaround that you can apply as a temporary solution.
That would have made sense if I would be using an Intel processor, but my machine is equipped with an AMD Ryzen 7 processor in combination with a NVIDIA GeForce RTX 3060 graphics card...
Anyhow, nothing was saved as it turned out... I hoped closing Articulate 360 via de task manager would give me a "recovery/autosave" file (as it normally does), but unfortunately that wasn't the case.
So, I had no other option than to do the work again and hit the save button around 1.5 million times in between. Didn't get the error again in this project so far. Weird.
If you need additional information, please let me know.
15 Replies
Also, I am getting the error message: 'The project file could not be saved. Object reference not set to an instance of an object'
Hi Adam,
Eek! Sorry, you're running into those errors (we're working on making the text there more descriptive!) but it would help to know what version/update of Storyline you're using? You can check by going to the "Help" Tab -> "About Articulate Storyline".
Also, you mentioned trying to save locally which is what we always recommend. Was the file previously saved to a network/shared drive? Have you also checked the general best practices here to prevent odd behavior that ultimately leads to file corruption?
I always try . importing a file into a new local .story file too - that often resolves any of those errors.
Hello - I have the same problem since yesterday. And it affects every project file. It has become impossible for me to save anything, even a new empty project doesn't save.
Saving to the desktop, fresh log-in or a fresh install of Storyline also didn't solve this issue.
On another machine there is no problem with the same files. Colleagues can open and save the same project files.
Most times it reads "The project could not be saved. One or more errors occurred."
Sometimes it says it could not find "System.Diagnostics.Debug. Version=4.0.0.0, Culture=neutral, PublicKeyToken=..."
Hi, Huan.
Thank you for reaching out, and great call opening a support case with our engineers! I see that you're working with Mick, so you're in great hands!
Please reach out to Mick through the case if you have additional questions.
I am getting the same error. Please advise.
This is really bad as I will lose all the work if I cannot save.
Hello, Articulate-Team.
I'm sorry to hear you're experiencing this error when attempting to save your project!
I went ahead and opened a support case on your behalf, so our engineers can help troubleshoot the issue with you. You should hear from our team soon via e-mail.
By any chance, are you running DropBox on your computer? If so, select "Pause File Sync" in DropBox then save your Story file with a new name.
I am having the same problem.
Hi, Patrick.
Thank you for reaching out, and I'm sorry you're running into errors when trying to save your project!
Are you working from a local hard drive? We don't recommend working with files on a network drive as it can cause erratic behavior. If it's a local drive and syncing with a service such as OneDrive or Dropbox, it can cause a similar effect as a network drive, as Michael mentioned above.
If this is not your scenario, please reach out through a support case so we can investigate this further.
I have had an issue for awhile the efficiency of my work is greatly affected. I am working with Articulate Support. I am just curious - I am 1 of a team of 4 and all of them have been upgraded to Windows 11. I am the only one that is having issues.
Hi Celeste,
I see that my teammate Luiza was able to identify you were being affected by a known issue. Our apologies for any inconvenience this may have caused. You’re in great hands. We’ll send you an update through the support case that you created as soon as we have new information.
Ok, so I see a lot of people having this problem (as do I this evening). But what is this "known issue" and more important, how do I resolve this issue?
Hi Kaj,
Sorry to hear that you are encountering a similar issue. Just to give you a background of it, using Intel 11th Generation Core series processors or later causes a memory leak that affects the performance of Storyline 360. You can reach out to our support team here to confirm if you are being affected.
We are still working on a fix, and you can check out the document below for a possible workaround that you can apply as a temporary solution.
Storyline: Memory Leaks When Using Machines With Intel Iris Xe Graphics
We'll post an update here as soon as we receive any news, and our apologies for any inconvenience this issue may have caused.
Hi Joe,
Thanks for the reply.
That would have made sense if I would be using an Intel processor, but my machine is equipped with an AMD Ryzen 7 processor in combination with a NVIDIA GeForce RTX 3060 graphics card...
Anyhow, nothing was saved as it turned out... I hoped closing Articulate 360 via de task manager would give me a "recovery/autosave" file (as it normally does), but unfortunately that wasn't the case.
So, I had no other option than to do the work again and hit the save button around 1.5 million times in between. Didn't get the error again in this project so far. Weird.
If you need additional information, please let me know.