Scormbee

Fixing the Most Common SCORM Errors in Moodle, Canvas and TalentLMS

11 min read Czytaj po polsku

SCORM problems look mysterious from the outside: a course that "doesn't save", a score that never arrives, a learner stuck at incomplete for the third time. Inside, they come from a short list of causes. This guide goes through them in the order you'll meet them, from upload to report, with the exact messages and settings in Moodle, Canvas and TalentLMS.

Start here: a five-minute diagnosis

First, reproduce the problem outside your LMS. If the course behaves the same in a neutral player, the package is at fault. If it works there, look at the LMS settings.

  • The SCORM validator checks the ZIP: manifest at the root, launch file present, files listed in the manifest actually there.
  • The SCORM player runs the package against a simulated LMS and logs every API call, so you can see what the course sends and when.
  • SCORM Cloud offers a free trial account and keeps a detailed log of each registration.
  • The browser console (F12, then Console) shows script errors while the course runs in your LMS.

Then match the symptom:

Symptom Most likely cause Section
Upload rejected, "missing imsmanifest.xml" Manifest not at the ZIP root 1
"Unable to acquire LMS API" or similar The course can't find the API object 2
Status stays incomplete or not attempted No finish call, a mismatched completion rule, an unsupported version 3
Score missing, or failed despite passing Score fields, pass mark mismatch, grading settings 4
Learners start from the beginning again Exit mode, suspend data overflow, forced new attempts 5
Clicking Enter does nothing Popup blocked 6
Works in Chrome, fails in Safari Third-party cookies 7

1. Upload fails: manifest not at the root

Moodle says: "Incorrect file package - missing imsmanifest.xml or AICC structure". Other LMSs say "invalid package" or "manifest not found". The LMS looks for imsmanifest.xml in the root of the ZIP and doesn't find it.

Check what's inside without unzipping:

unzip -l course.zip | head

You want to see imsmanifest.xml with no folder in front of it. If you see course/imsmanifest.xml, the folder was zipped instead of its contents.

Common causes and fixes:

  • The folder was compressed. macOS "Compress" and Windows "Send to compressed folder" on a folder both add that folder level. Open the folder, select everything inside it, and compress the selection.
  • A ZIP inside a ZIP. Some downloads wrap the package together with other files. Unzip once and upload the inner ZIP.
  • The wrong export. A "web" or "HTML" export has no manifest at all. Export again and choose SCORM.
  • The file is too large. In Moodle the limit comes from the site and course maximum upload size and from PHP's upload_max_filesize and post_max_size; ask your administrator. Institutional Canvas guides list a 500 MB limit for SCORM packages. Compress video and large images.
  • An unsupported version. TalentLMS's help center lists SCORM 1.2 and not SCORM 2004 or multi-SCO packages. A SCORM 2004 package may upload and then fail to track; export SCORM 1.2.

2. "Unable to acquire LMS API"

This message, or a variant of it, appears when the course searches the windows around it for the SCORM API object (API in SCORM 1.2, API_1484_11 in SCORM 2004) and finds nothing. Articulate's players show it as "Unable to acquire LMS API, content may not play properly and results may not be recorded."

Cause How to tell Fix
Opened outside the LMS The address bar shows a file path, a file share or a direct link Launch only from the LMS activity
Course files on another domain The console shows "Blocked a frame with origin … from accessing a cross-origin frame" Host the package in the LMS, or use a package designed for cross-domain delivery
The LMS window that held the API was closed or reloaded Happens when the learner keeps working in the LMS tab while the course is open in a new window Open the course in the current window, or tell learners to leave the LMS tab alone
Version mismatch The manifest declares one SCORM version, the course looks for the other API Re-export in the version the LMS supports
A browser extension blocks scripts Works in a private window without extensions Allow the LMS domain in the extension

The cross-origin message is the most useful one to recognize. It means the course and the LMS are on different domains, and no setting inside the course will fix it.

3. The course stays "incomplete"

The LMS records only what the course sends. If the status never changes, either the course never sent it, or the LMS expects something else.

The course never finished. A course should call LMSFinish (SCORM 1.2) or Terminate (SCORM 2004) and save regularly with LMSCommit or Commit. Chromium-based browsers block synchronous requests while a page is closing, so a course that saves only when the window closes can lose its last data. In the player's log, look for the finish call and for the last status sent before it.

The completion rule in the course wasn't met. "All slides viewed" fails if one slide was skipped, and in SCORM 1.2 a failed quiz replaces completed with failed.

The LMS rule differs from what the course sends. In Moodle, the activity completion settings can require a status ("Passed" or "Completed") or a minimum score. A course without a quiz only ever sends completed, so an activity that requires "Passed" will never complete. Align the two.

The version isn't fully supported. Moodle implements SCORM 2004 only partly, and TalentLMS lists SCORM 1.2 only. If a 2004 package misbehaves, export SCORM 1.2 and test again.

Moodle's "Force completed" setting marks attempts complete regardless of what the course sends. Treat it as a last resort, because it hides the real problem instead of fixing it.

4. Score missing, or "failed" despite passing

The score is out of range. In SCORM 2004, cmi.score.scaled runs from -1 to 1, so 85% is 0.85. Sending 85 returns error 407, "Data Model Element Value Out Of Range", and no score is stored. A decimal comma (0,85) is a type mismatch, error 406. In SCORM 1.2, send cmi.core.score.raw together with score.min and score.max, so the LMS doesn't have to guess the scale.

The pass mark differs. The manifest can carry its own pass mark: adlcp:masteryscore in SCORM 1.2, imsss:minNormalizedMeasure in SCORM 2004. If the course passes learners at 70% and the manifest says 80, a learner with 75% sees "Passed" in the course and "Failed" in the report. Moodle's "Mastery score overrides status" setting does exactly this: when the raw score is lower than the mastery score, the status is set to failed. Use one value everywhere. SCORM 1.2 vs 2004 covers this in detail.

