Table of Contents |
---|
...
- Check the Scorm version (see SCORMVersion 5440507153)
- Check that the course link is published (see CourseIsNotViewableByStudents5440507153) (only applies to 4.2.x)
- Check the SCOId and Resource Id for invalid characters (see No Error (infinite loading) or "No Links Specified" in the LMS, fixed in 4.3.0)
- Check the SCOManifest.js and ensure a SCOId is mapped (see OldManifestMapping 5440507153)
- Check the browser's Console for errors and Network tab for external calls and or errors (including 3rd party cookies and if the course is using Flash).
- Note: Often, Scorm courses will cancel a web request for their entry point and then re-request it. This is very common, and hasn't been known to cause any issues (and can be reasonably ignored as the problem):
- Note: Often, Scorm courses will cancel a web request for their entry point and then re-request it. This is very common, and hasn't been known to cause any issues (and can be reasonably ignored as the problem):
- Check the Scorm calls by debugging the Scorm course via the browser's Sources tab and setting break points in API.LMSGetValue and API.LMSSetValue in MarineLMS-SCORM-API.js (see DebuggingAPICalls 5440507153)
- Try and import the Scorm course locally, and debug the extraction process to ensure the course contains activities and has a valid manifest (see DebugtheScormExtraction(ImportScormcommand) 5440507153)
- Check the package works outside the LMS by verifying the package on the Scorm Cloud (see TestingthePackageExternally 5440507153)
If all those steps fail, the issue will need to be escalated, and bounced back to the client/vendor; or new troubleshooting steps will be required.
...
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
var myAPI = getAPIHandle(); if (!myAPI) { console.log("Mapping: Could not find API"); } else{ console.log("APIFOUND"); myAPI.SCOIdFromManifest = {}; myAPI.SCODataFromManifest = {}; myAPI.SCOIdFromManifest = '__6g7FD8imvYA_course_id_RES'; myAPI.SCODataFromManifest = {"id":"__6g7FD8imvYA_course_id_RES","timelimitaction":"ContinueNoMessage"}; } |
Common Errors
Illegal Characters in Path
As of 4.4.0 a new command has been added to check the file names for illegal characters. Example:
Code Block |
---|
Executed Command:
CheckScormPackageForIllegalFileNames G:\temp\Restaurant College Module 3\imsmanifest.xml
Potentially problematic file names:
scormcontent/assets/SmmU578JI3PILR8g_transcoded-P77p2VQ6Zr8Yh-Uf-Saute%C3%A9d%20Beans.mp3 |
Before 4.4.0 this manifests as:
Code Block |
---|
Executed Command:
importScorm G:\temp\Restaurant College Module 3.zip /Root/Carnival/CCL/test Test C0902
Read Zipped Package: 'G:\temp\Restaurant College Module 3.zip'
Read Scorm manifest settings.
Unexpected exception in ImportScorm: This package could not be opened. More information: |
Run the command locally against the imsmanifest.xml to find problematic files. Once found, rename the asset on disk, and update the imsmanifest.xml reference with the updated file name (with the offending character removed). Re-zip and importScorm again.
No Error (infinite loading) or "No Links Specified" in the LMS
...
Course Is Not Viewable By Students
There is currently an issue on 4.2.x with the importScorm command, caused by
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
- After running importScorm, navigate to the course itself (final link).
- Before changing the template to the SCORM course template as you normally do, you need to Edit > Links > Publish the link.
- Then you can change the template to the proper SCORM template. (Edit > Page > Change Template)
Currently the SCORM templates (at least SCORM.Course.Simple.cshtml) don't seem to be aware of this and so no error is shown anywhere in the console or network trace.
Debug the Scorm Extraction (ImportScorm command)
When debugging the ImportScorm command the first break point should be set in CoreClient.Scorm.cs on line 183 (CreateManifestJSFile()). If the sco_resources count is 0, the course either has multiple child activities (which isn't supported until 4.2.x
), or the manifest is incorrectly made/formatted. If this method is unable to find any sco resources, the package is improperly made, and must be checked on Scorm Cloud (see next section) and/or bounced back to the client/vendor. Jira Legacy server System JIRA serverId 23f523ea-1678-3ca2-a1e8-2de53fd3b74a key COREDEV-4876
Testing the Package Externally
...