SCORM 1.2 Suspend Data Reported Incorrectly

May 15, 2012

Hi everyone!

We've heard from a number of users that they've completed some courses that have been built using Articulate Presenter 10.  

When looking at logs on the LMS of the exchange between the courses and the LMS, it looks like suspend data is being initialized as "|".  When users exit the course and re-launch it, suspend data appears to be retrieved from the LMS and then set as "||undefined".  

There are a number of users that have been able to complete the courses without any problems.  This would suggest that it has something to do with the user's Flash Player or browser but so far we haven't been able to find any correlation.  

Has anyone else experienced this?  Does anyone know what might be causing it?

Thanks!

4 Replies
Peter Anderson

Hey guys, 

If you're experiencing issues with LMS content, I'd recommend referring to this article, which outlines common issues pertaining to viewing and tracking content in an LMS. The section on testing your course in SCORM Cloud may be especially helpful. 

Also, be sure to package your published content properly for your LMS:

Storyline:

http://community.articulate.com/tutorials/products/publishing-a-project-for-lms.aspx

Studio '09:

http://www.articulate.com/blog/publish-to-lms-with-studio-09/

If the issue persists, you might want to open a support case with your LMS provider, since they're your primary source of support for LMS tracking and reporting issues.

joe smith

Hi Atom & Adam,

I know this is an old post that you were both part of, but I am currently experiencing the same issue with one of my users.  Thousands of users have used the course and everything worked just fine, so I'm certain the issue is something to do with the user's operating environment.  He was originally using IE10.  I then had him switch to Google Chrome in hopes that it would fix the problem, but the same issue happened with the 'undefined' suspend_data field.

So my question to both of you is did you ever figure out what was causing this problem?  Was there a solution you stumbled across that fixed the issue?

Any feedback you could provide would be greatly appreciated.

Thanks,

Steven

This discussion is closed. You can start a new discussion or contact Articulate Support.