Publishing for Lectora

Hi - I have an Articulate presenter course that my client is trying to place into a Lectora/Oracle LMS.  I don't have any experience with this, as we typically publish everything to Articulate Online.  I tried publishing using the LMS settings within Articulate, but the client is  saying they are getting the following error...

Does anyone know what to do with this?

Thanks in advance for any advice!


5 Replies
Christine Hendrickson

Hi Alyson,

I haven't personally used Lectora. However, I believe you need to publish as SCORM and provide Lectora with a zip created with Presenter. I've read that if you manually zip the file yourself, Lectora won't be able to work with the file properly. 

I found an older thread, here, that provides a little more information. 

Hopefully we can find some community Heroes that have used this LMS with some additional suggestions. Alternatively, if the client is limited to this particular LMS, it couldn't hurt to contact Lectora and ask them if they can give any advice about adding the content to their servers.

Let us know how it goes!

Dwayne Schamp

I have used both Lectora and Articulate for years. in the past, I let the Lectora course be the SCORM connection to the LMS and "wrap" the Articulate web output into it. It looks like they are publishing the Lectora course as SCORM as well, which is causing the conflicting communication from the file.

After publish to web, all they should need to do is drop in the player.html into an iFrame on a Lectora page and make sure the player.html, player folder, and data folder are at the same level as the "a001_index.html" file in the Lectora SCORM->HTML> folder.

Leslie McKerchie

Hi Peter! I do not think that I've welcomed you to E-Learning Heroes yet, so welcome

Would you be able to test your course in SCORM Cloud to help us determine if the issue is Articulate related or if it is on your LMS's side? If it appears in SCORM Cloud as well, we'd be happy to take a closer look at what might be going on. If you cannot replicate the issue in SCORM Cloud, it is probably an issue that you would want to take to your LMS team.