I am working on a SL file, translating a previously published course into a new language. I went to save the file today and received the following error:
"GDI+ could not load image from file. Cache count: 99. Total undisposed cache objects: 170"
What does this error mean and how can I get it to go away?!
Hi Melissa! Happy to help you get back up and running.
First, are you able to save the file at all? If not, try doing a Save As to save the file with a different name and to a different location on your local hard drive.
If you're still unable to save and close the file, reach out to our Support Team here. They'll gather more information about your system and help you with next steps!
Hi Melissa! Thanks for opening a case, and I see you're already working through this with Renz. I hope you're able to locate a temporary file using the steps he shared. Keep us posted!
Hi Leslie, I am not able to import my file into a new one since I can't save it in the first place to do so. It only allows closed files to import into new files. Do you have any other suggestions?
Sorry you're still at this roadblock. This is an excellent opportunity for our Support team to jump in and lend a hand! I opened a case on your behalf, so look out for an email with new approaches to try from our engineers. I'll follow along so I can update this discussion with our findings!
I’m trying to save my project but I keep getting this error message "The Project File could not be saved. GDI+ Could not load image from file. Cache count:99. Total undisposed cache objects:427
I was finally able to copy everything into a new storyline file and save
it. It was really weird.
I never had that happen before.
What is the reason so I can avoid that in the future.
dawn
Dawn DeVillers
Director of Production at KMI Learning, Inc.
Phone: 614.224.0664 ext.105
Cell: 614.589.8651
fax: 614.224.0665
330 West Spring St #320
Columbus, OH 43215
[image: Learning that builds business]
[image: Join KMI Learning on Youtube]
[image:
Find KMI Learning on Google Plus]
[image: Follow KMI Learning
on Twitter] [image: Like KMI Learning
on Facebook] [image: Connect with
KMI Learning on Linkedin]
Thanks for reaching back out. I'm going to let Renz, in your support case, know that you're still running into difficulty with this so you can continue working together.
Hi Dawn,
Thanks for popping back in with an update and letting us know that it's working for you now.
I've shared your latest with Peter in your support case as well.
We have not tracked down the cause of this error yet, but this conversation is attached so that we can share any updates with you here.
It looks like your email signature came through when you replied via email. You can remove that if needed by clicking ‘Edit’ beneath your response. Here’s a quick Peek video if you need help.
We have multiple people working in Storyline files where this is happening regularly for the last month.
We are constantly opening new projects and then importing files to fix the issue however this hugely time consuming due to the detailed setup of our modules.
Is there and ETA for this fix? Or a version we can roll back to?
My big factor was saving the newly imported storyline file in a new location. It seemed once I saved it someplace completely different from where the other file was, I stopped seeing the issue.
I was having the same issue too for a long time on just one file. After working with Renz, I completely uninstalled ALL articulate, then Renz had me run a "clean up" program, then reinstall Articulate apps. (note: there was also several reboots in there too!)
Once I reinstalled, I imported into a new file and saved it somewhere else on my C Drive. A completely new folder. And that seemed to do the trick. It took all-in-all, about 3 hours. But it worked.
I would try and get with an Articulate team member to have them give you instructions to see if that might work for you.
I feel your pain! Hang in there. Hope you find a solution quickly. Really knocks the wind out of a project when this happens!
I'm so sorry you've come across this error. Our team is looking into its cause, and we'll keep this discussion posted on any new developments!
As we continue to investigate, I echo Melissa in that our Support Engineers would be happy to help. Click here to start a conversation with the team. They'll do a deep dive and let you know what they find!
We just released another update of Storyline 360. That release includes a fix for the issue where you would see a “The project file could not be saved. GDI+ could not load image from file” error when saving a file.
23 Replies
Hi Melissa! Happy to help you get back up and running.
First, are you able to save the file at all? If not, try doing a Save As to save the file with a different name and to a different location on your local hard drive.
If you're still unable to save and close the file, reach out to our Support Team here. They'll gather more information about your system and help you with next steps!
Thanks. I tried to save as, and got a different error "The project file could not be saved. One or more errors occurred."
I will reach out to the support team. Thanks!
Hi Melissa! Thanks for opening a case, and I see you're already working through this with Renz. I hope you're able to locate a temporary file using the steps he shared. Keep us posted!
Hi Melissa,
I'm currently haven't the same problem with my file, were you able to get this resolved?
Thanks for reaching out and letting us know that you're running into a similar issue.
I took a quick glance and it looks like she was able to import the file into a new one and proceed.
Try that and let us know if you need further assistance.
Hi Leslie, I am not able to import my file into a new one since I can't save it in the first place to do so. It only allows closed files to import into new files. Do you have any other suggestions?
Hello there!
Sorry you're still at this roadblock. This is an excellent opportunity for our Support team to jump in and lend a hand! I opened a case on your behalf, so look out for an email with new approaches to try from our engineers. I'll follow along so I can update this discussion with our findings!
I’m trying to save my project but I keep getting this error message "The Project File could not be saved. GDI+ Could not load image from file. Cache count:99. Total undisposed cache objects:427
Thanks for reaching out, Vilma! We're seeing the same problem, and our team is looking into a solution.
As soon as we know more, we'll pass the news along to you!
I need help NOW!!!! i get the same error and I can not save it. My project is due today!
what do i do?
dawn
Hi Dawn,
Thanks for reaching out.
Were you able to try doing a Save As to save the file with a different name and to a different location on your local hard drive?
I've opened up a support case on your behalf as well so that you can easily reply and work 1:1 with a support engineer if you need further assistance.
I still am having issues with this file and the same error.
I can save into a new storyline file however, it gives me the same error.
Am interested in what might work to fix this file.
I was finally able to copy everything into a new storyline file and save
it. It was really weird.
I never had that happen before.
What is the reason so I can avoid that in the future.
dawn
Dawn DeVillers
Director of Production at KMI Learning, Inc.
Phone: 614.224.0664 ext.105
Cell: 614.589.8651
fax: 614.224.0665
330 West Spring St #320
Columbus, OH 43215
[image: Learning that builds business]
[image: Join KMI Learning on Youtube]
[image:
Find KMI Learning on Google Plus]
[image: Follow KMI Learning
on Twitter] [image: Like KMI Learning
on Facebook] [image: Connect with
KMI Learning on Linkedin]
Hi Melissa,
Thanks for reaching back out. I'm going to let Renz, in your support case, know that you're still running into difficulty with this so you can continue working together.
Hi Dawn,
Thanks for popping back in with an update and letting us know that it's working for you now.
I've shared your latest with Peter in your support case as well.
We have not tracked down the cause of this error yet, but this conversation is attached so that we can share any updates with you here.
It looks like your email signature came through when you replied via email. You can remove that if needed by clicking ‘Edit’ beneath your response. Here’s a quick Peek video if you need help.
What is the update with this issue???
We have multiple people working in Storyline files where this is happening regularly for the last month.
We are constantly opening new projects and then importing files to fix the issue however this hugely time consuming due to the detailed setup of our modules.
Is there and ETA for this fix? Or a version we can roll back to?
Amy,
I copy and paste the slides into another storyline and made sure the files I am using are on my C drive. so far it is working ok for me.
Dawn
Hi Amy,
Thanks for reaching out and letting us know that you're running into an issue as well.
Importing slides into a new project has been alleviating the issue in most of the instances of this error for the users that have reached out.
I've not seen any users request or mention rolling back versions, but users are able to install previous versions on their own.
We are working on this issue and this conversation is attached so that we can update you as soon as we have additional information to share.
My big factor was saving the newly imported storyline file in a new location. It seemed once I saved it someplace completely different from where the other file was, I stopped seeing the issue.
We always work with files on our C drive due to other issues surrounding locality.
Just is a painful process.
Would love to know as soon as possible, as this just keeps happening to me.
I've seriously had it happen 8 times today.
Very frustrating.
In fact even after importing and then resaving I still get the error.
Amy,
I was having the same issue too for a long time on just one file. After working with Renz, I completely uninstalled ALL articulate, then Renz had me run a "clean up" program, then reinstall Articulate apps. (note: there was also several reboots in there too!)
Once I reinstalled, I imported into a new file and saved it somewhere else on my C Drive. A completely new folder. And that seemed to do the trick. It took all-in-all, about 3 hours. But it worked.
I would try and get with an Articulate team member to have them give you instructions to see if that might work for you.
I feel your pain! Hang in there. Hope you find a solution quickly. Really knocks the wind out of a project when this happens!
Hi there, Amy!
I'm so sorry you've come across this error. Our team is looking into its cause, and we'll keep this discussion posted on any new developments!
As we continue to investigate, I echo Melissa in that our Support Engineers would be happy to help. Click here to start a conversation with the team. They'll do a deep dive and let you know what they find!
Good news, everyone!
We just released another update of Storyline 360. That release includes a fix for the issue where you would see a “The project file could not be saved. GDI+ could not load image from file” error when saving a file.
To take advantage of this fix, follow these steps to update your software. Let me know if you have any questions!
This discussion is closed. You can start a new discussion or contact Articulate Support.