Client Error Message Importing SCORM Course

Hey all, just wondering if anyone has any ideas?

Hi, Jack:

Well, according to the error log, there was an permissions error in grabbing the SCORM 1.2 API from the LMS.  This suggests to me that there might be a configuration issue with the LMS.  Does it support SCORM 1.2?  I would definitely get with whomever is responsible for administrating the LMS, starting with that question.  Then, you might try republishing your course for a later SCORM standard like 2004 and see if that doesn't fix it.

In any event, you should definitely get with the LMS tech support to begin troubleshooting.

It is most likely because your content and LMS are not in the same domain. You content is being launched from:

http://coxu.qa.cox.com/learningcontent/cox/roles/impact%20selling/index_lms.html

If the URL to the LMS does not start with:

http://coxu.qa.cox.com/

Then the content and LMS are considered to be in separate domains and won't be able to communicate via SCORM without jumping through some hoops. Note that these domains need to match EXACTLY.

I have encountered the same problem.

In my case I have the same domain for content and LMS.

My Articulate template does NOT open in a new window (as per other suggestions)

I use Plateau LMS but this situation has only occurred with an upgrade of Plateau to v6.3.5. The courses have previously worked OK without any problems.

If Articulate publishes to LMS using AICC there is no problem , but if output to Scorm 1.2 or Scorm 2004 then I get the error Unable to acquire LMS API.

If I use I.E. 8 the error log contains "Error grabbing 1.2 API Error:Permission Denied"

If I use FireFox  8 the error log says "Error: Permission denied for to call method Location.toString"

Plateau support suggest changing the findAPI routines from

theAPI = findAPI(window.opener)

to

theAPI = findAPI(top.window.opener)

or

theAPI = findAPI(window.opener.opener)

I do not know enough about Javascript to confidently do this.

Any sugeestions or has anyone else had the same problem?

Thanks

Neil

Does the version of Plateau you are using pass the compliancy test provided at http://www.adlnet.gov/capabilities/scorm#tab-learn ?

My guess is that it does not in the strict sense.

Not that is something you can do anything about in the short term but you might push them in that direction.

Hi Neil,

We're getting the same error message using an old version of Plateau. We'd like to know which folder and which file from the Articulate 1.2 publish  you found the code "theAPI." We'd like to use the suggested changes ["FindAPI(window.opener.opener)]" I've searched in a few and can't seem to locate it.

Thanks!

-Kristin

Hi Kristin

I think Articulate uses different code from what Plateau suggest is the usual SCORM API. So whereas Plateau suggest changing some Javascript routine called FindAPI,  Articulate has their routines in the \lms\SCORMFunctions.js file and the place where our code fell over was in SCORM_GrabAPI. I have tried minor changes to this code but to no avail.

I was hoping that since both Plateau and Articulate are Scorm compliant and have many users then others may have had the same problem.

By the way, a few years ago , we purchased some content from a provider (not Articulate based) which used a routine called FindAPI and although it didnt work initially,  I was able to do what Plateau suggested and got it working OK.

So like you I am a bit confused. I dont have decent Javascript skills to know what to do next. We are trying to organise some help from Plateau by someone who has also used Articulate. If we find an answer then I will let you know.

What version of Plateau are you using?

Cheers

Neil

Hi Neil,

Thanks for such a quick response. We're using a REALLY OLD version of Plateau (5.8.x) and plan to upgrade to a new LMS this year, but until we do so, we need to use what we have. I was looking in the SCORMFunctions.js file. Good to know I was in the right place. My co-worker knows a fair amount about the code and had me try a window.opener.opener fix, but to no avail. I did not try the top.window.opener option yet. Perhaps that will solve my issue...? I'll report back with any new results.

Enjoy your weekend,

-Kristin