Troubleshooting: Course Conversion

The following errors might be encountered during course conversion into D2L format. Try these troubleshooting steps first, and if they don't work, contact support for a more in-depth investigation of the issue.

Error: Package was not recognized

A package may be not recognized if:

  • It is not in a course archive format (for example, it is a .ppt or .pdf file instead of a course package exported from an LMS).
  • It was exported from a vendor that is not yet supported by D2L.
  • It failed to unzip.

Package Failed to Unzip

Symptoms

When importing a course package, you encounter the message: "The package was not recognized". The processing logs indicate "Unpackaging uploaded file" followed by "Unsupported file format". If the package was successfully unzipped, the processing logs would indicate "Successfully unpackaged file" instead.

The processing logs also indicate that the final status of the issue was "NoConversion". You can access the processing logs directly on the error page in Course Import by clicking on "View Processing Logs".

Cause

The following are common causes of this error: 

  • The package is not a valid archive file (for example, .zip, .mbz, .imscc, etc. which have been exported from an LMS). Verify that the file is an Archive or Compressed Folder file type before attempting your course import. The following file types are not valid for importing a course: .pdf, .ppt, .docx. If you are trying to add course content, use Content Tool - Add Module instead.
  • The course package does not have an imsmanifest.xml at the root level and it may instead be located in a sub-folder.
  • The course package contains files paths that are longer than 128 characters which is a Windows limit.
  • An archive file has been corrupted or damaged.

Resolution

If you are using an archive file, to verify your course package can be extracted, try to unzip the package locally first. Try the following steps to resolve the problem:

  1. Use the built-in operating system extraction program and try to unzip the file on your computer.

    If you successfully unzipped the package on your local computer, re-zip the file using your local operating system zip program or the program you were using. Retry the course import with the newly zipped package.
  2. Unzip the package and examine the folders structure to ensure that the imsmanifest.xml file is at the root level. If the imsmanifest.xml file is not at the root level move the file to this location and re-zip the package and retry the course import.
     
  3. Use WinRAR (http://www.rarlab.com/) to unzip the file on your computer.

    Your package may contain file paths longer than 128 characters. In this case, most extraction programs on Windows will fail. WinRAR will still extract the files, but will warn that files exceeding the maximum path length were truncated. Once the extraction is complete, it is recommended that these paths are truncated manually or removed. Then re-zip the files and retry the course import.
     
  4. Re-export your course package from the original source.

    If neither of the previous troubleshooting steps worked and the extraction still fails, your course package is likely damaged. Re-export the course package from the original LMS and retry the course import with a newly exported package.

Error: Package was not converted

This error commonly arises due to issues within the course package itself:

  • There may be key files missing (for example, imsmanifest.xml is a typical file expected to be among the course package structure).
  • There may be issues with XML in some of the files (for example, the files may have illegal characters or unmatched opening and closing brackets).

Typically in these cases, it is recommended to review the processing logs and inspect the specific complaint. Then explore the contents of your package to verify that the information is corrected. You can also try to re-export the package from the original source.

Invalid HTML

Symptoms

When importing a course package, you encounter the message "The package was not converted". The processing logs may indicate that an invalid or unexpected character has been encountered.

The processing logs also indicate that the final status of the issue was "ProcessingFailed". To access the processing logs directly on the error page in Course Import, click View Processing Logs.

Cause

Invalid XML can often cause conversions to fail. Sometimes the error directly names the exact file that is causing the problem. If it is not explicitly stated, try the main imsmanifest.xml file. If the manifest is improperly formed, serious issues may occur.

Resolution

To verify that an XML file is valid:

  1. Open the file in Google Chrome. If the XML is valid, it should render correctly; if not, the page will remain blank or report an error.
  2. Use an online XML validator like: http://www.xmlvalidation.com/
  3. If the XML is invalid, correct the XML, re-zip the package and retry importing your course package.
  4. the XML is valid, the issue with your package is likely in the structure of the package (for example, missing key files). In this case, re-export the package from the original source and retry importing your course package.

Error: Conversion Service is Temporarily Unavailable

If the Conversion Service is not available, it may relate to temporary issues that are being monitored by D2L support and will be resolved shortly. However, if you repeatedly see this error message, it may be worth verifying that the Conversion Service URL is properly configured. This can only be done by D2L support representative.