API error when viewing project

Mar 26, 2021

Hello,

My team and I are trying to resolve multiple issues with our LMS and SCORM. I am trying to figure out what issues are related to what so I have a couple of questions.

1. I am using Storyline 360. I am having problems publishing an updated version of a training. I tried to view the project after publishing but before uploading it to our LMS and I got the "unable to acquire API LMS" error. All of the discussions I have seen were around the error showing up after the course was published in the LMS. Does the fact I see it before it is uploaded into the LMS change anything?

2. The original training was published in SCORM 1.2. While I was on some extended leave a co-worker made a change to the training and changed the SCORM to version 4 when it was re-published. Could this be related to the problem? I have tried to republish with SCORM 1.2 and 4 and still get the API error.

I am not using a network to build or publish the project.

1 Reply
Lauren Connelly

Hello Katie!

I'm sorry you're running into this issue where the API error occurs when viewing a project! We are happy to help.

First, it sounds like you see the API error message when viewing the course on your local hard drive after publishing but before uploading it to your LMS. One way to fix this is in the Player Properties. Make sure in the Other section, Launch Player in New Window is selected. Viewing the course before uploading it to the LMS shouldn't cause an issue unless you're unzipping/zipping the published output folder while it's located in an external environment like a shared drive.

Second, you can change the SCORM version when publishing the project without causing this type of issue. I haven't seen changing the SCORM version cause an API error message.

If you need us to take a look at your project, then, with your permission, please share your project file with our support engineers to investigate what's happening. You can share it privately by uploading it here. It will be deleted when troubleshooting is complete.