Storyline crashes on preview or publish

every time I try to preview or publish a certain .story, Storyline crashes and I get an error report:

<?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>redacted</EmailAddress>
<MachineName>redacted</MachineName>
<HardwareId>redacted</HardwareId>
<Message>TimeSpan does not accept floating point Not-a-Number values.</Message>
<StackTrace> at System.TimeSpan.Interval(Double value, Int32 scale)
at gf.g()
at gf..ctor(Shape A_0)
at Articulate.Design.Shape.AddPlayerEventsCore(IPlayerService service, IPlayerTimeline timeLine, bwStageObject stageObj)
at Articulate.Design.Shape.Articulate.Player.IPlayerShape.AddPlayerEvents(IPlayerService service, IPlayerTimeline timeLine, bwStageObject stageObj)
at Articulate.Player.PlayerContentPublisher.a(IEnumerable`1 A_0, bwSlideBase A_1)
at Articulate.Player.PlayerContentPublisher.CreateSlideObject(IPlayerSlide slide, bwISlideContainer sceneobj)
at Articulate.Player.PlayerContentPublisher.CreateBridgewaterSlide(PlayerWriterSettings settings, IPlayerSlide slide, bwISlideContainer sceneobj)
at Articulate.Player.PlayerContentPublisher.CreateContentScenes(PlayerWriterSettings settings, IPlayerContentProvider contentProvider)
at Articulate.Player.PlayerWriter.WriteContent(IPlayerContentProvider contentProvider, Nullable`1 merged)
at Articulate.Player.PlayerWriter.Write(IPlayerContentProvider contentProvider)
at Articulate.Design.Publish.TargetContext.PublishBackgroundWorker.OnDoWork(DoWorkEventArgs e)
at Articulate.ComponentModel.STABackgroundWorker.a(Object A_0)</StackTrace>
</ErrorReport>

any idea on how to fix? thanks, Steve.

9 Replies
Alyssa Gomez

Yikes! That's definitely not supposed to happen, so let's see if we can straighten this out. Since you said that this happens only with a certain file, we can assume it's not an issue with your software but rather with the file itself. Would you mind sending your file to our support engineers here so we can test it? 

Katie (Gokhshteyn) Riggio

Sorry you're also at this roadblock, Monica. Happy to help!

Looking at Steve's case: My teammate, Miker, found a corrupt object on a slide that caused Storyline's crash. Do you experience this problem on a specific slide or with multiple ones?

Let us know how the importing process goes! If you're still stuck, we're ready to help! 

Monica Jackson

Katie, 

Thanks for the suggestions. I imported the SL file into a new SL file. I have four scenes and less than 20 slides. I was able to preview the first scene. Upon attempting to preview the second scene, SL crashed. I'm going to attempt to preview each slide in that scene, to determine if I can isolate the problematic slide. Hopefully, it won't be too painstaking and I can recreate the slide that is "giving me the blues" :-). Thanks again!

Katie (Gokhshteyn) Riggio

Thanks for the update, Monica!

It sounds like there's a corrupt object in the second scene. You can identify it by deleting objects one by one until you find the culprit.

It can be a laborious process – especially when there are a lot of slides – so don't hesitate to reach out to us for help! With your permission, we'll help you troubleshoot your .story file and will delete it once we nail down that culprit. 

Monica Jackson

Katie,
Yes, that is what I did. The problem was a table on a slide in the second scene. So, I deleted and recreated. It wasn't too painful to locate. I just needed to know where to start to locate the issue. The first approach was to try to preview each scene. If the scene did not preview, then I knew the problem was in a particular scene. Thankfully, it was only one slide and one object.

Thanks again!

Brian Njue

<?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">
<UserId>auth0|5c7f96bdc5df09359d5eaac2</UserId>
<HardwareId>WF38U-AUGQJ-TJ667-139RP-3TVVU</HardwareId>
<Message>Specified argument was out of the range of valid values.
Parameter name: direction</Message>
<StackTrace> at PointF s.e(IAnimatable A_0, Direction A_1, bool A_2, int A_3)
at bwVarPoint s.g(IAnimatable A_0, Direction A_1, bool A_2, int A_3)
at bwVarPoint af.e(IAnimatable A_0)
at bwPositionSegment af.g(IAnimatable A_0)
at bwPositionSegment af.h(IAnimatable A_0, Direction A_1)
at bwTweenPosition af.u(IAnimatable A_0)
at bwAnimation af.s(IAnimatable A_0)
at void u.Animate(IAnimatable animatable)
at string Articulate.Design.Animations.ShapeAnimations.a(bwStageObject A_0, string A_1, Nullable&lt;TimeSpan&gt; A_2)
at void Articulate.Design.Shape.ai(bwStageObject A_0)
at void Articulate.Design.Shape.Articulate.Player.IPlayerShape.AddAnimations(IPlayerService service, bwStageObject stageObj)
at void Articulate.Player.PlayerContentPublisher.a(IEnumerable&lt;IPlayerShape&gt; A_0, bwSlideBase A_1)
at bwSlide Articulate.Player.PlayerContentPublisher.CreateSlideObject(IPlayerSlide slide, bwISlideContainer sceneobj)
at void Articulate.Player.PlayerContentPublisher.CreateBridgewaterSlide(PlayerWriterSettings settings, IPlayerSlide slide, bwISlideContainer sceneobj)
at bool Articulate.Player.PlayerContentPublisher.CreateContentScenes(PlayerWriterSettings settings, IPlayerContentProvider contentProvider)
at bwContent Articulate.Player.PlayerWriter.WriteContent(IPlayerContentProvider contentProvider)
at bool Articulate.Player.PlayerWriter.Write(IPlayerContentProvider contentProvider)
at void nr.n()
at void Articulate.Design.Publish.TargetContext+PublishBackgroundWorker.OnDoWork(DoWorkEventArgs e)
at void Articulate.ComponentModel.STABackgroundWorker.a(object A_0)</StackTrace>
</ErrorReport>

 

Even after importing to different SL files, this still comes up. This seems like a commonly occuring problem.

Vincent Scoma

Hey Brian,

I am sorry that you are hitting this snag!

Does this issue seem to happen with one specific course? If so,  with your permission, I'd like to take a look at your project file to investigate what's happening. You can share it publicly here, or share it privately with our Support Engineers here. Either way, we'll let you know our findings and will delete it after having a closer look!