SCORM troubleshooting

Troubleshooting guide for SCORM files

Refer to this article to troubleshoot common issues that may arise when importing SCORM files.  

1. File import has failed  

The issue:

The SCORM file you tried to import could not be uploaded.

Why it happens:

The imsmanifest.xml file is missing or was not placed in the root directory of the ZIP file. Zoho Learn requires this manifest to understand how to load the module. This error may also occur if you zip a folder instead of its contents.

The solution:

  • Ensure that the imsmanifest.xml file is located in the root of the zipped package.

  • Don’t zip the folder containing the SCORM files. Instead, zip the contents of that folder directly.

2. Invalid SCORM version  

The issue:

The SCORM file is invalid and cannot be imported.

Why it happens:

Zoho Learn only supports SCORM 1.2 and SCORM 2004 (3rd and 4th editions). Uploading modules created in other versions will trigger a loading error.

The solution:

  • Return to your SCORM authoring tool.

  • Export or repackage the module using SCORM 1.2 or SCORM 2004 (3rd or 4th edition) format.

3. White page appears while starting a SCORM  

The issue:

When launching a SCORM module, only a blank screen appears.

Why it happens:

SCORM packages may attempt to load content from unauthorized external sources. Modern browsers block such cross-origin requests, especially when third-party cookies are disabled. These restrictions can result in a white screen.

The solution:

  • Ask users to enable third-party cookies in their browser settings.

  • Update your SCORM authoring tool to the latest version and republish the package to comply with modern browser security standards.

Learn more about managing third-party cookies.

4. Access denied: Error 403  

The issue:

Access is denied when trying to launch the SCORM file.

Why it happens:

This can occur due to blocked third-party cookies, which are essential for loading content in some configurations.

The solution:

  • Instruct users to enable third-party cookies in their browser settings.

Learn more about managing third-party cookies.

5. Slow to launch  

The issue:

The SCORM module is slow to load or lags during use.

Why it happens:

This issue is typically caused by an outdated or incompatible browser, which may fail to properly load or run the content.

The solution:

  • Make sure users are accessing the module through a modern, up-to-date browser (e.g., Chrome, Firefox, Edge).

  • Encourage users to clear their cache or try incognito mode if slowness persists.

6. SCORM upload and download errors while using custom domain  

The issue:

SCORM uploads or downloads fail when using Zoho Learn with a custom domain, although other functions may work as expected.

Why it happens:

When using a custom domain, certain SCORM actions rely on third-party cookies. If these cookies are blocked in the browser, uploads and downloads won’t work.

The solution:

  • Instruct users to enable third-party cookies in their browser settings.

Learn more about SCORM upload and download errors