Not tracking in the LMS

Hi Sharon,

Looks like it may be an issue with the LMS itself, but I'm not entirely sure. Have you tested your course in SCORM Cloud? This would help us determine if the issue is Articulate related or if it's on your LMS's side. If you're using AICC content please take a look at the article below for testing information:

Articulate Support - Testing AICC content at SCORM Cloud

If it appears in SCORM Cloud as well, we'd be happy to take a closer look at what might be going on.

If you can't replicate the issue in SCORM Cloud, it's probably an issue that you'd want to take to your LMS team. 

The articles here and here may also help clear up common LMS issues.

Let me know how it turns out.

Thanks!

Christine

It tracked perfectly in SCORM cloud.

My LMS person tells me the LMS doesn't support CMI interactions. What are those? What actions am I using in my course to get the error codes above?

Sharon

HI Sharon,

The following information gets communicated to an LMS by Articulate Storyline via SCORM and AICC:

• id: This is the number of the question in the quiz. It'll be in the format Question#_#. The first '#' is the question number. The second '#' is the number of the user's attempt. For example, Question5_2 would designate the user's second attempt on the fifth question.
• type: This is the type of question (True/False, Multiple Choice, Multiple Response, etc).
• student_response: This is how the user answered the question.
• correct_response: This is the correct answer for the question.
• result: This designates whether the user answered the question correctly or not.
• weighting: Articulate content does not currently utilize this item. It'll always be set to 1.
• latency: This is how long it took the user to answer the question.
• objective: Articulate content does not currently utilize this item. It'll always be set to 0.

SCORM 2004 content also communicates the question text to an LMS.

Are you including a results slide in your course? You could try creating a slide and see if that's handled by the LMS.

If you continue to have trouble with this, please go ahead and submit a support case with us. You'll be able to attach the .STORY file on the second page of the following form:

Articulate Support - Submit a Support Case

Please be sure to include a description of your issue. Please also include the URL for this thread in the form. Also, please share the case number with me. You're welcome to do so here, or in a private message. This way I can follow the progress of the case and update this thread.

Thanks again, Sharon!

Thanks, I'll submit my course. I have further information from our LMS folks:

Normal 0 false false false oNotPromoteQF /> EN-US X-NONE X-NONE MicrosoftInternetExplorer4

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman","serif";}

The updated content has beenplaced on the staging LMS environment.

Courseware launched andbookmarked but did not complete.

 

While taking the course Inoticed cmi.interaction being used by the course during the quiz. This is anunsupported function within the LMS.

These calls do not make any userside noticeable error but it is still recommended to remove these calls.

 

Also after finishing the quizwith a passing score, the course failed to properly submit the final data.

This is most likely due to theuse of putCoreSection(). I was unable to find any data on this function whensearching through the Run Time Environment documentation of SCORM 1.2 that ADLprovides. This document shows and defines all the SCORM 1.2 functions and theirproper use.  

 

Not seeing putCoreSection()makes me question if this is the correct function to be called.

LMSCommit() and commitData()were used by the course to submit this same section of data when I left thecourse before reaching the end. Those are the correct functions to use tosuccessfully submit the data to the LMS.

 

To fix this issue I wouldsuggest a double check and republishing of the content.

If you are unaware of how tochange this settings please contact your developer/content development programsupport. They should be able to assist you with these changes.

WedMay 1 09:33:42 EDT 2013 [DEBUG]: PlateauSCORMAPI commitData() called

WedMay 1 09:33:42 EDT 2013 [DEBUG]: PlateauSCORMAPI sendHACPMessage, props =={command: PUTPARAM; version: 2.0; session_id: C3324M1081S; AICC_Data:[CORE]LESSON_STATUS=passed,suspendSCORE=80,100,0[CORE_LESSON]2Qb_40a0d0l0m0r070y0b0e0x050q080g0i0s0n0u0o0w090c0f0k0v0p060j0h0t0~2G2~2C21001u11~2r20101101111012110131101411015110161101711018110191101a1101b1101c1101d1101e1101f1101g1101h1101i1101j1101k1101l1101m1101n1101o1101p1101q1101r1101s1101t1101u1100~218a02Z1214000~221a9101001a1a36z0jfDg30118_default2Agqn02A7fe720118_default000000010~2A2a95010210103ge1~2q1jDi3000I2118_default6Ai0012jDi2000n3118_defaultjDi300000118_defaultfDg20118_default6Ai00m1O0n0238fe720118_default000o03px0fe770178_default0000010~2H1a9401001a1a3Ke1BfDg30118_default6Ai00C16Ai00s26Ai00S0Nn02kafe720118_default0000n02etfe770178_default0000010~2d1a9101001a1a3ie1u6Ai00S0jDi300000118_default2Agqn02P7fe720118_default000000010~221a9101001a1a3C01jfDg30118_default2Agqn02R6fe720118_default00000001000; }

Wed May 1 09:33:42 EDT 2013 [DEBUG]:PlateauSCORMAPI setError(101, diagnostic == 'HACP error 401: putCoreSection()failed')

Wed May 1 09:33:42 EDT 2013 [DEBUG]:PlateauSCORMAPI ERROR: 101 - General Exception (HACP error 401:putCoreSection() failed)

Good morning Sharon,

I was able to find your case (#00331779 for my reference). Looks like Sid is working on the case and he's requested some additional information. 

Just wanted to check in with you and make sure you've received his email. If you're unable to find it, please try checking your spam folder. If you still can't find it, just let me know. I'd be happy to send it out to you again.

Thanks very much!