LMS issue - "Error - unable to acquire LMS API"

Hi

I am getting an error when I run index_lms.html locally on my machine (also my client is getting it on their LMS):

  • Error - unable to acquire LMS API, content may not play properly and results may not be recorded. Please contact technical support.

This doesn't happen when I run player.html from the same folder. What could it be? I found an article saying this is due to creating a "launcher.html" file, but I have created no such file (the box is unchecked in publish options)... The only two files in there are index_lms.html and player.html.

Many thanks

Sasha

44 Replies
Amaia Quesada

Hello,

I am having a bit of a similar issue.

I used to have my scorm file in scorm 1.2 format on our LMS, however the LMS specialist advised that if there is a lot of interaction it is better to publish it at scorm 2004 3rd edition in regards to the suspend_data.

The LMS would play the scorm 1.2 fine and now I am getting the error (see attachment error) and when I click on OK then I get a new window (see attachment error2).

The LMS specialist told me that he has seen a similar case before and that the problem was that the SCORM object was generated with the underlying assumption that it plays in a full page, which is not the case in "Inline" or "Lightbox" visualizations that I'm using, however not even the play in new window or full screen seem to work.

This did not seem to be an issue when using the SCORM 1.2 format. 
I run a test in scormcloud and with SCORM 1.2, I can complete the course although it says "success: unknown" and with SCORM 2004, I can complete the course too but it states "success: failed"

I see Andrea in a post above said it was solved when setting the slides to "reset to initial state" but I really do not want that in my course.

I changed the name of my file and it now seems to run smoothly on the LMS but it still sounds all very weird. Why would the name influence the behaviour?

Can you advice what to do?

Attached also the scorm 2004 3rd edition file.

Thanks in advance!

Leslie McKerchie

Hello Amaia!

Sorry to hear that you experienced difficulty with your file.

It sounds like it may be working as expected now?

Your file name can certainly come in to play: too long, special characters, accents, symbols, or even spaces. 

Check out this article on preventing file corruption, which has a specific section related to file names.

Heather Penningroth

I'm having a similar problem - but we only get the error when we run the course through our Single Sign On (SailPoint) on an iPad. We do not get the error when we use laptops or connect directly to the company network. I tried republishing , renaming, reversioning, and I also unchecked the "Launch player in new window" checkbox - still get the error.

Heather Penningroth

Well - the lesson was created in Storyline 2 and upgraded to Storyline 3. Published with SCORM 2004 HTML5/Flash - but we have other lessons that are still the Storyline 2 version giving us the same problem. I'm using an iPad Pro and Safari.

I'm avoiding going the  Articulate Mobile Player app route because it looks like it doesn't talk with LMS for tracking? 

Ashley Terwilliger

Hi Heather,

It may be the SSO that is not properly passing credentials and access from your iPad, but a good way to test that it's not the course as a whole is to upload to another environment. SCORM Cloud would be an easy one to use with your LMS published content, or if you wanted to test in a Web server environment upload to Tempshare.

Ashley Terwilliger

Hi Jason,

Are they unable to give you access to the original files, before publishing? Do you know what version/update it was published with? 

I don't know of any ways to edit it in the published output, as that's not something we can offer help on, but if anyone in the community does I hope they're able to share here. 

Leslie McKerchie

Hi Jason,

Thanks for reaching out and letting us know that you're having an issue viewing your course with Chrome and Edge.

It looks like the original issue posted here happened when the user viewed the published output locally.

  • Are you viewing a link from your LMS when experiencing the issue? 
  • What is the error that you are seeing?
Cheryl Powers

Sasha this thread is 7 years old but still a current issue presenting itself when IT rolled out more laptops running windows 10 with default browser Edge, no flash or java support.  I would like to have a better understanding of your previous share regarding the javascript  64bit/32 bit.  Unlike more recent replies below, the Storyline 360 content is not configured to launch in a new window because the SuccessFactors LMS software already automatically launches content in a new browser window.  I should mention that we did have difficulties with this course when we launched it after publishing in scorm 2004 so we went down to 1.2 and it was fine until Edge.

Sasha Scott

Hi Cheryl

This post was about Articulate Presenter rather than Storyline. My client had an issue with a recent update to the 64-bit Flash player in 2011 (Internet Explorer 9), before Storyline and Edge came along and before Flash player disappeared. If I remember, I think it was to do with intranet security settings blocking Flash messages because the player had just been updated and wasn't recognised or flagged as safe (something like that anyway), but the issue probably wouldn't be relevant today.

Sorry I can't be of more assistance.

Larisa Bolgova

Hello! 

Some of our customers get the following error:

Error - unable to acquire LMS API, content may not play properly and results may not be recorded. Please contact technical support.

The error is intermittent. Sometimes clearing cache and changing browser settings helps, but some customers cannot access the learning materials at all. 

What is the possible reason of this?
We use StoryLine 360.

Thanks,
Larisa

Luke Sochacki

All, 

I had this issue recently and put a ticket into CornerStone, our LMS provider, to find out what was going on. Here's what happened in our case:

1. We published the course in 2016 as a SCORM 1.2 course

2. We made changes to the course in 2019, and replaced the publication file with the new course, which was published in SCORM 2004 (3rd Edition)

3. The LMS did not like this, and threw this error because of it. Once we found this our from CornerStone, we replaced the publication file again as a SCORM 1.2 course, and have had no issues since

Hope this helps!

Luke

Luke Sochacki

All, 

I had this issue recently and put a ticket into CornerStone, our LMS provider, to find out what was going on. Here's what happened in our case:

1. We published the course in 2016 as a SCORM 1.2 course

2. We made changes to the course in 2019, and replaced the publication file with the new course, which was published in SCORM 2004 (3rd Edition)

3. The LMS did not like this, and threw this error because of it. Once we found this our from CornerStone, we replaced the publication file again as a SCORM 1.2 course, and have had no issues since

Hope this helps!

Luke