Scorm 1.2 Error Handling in Captivate 4

Report · Aug 17, 2010

We have been using Captivate 4 for SCORM courses in a Moodle LMS (1.9.8) implementation. All of our users run Windows XP SP3, IE 6, and have McAfee installed on their systems. We have been having 1/5 people who take the Captivate courses never connect to the API and thus no data is written except for a start.time which is seperate from the SCORM communication. I was wondering if there was anyway we could have a javascript error appear whenever a user does not connect to the LMS or API correctly. I know this is common in other implementations of SCORM, but I cannot figure out how to add it to Captivate since the calls are all made in ActionScript as far as I know.

I have been looking for common threads and have had no real luck.

As a side note, the users who aren't getting written to the database are users who previously took Captive 4 courses in the same LMS and had no issues even when using the same PC on the same day. If anyone knows why this could be happening or has any suggestions or how to discover the error please help, we have been dealing with this issue for far to long and it is quickly becoming a permanent headache...

Thanks!

Sean

Report · Aug 18, 2010

All (? or most) SCORM calls for published CP projects are contained in an external file. In CP4 it's "scorm_support.js".

So you could likely, if you have any JS expertise or resources, look at that...see where it attempts to connect to the API and customize it to throw an alert if it fails?

Erik