Fix the most common errors users encounter when using SCORM content modules.
Uploading: error message about a manifest file
The following screenshot shows an error message about a missing manifest file.
The message reads:
We failed to upload the Zip, as we did not find a manifest.
Are you sure imsmanifest.xml or tincan.xml is in the root of your package/zip, and not in a subfolder within your zip?
Fix 1: make sure the manifest is part of the zipped file
For SCORM files, typically the missing file is called imsmanifest.xml, and is missed when creating the ZIP. For Tin Can files, the manifest is called tincan.xml.
If the zipped file doesn't include the manifest, LearnUpon doesn't have the "directions" to use the module.
Make sure the manifest appears in the root of the zipped package.
Fix 2: make sure the manifest is at root of the zipped file, not within a file inside the zipped package
A similar error occurs if the SCORM package is zipped incorrectly before uploading: for example, the imsmanifest.xml is within another directory, not at the root of the zipped file.
This error occurs if you zip a file that contains all the SCORM components, including the manifest.
The solution: don't send a file containing components to zip, but zip the contents of the file. For example:
- open your compression software
- open the file containing all the components
- select and zip the component files, including the manifest
- return to the file containing the SCORM components
- within the file, select all components including the manifest
- select your zip option
The following screenshot shows the contents of a SCORM module, selected and ready to compress, aka zip.
Uploading: error message about SCORM version
LearnUpon supports SCORM 1.2 and SCORM 2004, 3rd and 4th edition versions. See SCORM and xAPI (Tin Can): overview for background.
If you attempt to upload modules made using the earlier SCORM 1.1 version, the application generates a loading error.
To upload successfully you need to republish the SCORM content in the correct version.
- return to the authoring tool
- generate the module again in SCORM 1.2 or SCORM 2004, 3rd or 4th edition format
- optionally: generate in Tin Can format
Most content authoring tools let you save and generate your content in multiple formats.
Running modules: a white page appears
If you select a SCORM module to start it, and you get a blank screen, check:
- how current is the SCORM authoring tool used to create the module?
- how current is the browser?
LearnUpon uses a content delivery network (CDN) to ensure speedy delivery of content to learners around the world. Some older SCORM modules can try to request data from outside their place of origin: so instead of requesting data from the original source, they request data from a different location.
The browser blocks the request, because calling for content from an unknown source is a security risk.
- update the SCORM authoring tool to a current version
- republish the module with a current authoring tool
Current tools keep up to date on good security practice and won't include requests outside authorized sources.
Running modules: access denied 403 error
This error can happen if the SCORM module is not published correctly, where:
- an asset is missing: a content file like a video or audio file isn't in the ZIP
- the path to an asset doesn't meet the default: for example, a module's manifest file is within another directory, instead of the root directory
When the SCORM module requests these assets from LearnUpon, the application cannot find them. Typically on the internet, this error appears as HTTP 404 "file not found".
LearnUpon uses AWS, which returns an HTTP 403 "access denied" error: from AWS' perspective, it was denied the requested asset.
- make sure your zipped package contains all its required files
- make sure the manifest file is in the root directory
Running modules: slow to launch, animations are "laggy"
If you launch a module and:
- module is consistently slow
- the content lags between steps
- the animations are slow or jagged or "laggy"
Typically, these faults relate to the browser. Content can fail to load and run if learners are using an out-of-date browser. LearnUpon runs smoothly on the most recent versions of browsers, and the previous major version.
The fix: make sure the browser available to users is up to date. See LearnUpon system requirements.
Warning: Microsoft ended support for Internet Explorer 11 in June 2022. As a result, LearnUpon doesn't support IE 11.
Running modules: module is blocked
If you start a module and find its progress is blocked outright, it may contain Adobe Flash content.
Warning: Adobe stopped supporting Flash Player on 31 December 2020, and blocked Flash content from running in Flash Player from 12 January 2021. Adobe strongly recommends all users immediately uninstall Flash Player to help protect their systems.
Some authoring tools previously used Adobe Flash for animations as as default, with a fallback option of HTML5. Adobe Flash is no longer supported, and represents a security risk in your content.
- in the authoring tool, check the default settings to ensure that the tool does not generate Flash animations
- make sure all content renders as HTML5
- republish the module without Adobe Flash content
User finishes a SCORM module but no score appears
When running a SCORM module, the module looks for a message called LMSFinish from LearnUpon, which tells the module that a learner exited a SCORM module. LearnUpon then needs to check for a score, and compare it to a mastery score.
In the application interface, the Save and Exit button generates LMSFinish. Sometimes LearnUpon doesn't generate this message because:
- the user exited the module by closing the browser tab, or the whole browser, instead of selecting Save and Exit
- the user has the SCORM module open in more than one tab or window: LearnUpon requires data from a single source
- the user has left a module open too long, such as over 12 hours: the module looks like it's running, but it has closed in the background
- the SCORM module didn't generate LMSFinish for other reasons
- the SCORM module has a publishing error, which means it doesn't send the lesson_status completion data: this data is the Passed/Failed or Complete/Incomplete which LearnUpon needs to provide a score
To test possible causes, run the LearnUpon debugger - see SCORM content: use the module debugging tool for troubleshooting for a how-to. You're checking:
- can the SCORM module send LMSFinish correctly when you select Save and Exit
- can the SCORM module send lesson_status, to generate completion data
Fix 1: LMSFinish requires Save and Exit button
If the module sends LMSFinish successfully: advise and support learners about running SCORM courses in their browser. Remind users to Save and Exit to end a SCORM module, so LearnUpon gets their completion data.
The following screenshot shows the browser reminder you get in Chrome.
The following screenshot shows the popup reminder within the SCORM file.
Note: this SCORM popup appears only if you progress through the module. It doesn't appear if you open and close the SCORM without actions like selecting Next or Previous, or entering answers to questions.
Fix 2: no LMSFinish or lesson_status messages
If the module is not sending LMSFinish or lesson_status correctly, or is sending the wrong status, you need to contact your SCORM developer to resolve the problem.