Articulate 360 Error When Setting Triggers

Thanks Alyssa,

I tried to import into a new file and received the same error. I've also gone and uninstalled / reinstalled yet still receive the same error. No luck....

Thanks for that update, Sheri. There's one more thing I'd like to check before we escalate this to the Support Engineers. I see from your video this is happening on Slide 4.2 - is that the only slide it's happening on, or all slides? If that's the only slide, there may be a corrupt object on that slide. You can identify it by deleting objects one by one until you find the culprit.

If you're seeing this on all slides, I'd like to get your file over to our Support Engineers for further troubleshooting. They're experts at this kind of thing, and you'll be in good hands. Also be sure to share your case number with me so I can follow along, as well. 

Hey Alyssa,

It happens on all slides regardless of shape. I've tried completely blank slides using the articulate provided buttons and same thing. I also just tried opening a new flie, created a button and tried to create a trigger. Same error :/

Hey Sheri - I see where you have reached out to our support team (01000020) on this issue and Cleo is testing.

After updating I started to receive the exact same error on all my projects. 

Edit: You can use the keyboard (arrow keys and tab) to navigate the trigger setup window but as soon as you click on any of the popups the error occurs. Hope that helps the team. (Sorry, I have no idea where those tickets are processed so I can't add this bit there.) 

Hey Justin - we are still working with Sheri on gathering some logs, so I don't have an update at this time. If you'd like to reach out in your own support case, we'd be happy to work with you as well so that we can understand this better. In the meantime, I will add your thoughts to the existing case as well.

Hey all- to update I had to connect with our IT team as I'm unable to get the logs needed. Hoping they will be able to share.

Justin- I've been able to work around the issue by using the tab, enter and arrow keys when I open the trigger dialog box as opposed to trying to use the mouse. Not ideal and takes some time from development, but at least I've been able to move forward with my projects.

Leslie - I've submitted case (01003200) with one of the logs I usually get. Not sure if the error report log is any different from what you are looking for.

Sheri - I'm in the same place. It is a pain and definitely slows down the process but at least we can still get some work done. :) 

Thanks so much Justin - your support engineer will let you know if they need anything further.

Thanks for sending that in, and particularly for including a copy of your .story project file, Justin!

We'll be in touch.

Hi,

The same issue occurs??? Please help us.  

Thanks for adding your voice to this problem, Alper.

Can you please click here and send us a copy of any .story project file where you have produced this error so that we can dig deeper?  Thanks!

Thank you Justin.

Actually the eror  occurs when working on any file like blank project at this time. But the error took place after editing states in last project. can it be related that?

Thanks again for the details, everyone.  It looks like we have enough information to try and debug this problem, and we're actively engaged in doing so now.  We'll keep you posted on a possible fix, and please note the temporary workaround shared above by Justin and Sheri.

Hi All,

The error occurs when pressing any combo box in Storyline. According to our error report  it's seem clearly:

<?xml version="1.0" encoding="utf-16"?>
<ErrorReport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<FirstName /> <LastName />
<EmailAddress>abc@abc.com</EmailAddress>
<MachineName>ABC-PC</MachineName>
<HardwareId>ABCD-ABCD-ABCD-ABCD-ABCD</HardwareId>
<Message>Object reference not set to an instance of an object.</Message>
<StackTrace> at Articulate.Windows.Forms.Metro.MetroComboBox.q()
at Articulate.Windows.Forms.Metro.MetroComboBox.WndProc(Message&amp; message)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message&amp; m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message&amp; m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)</StackTrace>
</ErrorReport>

Thanks for the additional information, Alper.  I'll add this to our bug report!

Sheri, Justin, and Alper:

We've found that a Windows Classic system theme on a Windows 7 computer can cause an error in the Storyline 360 trigger wizard. We're working on a fix for it now. Until the fix is ready, you can switch to an Aero or Windows Basic theme to avoid the problem. Here's how to do that.

Please let us know if this resolves the problem for you!

Thanks Justin,

I've partnered with our IT team to adjust for our team and will post here if we have any additional issues/if it doesn't work.

You guys are awesome- will you update this thread once a fix is in place?

We certainly will, Sherry.  Thanks!

I was having the same issue and the switching to windows basic worked for me.

Lost 3 dev days thou :(

Thanks for your patience David, and for confirming the resolution!

Thanks for your solution. I love Windows Classic and I am looking forward to taking your update :)

Hey all- this also happens in Replay 360 as well. I'm hoping the same resolution will fix; still waiting on our IT team to adjust the settings on our laptops.

Thanks for the additional information, Sheri.  I've shared with my team that Replay is affected as well, and the same theme switch should resolve that also.