When publishing to LMS from Storyline 2, I receive an error, "Error - unable to acquire LMS API..." (see attachments). I was able to publish another project to LMS format earlier today, so it may be an issue with the project file. There was another error that mentioned file and/or directory names may be too long, but I got past that by dropping a few characters.
Hi, Tan -- Thanks for reaching out and sorry to hear of your troubles! Perhaps you'll find improvement if you run through some of the suggestions offered on a similar topic over here. Please let us know if issues persist and we'll see what more we can do to assist! :)
Thanks Christie! I tried the fix that worked for Maree Eilman (change file name, version, re-publish), but I wasn't so lucky. I get the same error. Here's where things go wrong:
20:Wed May 04 2016 10:35:32 GMT-0700 (Pacific Daylight Time) - In SCORM_GetAPI 21:Wed May 04 2016 10:35:32 GMT-0700 (Pacific Daylight Time) - SCORM_GetAPI, searching opener 22:Wed May 04 2016 10:35:32 GMT-0700 (Pacific Daylight Time) - Error grabbing 1.2 API-SecurityError:Blocked a frame with origin "null" from accessing a cross-origin frame. 23:Wed May 04 2016 10:35:32 GMT-0700 (Pacific Daylight Time) - Unable to acquire SCORM API: 24:Wed May 04 2016 10:35:32 GMT-0700 (Pacific Daylight Time) - SCORM_objAPI=object 25:Wed May 04 2016 10:35:32 GMT-0700 (Pacific Daylight Time) - In InitializeExecuted, blnSuccess=false, strErrorMessage=Error - unable to acquire LMS API, content may not play properly and results may not be recorded. Please contact technical support.
Hi, Tan -- Thanks for your reply and so sorry to hear that issues persist! It would be best if you were able to share that information with our Support Engineers so that they may be able to provide additional technical insights. Please use this form to submit a case and I will be sure to follow along! :)
Hi, Tan -- May I ask which browser you are using? I have heard of this trouble before and usually switching to a different browser to submit the case will do the trick! But, I'd be happy to go ahead and create a ticket on your behalf. You will be receiving a confirmation message to the email we have on file for you in our system shortly. Thanks for your patience! :)
Hi, Tan -- Your case #00787803 has been received in our system! If you have not received the confirmation email, please check your SPAM folder in case it was routed there in error.
I popped in to take a look at Tan's case and wanted to share the resolution that was able to assist the user.
From our support engineer:
I've ran a quick test on SCORM Cloud (Industry standard LMS testing engine) and the content worked as expected. However, it appears that your Storyline course was configured to launch in new window. If your LMS automatically launches content in a separate browser window, we don't recommend setting Storyline to launch content in a new window. Otherwise, you may encounter an LMS communication error.
Please follow the instructions on this article and republish your content to your LMS:
8 Replies
Hi, Tan -- Thanks for reaching out and sorry to hear of your troubles! Perhaps you'll find improvement if you run through some of the suggestions offered on a similar topic over here. Please let us know if issues persist and we'll see what more we can do to assist! :)
Thanks Christie! I tried the fix that worked for Maree Eilman (change file name, version, re-publish), but I wasn't so lucky. I get the same error. Here's where things go wrong:
20:Wed May 04 2016 10:35:32 GMT-0700 (Pacific Daylight Time) - In SCORM_GetAPI
21:Wed May 04 2016 10:35:32 GMT-0700 (Pacific Daylight Time) - SCORM_GetAPI, searching opener
22:Wed May 04 2016 10:35:32 GMT-0700 (Pacific Daylight Time) - Error grabbing 1.2 API-SecurityError:Blocked a frame with origin "null" from accessing a cross-origin frame.
23:Wed May 04 2016 10:35:32 GMT-0700 (Pacific Daylight Time) - Unable to acquire SCORM API:
24:Wed May 04 2016 10:35:32 GMT-0700 (Pacific Daylight Time) - SCORM_objAPI=object
25:Wed May 04 2016 10:35:32 GMT-0700 (Pacific Daylight Time) - In InitializeExecuted, blnSuccess=false, strErrorMessage=Error - unable to acquire LMS API, content may not play properly and results may not be recorded. Please contact technical support.
Hi, Tan -- Thanks for your reply and so sorry to hear that issues persist! It would be best if you were able to share that information with our Support Engineers so that they may be able to provide additional technical insights. Please use this form to submit a case and I will be sure to follow along! :)
Christie, thanks, although when I attempted to submit a case, there's an issue with the form:
"Whoops. We are having trouble processing your request. Please try again later."
Hi, Tan -- May I ask which browser you are using? I have heard of this trouble before and usually switching to a different browser to submit the case will do the trick! But, I'd be happy to go ahead and create a ticket on your behalf. You will be receiving a confirmation message to the email we have on file for you in our system shortly. Thanks for your patience! :)
Hi, Tan -- Your case #00787803 has been received in our system! If you have not received the confirmation email, please check your SPAM folder in case it was routed there in error.
Hi.
I have the same issue, have you been able to fix it?
Hi Julien!
I popped in to take a look at Tan's case and wanted to share the resolution that was able to assist the user.
From our support engineer:
I've ran a quick test on SCORM Cloud (Industry standard LMS testing engine) and the content worked as expected. However, it appears that your Storyline course was configured to launch in new window. If your LMS automatically launches content in a separate browser window, we don't recommend setting Storyline to launch content in a new window. Otherwise, you may encounter an LMS communication error.
Please follow the instructions on this article and republish your content to your LMS:
http://www.articulate.com/support/storyline-2/lms-communication-error-when-launching-content-in-a-new-window-sl2
This discussion is closed. You can start a new discussion or contact Articulate Support.