Skip to main content
MichaelStephens
Legend
January 20, 2017
Question

Troubleshooting a published training

  • January 20, 2017
  • 1 reply
  • 279 views

Before publishing a captivate file to Cornerstone OnDemand, which my organization uses for distributing SCORM trainings, I always conduct a lot of testing across multiple operating systems and browsers to make sure trainings work correctly after I upload them to our own internet server. This week we’re receiving word that a random trainees around the state are experiencing an issue with one training that’s been fine for everyone for over a year.

The issue is that half-way through, the audio in the timeline for different slides aren't playing. Closing their browser and re-opening the training in CSOD will then play the audio for that slide, but a few slides later the same thing occurs. After a few more times of closing/opening the browser the audio will work perfectly for the rest of the training.

To investigate the issue I’ve launched the training from CSOD, opened the program Fiddler so I can monitor all the HTTPS traffic the browser is receiving and sending, and then went through the whole thing. Fortunately/unfortunately, the audio glitch never occurred and I didn’t see anything in the Fiddler logs that showed anything unusual.

I know that the problem the trainees are experiencing could be with the CSOD servers, the path the internet traffic is taking, the speed and quality of the trainees internet connection, if they’re on a LAN or Wi-Fi, and/or something with the trainees computers. So, before I submit a ticket to CSOD to have them look into the problem, something which I really don’t have much hope for based on past experience, is there anything else that I can do in order to figure out where the problem is occurring?

    This topic has been closed for replies.

    1 reply

    RodWard
    Community Expert
    Community Expert
    January 20, 2017

    Make a list of all trainees that report the issue and find out:

    • What their computer specs are.
    • Whether they were using a mobile device and if so what its specs are.
    • Which browser and version of it they were using.
    • What time of day this occurred for them.

    Then you should have some good intel to work from.  You may see a pattern.

    MichaelStephens
    Legend
    January 25, 2017

    Unfortunately the trainees aren't very tech savvy and it's difficult to get accurate information from them. However, the one person who was able to respond with any info did say they used Internet Explorer and were on a WiFi connection, both things I had a suspicion may be true. I recall a year ago when we were testing this online training that someone said they had somewhat of a similar problem but I couldn't reproduce it and since they were located in another city I couldn't see it occurring. However, they were also using IE, which I did test out, but it's possible they were using WiFi at the time which I didn't think to test for.

    So it looks like I'll be doing some testing of the training using IE and a WiFi connection. Fortunately Fiddler will allow me to capture all the HTTPS traffic so I can see exactly what the browser is accessing the whole time and how long things take to load.

    Something I am wondering about is if there are any known issues regarding IE and Captivate files published to HTML5. The other people that were testing out the training were using Chrome and FireFox so I didn't know if there are any connections in this regard.

    RodWard
    Community Expert
    Community Expert
    January 25, 2017

    There could be issues if the learner is using an older version of IE.  Version 8 is NOT HTML5 compliant.  IE9 is marginal.  If your users are on IE versions prior to IE11 I would be suggesting they update and test again.  If they have another browser on their system (e.g. Chrome) ask them to test on that.  If the issue disappears entirely then it's probably the browser rather than their bandwidth that is causing it.  If they still have the same issue on a current version of Chrome then the bandwidth could be the issue.