eLearning standards and platforms
SCORM not working: find the cause and fix it
A SCORM package fails in one of four places: at upload, at launch, when it looks for the LMS, or when it saves results. Find your symptom in the table, then go to the section for the fix.
Updated
Facts checked on 21 November 2026
Find your symptom
| What you see | Likely cause | Fix |
|---|---|---|
| The LMS rejects the upload: "manifest not found" or "invalid package" | imsmanifest.xml is inside a subfolder, or the course was published for the web | Zip the contents of the folder, not the folder. Publish again with the LMS option. Details |
| It uploads, then will not launch or track | A SCORM 2004 package in an LMS that takes 1.2 only, or the reverse | Publish in the version the LMS supports. Details |
| Nothing opens when you click launch | The browser blocked the new window | Allow pop-ups for the LMS address, or open the course in the same window. Details |
| A blank white page, or a loading spinner that never ends | Course files on another domain, blocked cookies, or an http link inside an https LMS | Read the browser console, then host the files with the LMS. Details |
| "Unable to find an API adapter" or "API connection failed" | The course cannot reach the LMS's API object | Launch from the LMS, match the version, keep one domain. Details |
| The learner finished but still shows "incomplete" | The final save was lost when the tab closed, or the completion rule was never met | Leave by the course's exit button. Check the reporting setting. Details |
| "Failed" where you expected "completed" | A mastery score in the manifest is overriding the status | Align the reporting option with the LMS rule. Details |
| The score column is empty | The course has no scored quiz, so it never sends a score | Add a quiz, or track completion only. Details |
| Learners restart at the first slide | Saved progress is over the 4,096 character limit in SCORM 1.2, or the course did not ask to suspend | Shorten or split the course, or publish as SCORM 2004 3rd or 4th edition. Details |
Test outside the LMS first
The free SCORM viewer plays a package in your browser the way an LMS would and shows what the course reports: completion, score and every API call it makes. It opens SCORM 1.2 and 2004 packages, and the file is not uploaded anywhere.
- Drop the zip inIf the viewer cannot open the file it says why: it is not a zip, it was exported for the web and not for an LMS, or it has no imsmanifest.xml.
- Go through to the endFinish the course as a learner would, including any quiz, and leave by the course's own exit button if it has one.
- Read what it reportedYou should see the course start a session, set a status, save and close. If the status never moves off "incomplete" here, it will not move in your LMS either.
The viewer has two limits. It starts a fresh attempt each time, so it cannot show whether a learner resumes where they stopped, and it does not enforce SCORM 2004 sequencing rules. Test those in the LMS with a learner account, or in a hosted tester from the SCORM Cloud alternatives list.
Double-clicking index.html in an unzipped package gives a blank page or an API error every time. The course is looking for an LMS, and there is none behind a file on your desktop.
The package will not upload
scorm.com's packaging guide puts the rule in one line: the manifest "must always exist at the root of the content". Most rejected uploads break it by accident.
You zipped the folder, not its contents
Right-clicking the course folder and choosing Compress on a Mac, or Send to and Compressed folder on Windows, puts the folder itself inside the zip. The manifest then sits one level down, where the LMS does not look.
Open the folder, select everything inside it, and zip that selection. When you open the finished zip, imsmanifest.xml should be visible straight away, with no folder to click into. The same applies if you unzip a package to edit a SCORM file.
It was published for the web
Authoring tools offer a web or HTML output as well as an LMS output. The web version plays in a browser but has no manifest and no tracking script. Publish again and pick the LMS or SCORM option. How to create a SCORM file shows where that option sits in the common tools.
The version is wrong for the LMS
A package is SCORM 1.2 or one of the SCORM 2004 editions, and the manifest names which in its schemaversion line. An LMS that takes only 1.2 will reject a 2004 package, or import it and then fail to track it. If nobody can tell you what the LMS supports, 1.2 is the safer choice, for the reasons in SCORM 1.2 vs 2004.
If the upload stalls with no error at all, compare the file size with the LMS's upload limit. Packages with video in them reach it first.
The SCORM package is not loading, or the browser blocks it
Pop-up blocker
An LMS launches a course either in a frame inside its own page or in a new window. Chrome blocks pop-ups by default and shows "Pop-up blocked" in the address bar when it does. Click that notice, choose to always allow pop-ups from your LMS's address, and launch again. The lasting fix is on the LMS side: set the course to open in the same window.
The course files are on another domain
SCORM talks to the LMS through script calls between browser windows, and browsers allow those calls only when both windows come from the same domain. If the LMS is at lms.example.com and the course files are served from a content server elsewhere, the course loads and then sits there, unable to reach the LMS.
There are three ways out. Host the course files on the LMS's own domain. Use a cross-domain wrapper, a small package on the LMS side that relays messages to the remote course, which Rustici documents. Or use a standard built to work across domains, such as cmi5, compared in SCORM vs xAPI.
Third-party cookies
Remote content that needs its own login or session cookie has a second problem: inside the LMS page its cookies count as third-party. Safari blocks those by default and Firefox isolates them by default. Chrome blocks them only in Incognito, or when the user has turned blocking on. So a course that runs in a normal Chrome window and goes blank in Incognito or Safari points here.
Allowing the content site in Chrome's third-party cookie settings fixes one machine. For a whole workforce, the content has to move to the LMS domain or stop depending on its own cookies.
An http link inside an https LMS
If the LMS runs on https and the course loads a script or a frame over plain http, the browser refuses the request. Older packages with hard-coded http links fail this way. Correct the links in the source file and publish again.
Press F12 (Option, Command and I on a Mac), open the Console tab and launch the course again. Red lines that mention a cross-origin frame point to the domain problem. Lines that start "Mixed Content" point to an http link. A 404 names a file that is missing from the package.
"Unable to find the SCORM API" or "API connection failed"
The wording varies with the authoring tool: "unable to find an API adapter", "SCORM API connection failed", "could not find the SCORM API". Each one says the course looked for the LMS and did not find it.
When a course starts, it looks for a JavaScript object that the LMS provides. In SCORM 1.2 the object is named API. In SCORM 2004 it is named API_1484_11. The course checks the window that contains it, then that window's parent, and so on up the chain. If that fails, it checks the window that opened it and that window's parents.
| Cause | How to tell | Fix |
|---|---|---|
| There is no LMS | You opened the file directly, or used a preview that provides no API | Launch from the LMS or from the SCORM viewer |
| Version mismatch | A 1.2 course looks only for API, a 2004 course only for API_1484_11 | Publish in the version the LMS supports and upload it as that type |
| Two domains | The console shows a cross-origin error | Host the course files with the LMS |
| A new window that cannot see the LMS | It fails only when the course opens in a new window | Set the course to open in a frame inside the LMS page |
| Nested too deep | The LMS itself sits inside a portal with many frames | Open the LMS outside the portal and launch again |
The last row is rare. ADL's sample search code for SCORM 1.2 gives up after 7 parent windows and reports the API as too deeply nested. The 2004 sample allows up to 500 tries.
SCORM is not tracking completion or score
A SCORM 1.2 course has to make four kinds of call for anything to be stored: LMSInitialize to open the session, LMSSetValue to write a result, LMSCommit to ask the LMS to store it, and LMSFinish to close. In SCORM 2004 the same calls are named Initialize, SetValue, Commit and Terminate. A result that was set and never committed may not reach the LMS database.
The learner closed the tab
Many courses send their last save as the window closes. Since version 80, Chrome has disallowed synchronous requests while a page is being dismissed. Rustici Software, the company behind scorm.com and SCORM Cloud, documents that this can block the final save and leave the attempt incomplete.
Leaving by the course's own exit button avoids the lost save. Closing the browser tab is what triggers it. Put that one line in the course description, then ask your LMS vendor whether its player handles the Chrome change, because the permanent fix is on their side. Moodle, for one, has an "Auto commit" setting that saves 60 seconds after values are set.
The status rules in SCORM 1.2
SCORM 1.2 has one status field, cmi.core.lesson_status, with six allowed values: passed, completed, failed, incomplete, browsed and not attempted. The rules the LMS applies to it explain most odd results.
- On first launch the LMS sets the status to "not attempted".
- If the course closes without ever setting a status, the LMS sets it to "completed". A course that reports nothing is complete as soon as it has been opened and closed.
- If the manifest carries a mastery score and the course reports a raw score, the LMS compares the two and sets "passed" or "failed".
The specification is unclear about whether the mastery score should override a status the course set for itself, and LMSs differ. Rustici's player makes it a setting per course, and Moodle has a "Mastery score overrides status" setting. So a learner can view every slide, score 60 against a mastery score of 80, and show as "failed" where you expected "completed".
Decide which result you want the LMS to show, then make both ends agree: the authoring tool's reporting option (completed or incomplete, against passed or failed) and the LMS's completion rule for the course. SCORM 2004 splits the field into completion status and success status, which removes the ambiguity, though an LMS rule can still be watching the one your course does not set.
The score column is empty
A score exists only if the course writes one. A package with no scored quiz, such as a converted slide deck or a wrapped video, reports completion and nothing else.
Learners restart at the beginning
The cmi.suspend_data field. Long courses with many slides and variables can outgrow it.
The 2nd edition allows 4,000, so check which edition you are publishing.
The cmi.core.lesson_location field, which holds the place to resume from.
When a course tries to save more than the LMS will hold, the save can be refused or cut short, and the learner comes back to slide one or to a course that will not load. Publish as SCORM 2004 3rd or 4th edition if your LMS supports it, or split the course into shorter packages.
Resume has a second requirement. The course must set its exit value to "suspend" when the learner leaves (cmi.core.exit in 1.2, cmi.exit in 2004). If the value is left empty, the LMS starts a new attempt at the next launch.
SCORM error codes in plain words
After any call, a course can ask the LMS for the code of the last error. You will meet these numbers in the SCORM viewer's log, in an LMS debug log or in the browser console. The names are the official ones from the run-time reference.
SCORM 1.2 error codes
| Code | Name | What it means |
|---|---|---|
| 0 | No error | The last call worked. |
| 101 | General exception | Something failed and the LMS has no more specific code for it. |
| 201 | Invalid argument error | The course passed a name or value the LMS does not recognise, such as a misspelt data element. |
| 202 | Element cannot have children | The course asked for the sub-items of an element that has none. |
| 203 | Element not an array, cannot have count | The course asked how many entries an element has, and it is not a list. |
| 301 | Not initialized | The course called the API before LMSInitialize, so the session never started. |
| 401 | Not implemented error | The element is valid SCORM 1.2, but this LMS does not support it. Many elements are optional in 1.2. |
| 402 | Invalid set value, element is a keyword | The course tried to write to a reserved keyword. |
| 403 | Element is read only | The course tried to change a value only the LMS can set, such as the mastery score. |
| 404 | Element is write only | The course tried to read a value it can only send, such as session time. |
| 405 | Incorrect data type | The value is in the wrong format, for example a status that is not one of the six allowed words. |
SCORM 2004 error codes
| Code | Name | What it means |
|---|---|---|
| 0 | No error | The last call worked. |
| 101 | General exception | A failure with no more specific code. |
| 102 | General initialization failure | The LMS could not start the session. |
| 103, 104 | Already initialized, content instance terminated | Initialize was called twice, or called after the session had ended. |
| 111 | General termination failure | The LMS could not close the session. |
| 112, 113 | Termination before initialization, termination after termination | Terminate was called with no open session, or called twice. |
| 122, 123 | Retrieve data before initialization, after termination | The course tried to read a value outside an open session. |
| 132, 133 | Store data before initialization, after termination | The course tried to write a value outside an open session. A late save after exit lands here. |
| 142, 143 | Commit before initialization, after termination | The course asked the LMS to save outside an open session. |
| 201 | General argument error | The course passed an argument the LMS cannot accept. |
| 301, 351, 391 | General get, set and commit failure | A read, a write or a save failed with no more specific cause. |
| 401 | Undefined data model element | The element name does not exist in SCORM 2004, for example a 1.2 name such as cmi.core.lesson_status. |
| 402 | Unimplemented data model element | The element is valid, but this LMS does not support it. |
| 403 | Data model element value not initialized | The course read a value nothing has written yet. |
| 404, 405 | Element is read only, element is write only | The course tried to write a read-only value or read a write-only one. |
| 406, 407 | Type mismatch, value out of range | The value is the wrong kind of data, or the right kind but outside the allowed range. |
| 408 | Data model dependency not established | The course set a value before the one it depends on, such as an answer before the question's identifier. |
Some codes are harmless. In SCORM 2004, 403 turns up in normal running whenever a course reads a value nothing has written yet, such as the bookmark on a first launch. In 1.2, 401 often means the course asked for an optional element this LMS never implemented.
If it still fails, send support these six things
- The SCORM version and edition the package was published in.
- Whether it runs and completes in the SCORM viewer.
- The browser and its version, and whether a second browser behaves differently.
- Whether the course opens in a new window or inside the LMS page.
- The exact error text, plus any red lines from the console.
- Whether you tested as a learner or in an administrator preview. Some LMSs do not save results from a preview.
Questions people ask
Why is my SCORM package not working in Chrome?
Why is my SCORM package not loading?
What does "unable to find SCORM API" mean?
Why is SCORM not tracking completion?
What is the suspend data limit in SCORM 1.2?
What does SCORM error 301 mean?
How do I test a SCORM package without an LMS?
Sources
- scorm.com (Rustici Software): SCORM run-time reference, API calls, data model and error codes
- scorm.com: the SCORM run-time environment
- scorm.com: API discovery algorithms (ADL sample code)
- scorm.com: SCORM content packaging
- scorm.com: SCORM and cross-domain content
- scorm.com blog: Why can't my content find the SCORM API?
- scorm.com blog: lesson status and mastery score in SCORM 1.2
- Rustici Software support: blocked SCORM exit postbacks with Chrome 80 and above
- Chrome for Developers: deprecations and removals in Chrome 80
- web.dev: synchronous requests during page dismissal
- MDN: third-party cookies
- MDN: mixed content
- Google Chrome Help: block or allow pop-ups
- Google Chrome Help: third-party cookie settings
- Moodle documentation: SCORM settings
Keep reading
Last reviewed 21 November 2026. Recourse publishes these guides for learning, customer education and change teams. Details drawn from public sources can change.