I'm sorry to hear you're running into this error! First, be sure your file is saved to your local hard drive. Working from a network or shared drive is risky, so it's best to work from your C: drive to protect your files.
Also, try copying the slides from the original file into a new file, a few at a time. You'll want to save the new file to your local drive between each copy and paste. Let me know if that solves it!
Thank you for reaching out and sharing that you are experiencing a similar issue.
It looks like Sagar was able to reach out to our support team directly as Ren advised above, but we did not hear back from him, so I do not have an update to provide.
Are you seeing the same error?
Are you able to do a Save As and save using a different name?
I have just run into this problem myself - already have a Case #02813490 (Mark Glino) unresolved for other another issue - and importing into a new project multiple times has not resolved anything.
I appreciate you reaching out, and I'm sorry you're experiencing this error so often. I do not see a standard solution, so I'd recommend working directly with one of our support engineers as the next step.
I've opened a support case on your behalf, so one of my teammates will be in touch shortly via email!
I continue to get this error and it causes a lot of frustration. I don't see anything here that helps me fix this problem. I don't even know what is meant by a nullable object. I didn't have this problem until I started using master slides. Please advise.
I'd like to connect you with one of our support engineers, so I went ahead and opened a case on your behalf. You should hear from our team soon via e-mail.
I keep getting this error too. It costs me a lot of time when I lose work like this and have to start over from my last save. And the staff responses on here aren't helpful at all.
I'm having the same issue. I'm not sure why support cannot post whatever resolution they came to on this forum. It would be very helpful to not have to have everyone have to open a ticket every time they have this particular issue.
I really love Storyline. I've been using it for as long as it's been around. What I don't like is a thread like this where dozens of people are having the same issue and told to go to support desk. If there is a common issue and presumably a common solution, why can't you just post what you think will fix it. I'm likely to miss all of the work I've put into this waiting on the help desk to get back to me 2 days later and of course I can't reboot my computer or use Storyline until it's resolved. :(
Thanks for asking out about this! After looking through some similar cases, it looks like support's solutions aren't exactly the same per user. So a blanket solution wouldn't really work here. If you'd like to open a support case, you can do so using the link below or I can do it for you. We would love to get things on track for you!
17 Replies
Hi Sagar,
I'm sorry to hear you're running into this error! First, be sure your file is saved to your local hard drive. Working from a network or shared drive is risky, so it's best to work from your C: drive to protect your files.
Also, try copying the slides from the original file into a new file, a few at a time. You'll want to save the new file to your local drive between each copy and paste. Let me know if that solves it!
If not, connect with a support engineer, and they can dig into this error with you!
This does not resolve the issue. I have saved local, reduced number of scenes. Noting seems to help :(
Hi Metro Training - ML,
Thank you for reaching out and sharing that you are experiencing a similar issue.
It looks like Sagar was able to reach out to our support team directly as Ren advised above, but we did not hear back from him, so I do not have an update to provide.
I have just run into this problem myself - already have a Case #02813490 (Mark Glino) unresolved for other another issue - and importing into a new project multiple times has not resolved anything.
I have been getting that error too. It happens so often i have 3 different backup copies all saved on my C Drive as is it master file.
Is there any solution?
Hello Alison,
I appreciate you reaching out, and I'm sorry you're experiencing this error so often. I do not see a standard solution, so I'd recommend working directly with one of our support engineers as the next step.
I've opened a support case on your behalf, so one of my teammates will be in touch shortly via email!
Hi There,
Getting the same problem. Did you find the solution?
Hi, Katherine.
Thank you for opening a support case! I see you're working with Cleo, so you're in great hands!
Please reach out through the case if you have additional questions.
I continue to get this error and it causes a lot of frustration. I don't see anything here that helps me fix this problem. I don't even know what is meant by a nullable object. I didn't have this problem until I started using master slides. Please advise.
Hi, Leldon.
I'm sorry to hear you're experiencing this error!
I'd like to connect you with one of our support engineers, so I went ahead and opened a case on your behalf. You should hear from our team soon via e-mail.
I keep getting this error too. It costs me a lot of time when I lose work like this and have to start over from my last save. And the staff responses on here aren't helpful at all.
the errors are hopefully documented in the log files
open in windows file explorer
%LocalAppData%/Articulate/360/Logs/
-> Storyline_STABLE_yyyymmdd_hhmmss.log
send these files to articulate in a support case
I'm having the same issue. I'm not sure why support cannot post whatever resolution they came to on this forum. It would be very helpful to not have to have everyone have to open a ticket every time they have this particular issue.
really the same error "Nullable ..." ?
if not, post a screenshot of the error message
Here's how I fixed it:
Save as OriginalFileName_1 in my downloads folder.
Close the file.
Re-open the new _1 file.
Save as OriginalFileName on P drive.
That worked to save and to publish!
I really love Storyline. I've been using it for as long as it's been around. What I don't like is a thread like this where dozens of people are having the same issue and told to go to support desk. If there is a common issue and presumably a common solution, why can't you just post what you think will fix it. I'm likely to miss all of the work I've put into this waiting on the help desk to get back to me 2 days later and of course I can't reboot my computer or use Storyline until it's resolved. :(
Hi James,
Thanks for asking out about this! After looking through some similar cases, it looks like support's solutions aren't exactly the same per user. So a blanket solution wouldn't really work here. If you'd like to open a support case, you can do so using the link below or I can do it for you. We would love to get things on track for you!