Skip to main content
jonathanf94338796
Participant
May 17, 2016
Question

ERROR – unable to acquire LMS API, content may not play properly and results may not be recorded. Please contact technical support’ Success Factors

  • May 17, 2016
  • 5 replies
  • 17098 views

Hi,

Trying to play and view SCORM compatible files exported from Adobe Captivate 8 and 9 in Success Factors LMS.

I get the message - 'ERROR – unable to acquire LMS API, content may not play properly and results may not be recorded. Please contact technical support’

I have tried SCORM versions 1.2 v3 and 2004 V2 and V4.  We can view the content, however it does not track, show as complete etc.

We are just in the process of implementing Success Factors and are a bit stumped....

Anyone experienced this problem before? Or know of a fix?

Many thanks

This topic has been closed for replies.

5 replies

Participant
June 12, 2021

Dear Sir,

Anyone please explain about this error i'm new to Captivate. Whenever built the project/module and plays in browser(html5) same error message shown on browser. what to do? please replay me.

Thanks in advance.

RodWard
Community Expert
Community Expert
June 12, 2021

Ths other answers on this thread clearly explain what is happening.  Have you read the other answers yet?  Is there something about this that is still not clear to you?

Participant
March 22, 2020

disable it all,  make elearning output disable

RodWard
Community Expert
Community Expert
March 22, 2020

@adchef.

If you are asking a question, you will need to give more information.  This thread is four years old. 

Perhaps you should start another thread and ask your queston there.

Known Participant
August 23, 2016

Actually I think this is a normal error because it is not hooked into an LMS right?

Allen_Partridge
Adobe Employee
Adobe Employee
August 23, 2016

Correct - the error just means that it isn't synced with the LMS. Since you've not yet uploaded it - that's expected.

Known Participant
August 23, 2016

I am getting this same error when I publish the files to a folder from Captivate and view output. This is before bringing it into the LMS.

RodWard
Community Expert
Community Expert
May 17, 2016

Upload your same zipped SCORMs to SCORM Cloud to test.

If they work in SCORM Cloud then the issue is with your LMS.

If they also do not work in SCORM Cloud then the issue is with your SCORMs.

jonathanf94338796
Participant
May 18, 2016

Thanks Rod, I have tried the files in SCORM cloud and they do work and track, I demonstrated this to our implementation partner and they said that this is a different system to Success Factors and does not have as many complex tracking functionality and the problem still lies with the content.

Is the information we are being told incorrect from the partner?

RodWard
Community Expert
Community Expert
May 18, 2016

Yes and No. 

Yes SCORM Cloud is definitely a different system to Success Factors.

No that doesn't mean its tracking ability isn't as good.  It's probably even better.

They're just trying to dodge having to get in and look under the hood at what the real problem is.

Each LMS vendor has a slightly different idea of how the SCORM standard should be implemented.  They would LIKE you to think that their LMS is better than everyone else's but that's just their marketing hype.  Don't take it as gospel.

SCORM Cloud is actually built by Rustici Software, the people that are heavily involved in the SCORM standard itself, as well as the Tin Can / xAPI / Experience API (whatever you want to call it) standard that was supposed to replace SCORM (but hasn't).

Rustici Software's products are recognised as being the best in the industry and they actually build many of the SCORM Players that are used by other top-rank LMSs.  SCORM Cloud itself is recognised as the 'gold standard' for SCORM compliance and that's why we always recommend people test out their Captivate SCORMs there before concluding that the problem MUST be with their content.

The LMS vendors ALWAYS blame the content.  But in the vast majority of cases that I have seen the issue is actually with the way the LMS has chosen to interpret the SCORM standard.