Forum Discussion
Error - unable to acquire LMS API content may not play....
This issue started yesterday on my computer. I wasn't able to preview my course in the LMS. I read previous reports about Java and Storyline so I updated my Java to the most current version...and it didn't work. I restarted my computer and changed browsers...and it still didn't work. If I log in as an administrator it works fine, but when I log into the LMS as a participant, I get the error. Now we are getting trouble tickets from dozens of learners (from a variety of buildings on campus) trying to take different courses on our server and they are getting the same error. What is the fix for this? How can the same error affect me and courses I didn't even develop that are currently on our server!
6 Replies
Hi Yvonne,
Have you reached out to your LMS team about the version of Java that they need to work with? I'd begin there to start tracking down the issue.
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! :)
Looks like you shared in a lot of threads Michelle :) I was feeling like a broken record, but you sought out to share where applicable. Thanks again!
Ha ha! There were so many on this topic so I posted to the ones that had the most replies! Thanks. :)
Sent from my iPhone
We are getting this error, and that check box is not checked. We published as SCORM 2004, without that box checked, and we are still getting this message. Could there be any other reason?
Hello Rebekah,
Thank you for reaching out and sharing that you are getting a similar error. It looks like this conversation is a bit dated, but I'd be happy to dig in and help you here.
- To confirm, you are seeing this error when uploading your content to the LMS or when viewing the content within the LMS?
- Are you able to replicate this behavior in another LMS, such as SCORM Cloud, or is this limited to your LMS?
