Troubleshooting Common SCORM Cloud Course Import Errors

Encountering an error while importing a course into SCORM Cloud can bring your workflow to a halt. This guide breaks down the most frequent import errors, what causes them, and the steps you can take to resolve them quickly.

1. "Internal error importing course"

Common Causes:

• Malformed ZIP file: The uploaded file is not a valid ZIP archive.
• Invalid manifest structure: The imsmanifest.xml file is missing, malformed, or not located in the root directory.
• Missing required files: Essential schema or manifest files are absent.
• File encoding issues: Encoding conflicts in XML or text files.
• Corrupted course package: The file was damaged during creation or upload.

Solutions:

• Re-download or re-export the course from your authoring tool.
• Extract the ZIP file locally to verify it isn't corrupted.
• Ensure the imsmanifest.xml file is located in the root of the ZIP file (not inside a subfolder).
•  Check for special characters in title and file names.
• Try uploading using a different browser or after clearing your cache.
• Test on a different network connection to rule out local network upload drops.

2. "Error opening zip file"

Cause: The file you are trying to upload is not recognized as a valid ZIP archive.

Solutions:

• Verify file integrity by attempting to extract it locally on your computer.
• Re-export or re-package your course from your authoring tool.
• Double-check that the file extension is exactly .zip.
• Try uploading a known working test SCORM package to verify the system is functioning correctly.

3. "A course already exists with the specified id"

Cause: You are attempting to import a course using a Course ID that is already in use within your environment.

Solutions:

• Choose a different, unique Course ID for the new upload. If using the UI, SCORM Cloud will generate a unique course ID if one is not provided.
• If you are trying to update an existing course through the API, be sure to include the mayCreateNewVersion parameter as part of your course import request. (API Documentation)

4. File Type Not Recognized

Error: "A contentType was provided; however, it is not a recognized media type"

Solutions:

• Ensure you are using a supported format: SCORM 1.2, SCORM 2004, AICC, cmi5, xAPI, or supported media files (MP4, PDF, etc.).
• Verify that the correct content type header is being sent in your API request.
• Double-check that you are uploading the actual zipped course file and not an unzipped folder.