Are you using an image with a link to the module rather than going to the module directly from the default link? We have a set up as below where the computer logo also has the link above. If I click "System Changes" it works fine, if I click the computer image, it breaks with an API error (usually because there is a new version and the image link wasn't updated). People only sometimes use the image to enter the module and so we only sometimes see the error - and people will generally try the other link first before seeking support so it can go a while before being noticed.
In short, check your links match if using custom ways to enter the module.
Thanks for reaching out, and good call to start a case with our support team. It looks like my teammate, Carlo, reached out with some initial steps to troubleshoot your file.
Let him know if they helped or if you need additional assistance with the error!
Hi I have found the same error on iPhone while running the course which I is published on scorm1.2 and tested on scorm cloud. This issue is occurring randomly and not in a particular scenario. Initially this course was published in SCORM 2004 and later we have changed the same to SCORM 1.2.
Thanks for reaching out to follow up. I glanced through many of the support cases that folx worked on with our team, and the solutions varied, so we'd like to help you specifically as well.
Are you getting this error when uploading the content to your LMS or accessing it in a specific environment?
Did you publish for LMS and zip the contents from the successful publish dialog box, or did you manually zip the contents?
Are you able to replicate the behavior in SCORM Cloud?
If you'd prefer to work directly with our team, please contact our team directly here.
61 Replies
I am getting the same error message when viewing SL SCORM project in Moodle. Any update / solution?
Using Moodle as LMS and SL360.
Hi Sebastjan!
After looking through similar cases, I don't see a standard solution, so we'll want our Support Engineers to step in. Please use this link to connect with our Support Team.
Are you using an image with a link to the module rather than going to the module directly from the default link?
We have a set up as below where the computer logo also has the link above.
If I click "System Changes" it works fine, if I click the computer image, it breaks with an API error (usually because there is a new version and the image link wasn't updated). People only sometimes use the image to enter the module and so we only sometimes see the error - and people will generally try the other link first before seeking support so it can go a while before being noticed.
In short, check your links match if using custom ways to enter the module.
Hi I have this problem:
An error has occurred:
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.
Debug window could not be opened, popup blocker in place?
Please help me, Thank you
Hi Anton,
Thanks for reaching out, and good call to start a case with our support team. It looks like my teammate, Carlo, reached out with some initial steps to troubleshoot your file.
Let him know if they helped or if you need additional assistance with the error!
Hi I have found the same error on iPhone while running the course which I is published on scorm1.2 and tested on scorm cloud. This issue is occurring randomly and not in a particular scenario. Initially this course was published in SCORM 2004 and later we have changed the same to SCORM 1.2.
Please provide some solution. Thanks.
Please suggest any solution on this issue ASAP this is argent for me.
Hi, Pankaj.
I'm sorry to hear you're experiencing this error under an urgent deadline!
I went ahead and opened a support case with our engineers on your behalf, so you should hear from our team soon via e-mail.
Any news about the unable-to-acquire-lms-api issue?
Hi Marco,
Thanks for reaching out to follow up. I glanced through many of the support cases that folx worked on with our team, and the solutions varied, so we'd like to help you specifically as well.
If you'd prefer to work directly with our team, please contact our team directly here.
Hi Leslie, there was a Java issue indeed ...
Tnx