I'm sorry you've run into this error. The best way for us to diagnose it and determine how to help you fix it is to have you work with our Support Engineers, and they can take a look at what's happening on your end.
I went ahead and started a Support case for you since I didn't see one already opened for this issue. You'll receive an email from our team shortly.
Thanks Ashley. If we could reproduce this error you can be sure we would open a case. Unfortunately, it is completely unpredictable and may not happen again for days.
That's why error messages that include diagnostic information are so important.
I can appreciate how frustrating it is when this error is inconsistent and without any additional diagnostic info. That's one of the reasons I'm suggesting working with our Support Engineers directly versus posting in ELH.
Working with our Support engineers via a case is the best way to troubleshoot that type of error message and to find a cause, as they can help with some more steps to gather diagnostics. John has been assigned to your case and will be in touch soon with some next steps!
Sharing here in ELH is a great way to gather community input and assistance on technical, design and how to issues. The larger issues of Storyline not working is often something the ELH staff will engage the help of our Support Engineers on, so I'd hate to think that our delay in opening a case for you would impact you receiving help quicker!
I'll follow along in your case with John too so that I can share any updates here.
4 Replies
Hi Sam,
I'm sorry you've run into this error. The best way for us to diagnose it and determine how to help you fix it is to have you work with our Support Engineers, and they can take a look at what's happening on your end.
I went ahead and started a Support case for you since I didn't see one already opened for this issue. You'll receive an email from our team shortly.
Thanks!
Thanks Ashley. If we could reproduce this error you can be sure we would open a case. Unfortunately, it is completely unpredictable and may not happen again for days.
That's why error messages that include diagnostic information are so important.
Sam
Hi Sam,
I can appreciate how frustrating it is when this error is inconsistent and without any additional diagnostic info. That's one of the reasons I'm suggesting working with our Support Engineers directly versus posting in ELH.
Working with our Support engineers via a case is the best way to troubleshoot that type of error message and to find a cause, as they can help with some more steps to gather diagnostics. John has been assigned to your case and will be in touch soon with some next steps!
Sharing here in ELH is a great way to gather community input and assistance on technical, design and how to issues. The larger issues of Storyline not working is often something the ELH staff will engage the help of our Support Engineers on, so I'd hate to think that our delay in opening a case for you would impact you receiving help quicker!
I'll follow along in your case with John too so that I can share any updates here.
Ran today's update and we're getting the "Close non-essential applications and save your project file." frequently.
Are other users seeing this error?
This discussion is closed. You can start a new discussion or contact Articulate Support.