LMS API error and Edg animation

Mar 16, 2015

Hi. I’m dealing with the error “unable to acquire LMS API, content may not play properly and results may not be recorded” (captivate 8). This is the background:

I made a course and import an Edge animation audio display buttons to control an audio file (captivate is the worst for that). My animation include the audio. Everything is fine in my html output file but SCORM and EXE files not. I tried all kind of SCORM outputs (My Moodle system is located on my pc). Also, I checked it with SCORM CLOUD and my file is fine, but the problem still there. Finally, I have a file that works in Moodle but doesn’t display the animation, I have an empty space (the error message still showing up).

I disassemble my file to find what happened and made a new one with my audio animation and a new one with the animation without audio, same results. I create a new one just with the animations and I have an empty space. It seems that the import animation just work in the case of an html output.

I need an EXE file working too.

I tried CAPTIVATE SCORM test and this is the result:

Firefox:

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

Press 'OK' to view debug information to send to technical support.

New window:

44:Mon Mar 16 2015 10:28:46 GMT-0600 - In IsLoaded, returning -false
45:Mon Mar 16 2015 10:28:46 GMT-0600 - In IsLoaded, returning -false

Explorer:

The same.

Google Chrome:

The page at bk.psu.edu says:

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

Press 'OK' to view debug information to send to technical support.

New window:

44:Mon Mar 16 2015 10:28:46 GMT-0600 - In IsLoaded, returning -false
45:Mon Mar 16 2015 10:28:46 GMT-0600 - In IsLoaded, returning -false

Java console:

@1426523512128 LMS Driver not loaded. CPLibrary.js:122

Thanks a lot

3 Replies

This discussion is closed. You can start a new discussion or contact Articulate Support.