Sometimes SCORM packages are returning some issues in the used LMS. For example, there could be issues loading the content, or incorrect tracking.
In such cases, it is a good idea to run some troubleshooting, before reaching out to us, as the issue could be with the package itself or its content.
In here, we provide some steps you can follow, in order to troubleshoot issues with your SCORM file - you do not need to follow them all, but some of them should be easy to complete:
- Check if the package works on other systems.
- Check your SCORM version, and verify if it is compatible with the one supported by your LMS provider. This can be done by checking the XML file in the package, or by checking with your SCORM provider
- If possible, validate your SCORM package. A SCORM package can have many types of file, and the XML file in it delivers information about them. If this file is corrupted somehow, or invalid, the course will not work as expected. In order to verify your package, you can use online tools. This can be done through external providers, such as SCORM cloud.
- The issue could even be with the SCORM code - the code that makes sure the course can 'communicate' with the LMS system you are using (for example Emply). If that code is faulty, the course will not work as expected. SCORM code can be reviewed and debugged by your IT department, or through the use of online tools.
- Make sure your browser and plugins are up to date. Outdated tools, browsers and plugins can be at fault, when content is not rendered as expected, as they can affect course content. If you have browser or plugins that are outdated, incompatible or blocked, the course will not be loaded, or won't work.To avoid this, you should update your browser and plugins to the latest versions and make sure they are compatible with your LMS and your SCORM version. You should also check your browser settings and disable any pop-up blockers, ad blockers, or security extensions that may interfere with your course. If possible, you can also try a different browser, and check if that solves the issue.
If everything you have checked is as it should be, and the issue still persists, get a hold of us, making sure to deliver the following information:
1. Nature of the issue
2. How to reproduce it
3. SCORM package
4. List of what has been troubleshooted, and results (for example what version the package is, or what browser and version is used)