The LMS grades something else. In Moodle, check the SCORM activity's "Grading method". "Learning objects" counts completed or passed objects, so a single-SCO course shows 1 instead of 85. "Highest grade" shows the score. "Attempts grading" then decides which attempt counts: highest, average, first or last completed.

Canvas created no gradebook column. In Canvas's SCORM tool you choose an import type: graded assignment, ungraded assignment or page. Only a graded assignment gets a gradebook column, and the import type can't be changed later. Delete the package from the SCORM tool and upload it again with the right type.

5. Learners start from the beginning

The exit mode isn't suspend. When a learner leaves early, the course must set cmi.core.exit (1.2) or cmi.exit (2004) to suspend. Otherwise many LMSs start a new attempt next time and discard the saved state.

Suspend data overflowed. The saved state has a limit: 4,096 characters in SCORM 1.2, 4,000 in SCORM 2004 2nd and 3rd editions, and 64,000 in the 4th edition. Past it, some LMSs reject the write and others cut the value, and either way the course can't read its state back. In the API log, look for a failed SetValue on cmi.suspend_data, or a value that stops at exactly 4,096 characters. Fix it by exporting SCORM 2004 4th edition, or by splitting a long course into modules.

The LMS forces new attempts. Moodle's "Force new attempt" setting can start a fresh attempt every time ("Always") or after a completed, passed or failed attempt. With "Always", resume never works. Also check the maximum number of attempts.

The learner switched devices. Progress travels only as far as the last successful commit. If the course commits rarely, the second device starts from an older point.

6. Clicking "Enter" does nothing: the popup was blocked

Many LMSs open courses in a new window, and browsers block windows that don't come straight from a click. Look for a blocked-popup icon at the end of the address bar.

  • For one learner: allow popups for the LMS domain. In Chrome: Settings, Privacy and security, Site settings, Pop-ups and redirects.
  • For the whole organization: IT can allow popups for the LMS domain by policy, for example Chrome's PopupsAllowedForUrls.
  • In the LMS: in Moodle, set "Display package" to "Current window" so no popup is needed.

7. Works in Chrome, fails in Safari: third-party cookies

When course content or a SCORM player runs in a frame served from a different domain than the LMS page, any cookies it uses are third-party cookies. Safari has blocked those by default since version 13.1 in 2020, Firefox isolates them per site, and any browser can block them through settings or company policy. This affects externally hosted content, some LTI-based SCORM players, and dynamic or dispatch packages that load the whole course in a frame from another domain.

Symptoms: a blank frame, a login screen inside the course, or progress that's lost between sessions, only in some browsers.

Fixes, best first:

  1. Host the course in the LMS itself, so everything is on one domain.
  2. Use content that doesn't depend on cookies in a cross-site frame.
  3. Open the course in a new window or tab, where its domain is first-party.

To confirm the cause, you can temporarily switch off Safari's "Prevent cross-site tracking" on a test device. That's a diagnostic step, not a fix to roll out to learners.

Platform quick reference

Moodle Canvas TalentLMS
SCORM versions 1.2 fully, 2004 partly Through the SCORM tool 1.2 per its help center; not 2004 or multi-SCO
Where to upload Add an activity, SCORM package SCORM link in course navigation, if enabled Course, Add, SCORM / xAPI / cmi5
Settings to check Display package, Grading method, Attempts grading, Force new attempt, Mastery score overrides status, activity completion Import type (cannot be changed later) Version of the package
Upload limit Site and course limits, PHP settings 500 MB in institutional guides Check current documentation

Prevent it next time

Before any course goes live:

  • imsmanifest.xml at the root, checked with the validator
  • The SCORM version your LMS supports fully
  • One pass mark, identical in the course and the manifest
  • The LMS completion rule matches what the course sends
  • Tested as a learner: complete, fail, leave halfway, resume
  • Opened once in Safari and once on a phone
  • The report line for your test learner reads correctly

Courses exported from Scormbee commit to the LMS shortly after every change, take the course's pass mark and the manifest's from one setting, and set the exit mode to suspend when a learner leaves early. If you have a course built elsewhere that keeps failing these checks and you'd rather rebuild it than patch it, How to edit a SCORM package without the source file covers the options.

Frequently asked questions

What does 'Unable to acquire LMS API' mean?

The course looked for the SCORM API object in the windows around it and didn't find it. Usually the course was opened outside the LMS, its files are served from a different domain than the LMS, or the LMS window that held the API was closed or reloaded.

Why does my course work in SCORM Cloud but not in Moodle?

The package is probably fine and an LMS setting differs: the completion rule requires passed while the course only sends completed, the grading method counts learning objects instead of scores, new attempts are forced, or the course opens in a blocked popup.

Why does the Moodle gradebook show 1 instead of the score?

The SCORM activity's grading method is set to Learning objects, which counts completed or passed objects rather than scores. Switch it to Highest grade.

What is the suspend_data limit in SCORM?

4,096 characters in SCORM 1.2, 4,000 in SCORM 2004 2nd and 3rd editions, and 64,000 in SCORM 2004 4th edition. These are the minimums an LMS must support; many store more, but courses shouldn't count on it.

Do SCORM courses work in Safari?

Yes, when the course is served from the LMS's own domain. Problems appear when content from another domain runs in a frame and depends on cookies, because Safari blocks third-party cookies by default.

More articles

12 November 2026 · 4 min read

How to Update a Dynamic SCORM Course

Publish a change to a Dynamic SCORM course in three steps: edit it, click Publish update, and every LMS shows the new version at the next launch.

Read →