I tried to access the course on the LMS and this is the error I received: "Error - Unable to acquire LMS API, content may not play properly and results may not be recorded." Has any experienced this and what is your solution? Thank you.

I had the same error message, and found out the hard way that it was the configuration of the LMS. We are going to a new LMS and found out that the "Stage" area (which is our current location for everything to test) was launching a window for the course that was looking to our "Production" area. Even though it was correctly locating the courses on our server, it could not do a cross domain for those 2 areas. Turns out that is a good thing (to prevent XSS/ Cross Domain access) because that would open us up to being hacked easily. I've been creating courses for 16 years, but I'm new to directly working with LMS systems. Hope this could help someone else. FYI: The LMS is "Success Factors" from SAP, and after a lot of research, there have been a lot of people with this error on many different LMSs and using several different Authoring Tools (Storyline 2, Captivate, Lectora). Really, all SCORM versions. (I would use Tin Can API if they had the ability to use that for Tracking/Reporting/Bookmarking. - Kyle

Hi Denys, Are you using the same LMS as Kyle? I'm not sure if he is still subscribed here, as the post is a bit older - but you could always use the "contact me" button on a ELH users' profile to reach out to them directly! Did you already test the steps here about launching it in a new window? What about testing in SCORM Cloud to compare to what you're seeing?

Hi Leslie, Thanks for the response. I have not tested with SCORM Cloud. I will test with SCORM Cloud if the error becomes a common problem. I do not think this is a Java issue since the error occurred on a mobile phone and immediately relaunching the course on the same phone was successful, but I will check with the LMS vendor. At this point I think the error occurred because of a weak mobile connection. I am hoping there are some folks out there that have a solution to decreasing the error's occurrence, such as how to increase the number of times the course attempts to connect to the LMS before giving the error.

Hi Thatchrina and welcome to Heroes! If you receive an "Unable to acquire LMS API" error when launching Articulate content in your LMS, this may be caused by the version of Java that you have installed.Some LMS’s use a Java API object to load content. Since content created in Articulate does not require Java, please do the following:* Contact your LMS provider and ensure that your installed version of Java is compatible with the version of the LMS you are using.* Ensure that you have published your content properly as described in the following article. Hope that helps and feel free to let us know if you need anything else!

Just an update this error message. The reason I received it was solely to do with a checkbox within the player. When the checkbox to launch in a new windrow, it creates a "launcher" file. In the past I could delete this file and still publish but that's not the case anymore. I have to uncheck the box. Perhaps there is a relationship to the Java version. If it's updated, this may not be an issue? I'm not sure, will have to test this out! :)

Got an error: Unable to acquire LMS API

AndrewEngland-2
Community Member
7 years ago
Hi Ashley,

The issue seems to be a Storyline issue, and device specific. Yes, it's only occurring on the Samsung device and the issue occurs both on Totara and on ScormCloud.

Aside from that, our LMS does not use Java at all.

Publish settings in Storyline seem to be correct.
KatieRiggio
Staff
7 years ago
Hi, Andrew. Thanks for reaching out in the forums, and I see you opened a support case earlier today for the same issue–smart move! I'm also perplexed as to what is causing this alert on your Samsung device – what OS is it running?

My teammate, Abel, will reach out with his findings as soon as he completes testing your file. I'll also follow along as the case progresses and share important updates here as needed!
- AndrewEngland-2
  Community Member
  7 years ago
  Hi Katie,
  
  Thanks for looking into this. The issue is causing some headaches for our
  client.
  
  The Samsung Galaxy tablet we have been testing on has the spec as attached
  screen capture. Hope this helps
  
  The client has also tested on a Samsung Galaxy tablet and experiences the
  issue. They're testing on a Samsung Galaxy Tab A 6.0.1.
  
  We await your findings.
  
  Thanks again,
  
  Andrew
AllanAikman-07c
Community Member
7 years ago
I have had this error intermittently with several e-learning modules. They have been constructed using various tools, mainly Storyline 360. I have checked Java and ensured the open in a new window is unchecked.

The latest ones with the issue, I tested in SCORM cloud and had no issues and the manifest looked ok. SuccessFactors LMS shows an error in upload, claiming an issue in the manifest.

Would it be possible for Articulate and SuccessFactors to get together and workout why this error is occurring?

I understand that if it works in SCORM cloud, the module is fine, but perhaps some communication between the two parties on what the LMS needs to handle Storyline 360 output?

Any thoughts?

regards

Allan
KatieRiggio
Staff
7 years ago
I'm sorry for the headaches this puzzle is causing, and appreciate the extra detail, Andrew! Every bit helps. I shared this information with Abel and see he is still hard at work carefully testing in various environments. Keep an eye out for his email soon, and I'll continue to follow along!

Hi there, Allan! I'm sorry you're still hitting that error, too. I'm sure this puzzle hasn't been fun to troubleshoot since it happens intermittently. You mentioned that about 12 out of 600+ learners run into this message – do you notice any trends in their environment? Just to verify, it sounds like you've shared the communication logs between SuccessFactors and your Storyline content with your LMS admin?

In the meantime, I've created a case on your behalf for our Support Engineers so we can help along the way. Someone from the team will be in touch and I'll follow this case as well.
AshleyT-Pollard
Staff
7 years ago
Hi Cheryl,

I saw your other post here on the issue as well, and I'm sorry this error continues to put up roadblocks for your content.

Have you heard anything from your SuccessFactors team about that error? It is LMS specific, so they'd be the best resource for digging in further. I'd share with them the links that work in SCORM Cloud so that they can compare for testing.

Keep us posted on what you find out, I know that lots of folks use Success Factors so it may help someone else who runs into a similar situation.
JenniferLazzaro
Community Member
7 years ago
Have there been any updates on this? We use Successfactors as our LMS and are starting to see this API connection error with our SCORM 1.2 courses. As others have noted, it appears to be random, but for some users, when they try to resume the course, it now completely freezes on them.
AshleyT-Pollard
Staff
7 years ago
Hi Jennifer,

I haven't heard any updates from Cheryl about what SuccessFactors thought, but you could always try messaging her directly using the Contact me button on her profile.

Let us know what you find out!
AllanAikman-07c
Community Member
7 years ago
I am still having these issues. I have shared the .story file and uploaded to SCORM cloud. I have been told that you are testing this, but I still have had no solution.
- GerryMcAteer-86
  Community Member
  7 years ago
  Hi Allan, just wondering if you have any luck with a solution to this issue? We are having the same issues as to what you are experiencing and it is causing a lot of frustration with our effected end users.
  
  thanks
  
  Gerry
  - AshleyT-Pollard
    Staff
    7 years ago
    Hi Gerry,
    
    Our team was also working with Allan and waiting to hear back with some additional info, but I don't see we've heard much since August.
    
    Did you also test to see if you're receiving this error in any other LMS environments, such as SCORM Cloud? Our team is happy to help test if you'd like to share details with us in a case.
KatieRiggio
Staff
7 years ago
Hi, Allan. I'm very sorry this error is still plaguing your courses, and really appreciate you continuing to reach out!

I took a peek at your case with my teammate, Ryan, and saw he shared instructions on how to enable LMS debug mode. Has SuccessFactors had a chance to review those logs? If you're able to share the logs in your case, we're also happy to help you and your team interpret it!

Thanks again, and we're both standing by if you need anything else!
LeslieMcKerchie
Staff
7 years ago
Hi Gerry,

Thanks for reaching out and letting us know that you are experiencing an issue as well.

I took a look at Allan's support case and wanted to share a link to a similar conversation that explains the resolution.

Hopefully this is able to help you out as well :)