The Secret to LMS Debugging

Unraveling the chatter between your learning management system (LMS) and the content you’ve produced in Articulate Storyline or Articulate Studio can be frustrating.

What should you do when learners do one thing but the LMS says they’ve done something else? How do you handle it when the score or status isn’t recorded as you’d expect or when the course doesn’t suspend or resume the way you’d like?

An important first step is to test your project in SCORM Cloud, but what should you do when your course works properly in SCORM Cloud but not in your LMS?

Enter LMS debug mode, an easy way to see exactly what your AICC/SCORM content is sending to the LMS and how the LMS is responding. By default, LMS debug mode is disabled in your published output, but it’s easy to turn on.

Watch this video to learn how to generate a debug log for troubleshooting purposes or follow the instructions below.

Step 1: Locate Your Published Configuration.js File

First, publish your course for LMS (Storyline, Presenter, Quizmaker, Engage), then click Open on the publish success window.

Click Open in Publish Success Window

Open the lms folder.

Open the lms folder

And find the Configuration.js file.

Find the configuration.js file

Step 2: Enable Debug Mode

Open Configuration.js in a text editor, such as Notepad, and locate the following line:

var SHOW_DEBUG_ON_LAUNCH = false;

Change this value to true.

Change the value to true

Save and close Configuration.js.

Step 3: Zip Your Content and Upload It to Your LMS

Return to the publish success window and click the Zip button. This creates a zipped file of the published output in the same location where you published your course. Upload this zipped file to your LMS.

Upload this zipped file to your LMS

Step 4: Launch Your Course and Save the Debug Log

When you launch the content in your LMS, it'll open in one window, and the debug log will open in another.

Debug log open in second window

After reproducing the issue you're troubleshooting, copy and paste the text from the debug window into a document for further investigation.

Step 5: Review the Debug Log

Your LMS provider is most qualified to interpret the contents of your debug log, so we recommend opening a support case with them. However, if you’re familiar with AICC or SCORM, feel free to take a look at the log. Sometimes, an issue is obvious and jumps off the page.

If neither you nor your LMS provider are able to spot the cause of the problem, submit a case to Articulate and we’ll take a look. Be sure to include a copy of your project file so we can reproduce the problem.

If you have any other suggestions on troubleshooting an LMS, share your thoughts with us and other community members in the comments below.

And for more helpful advice on everything related to e-learning, be sure to follow us on Twitter and come back to E-Learning Heroes regularly.

6 Comments