Problem

When attempting to import/upload a SCORM package with the Use Rustici Engine option enabled, the process fails immediately on the front end with the following error message:

Error in importing course to rustici engine [CourseId = EKPXXXXXXXXX-X]

This error typically occurs even if the course uploads successfully without Rustici Engine enabled, or if the exact same file uploads without issue in a non-production (e.g., TEST) environment.

Root Cause

This error indicates that while the primary NetDimensions Learning Management System (EKP) successfully received the uploaded file, the Rustici Engine sub-system failed to process the package, write to its database, or complete the backend registration. Common causes include:

• Backend database or storage permission blocks.

• Indexing issues or cached repository states on the Rustici server environment.

• Backend service timeouts or directory lock issues within the Rustici integration layer.

Initial Self-Diagnostic Steps

Before escalating to support, perform these checks to isolate the issue:

1. Verify Core Application Upload:

   • Try uploading the course package with "Use Rustici Engine" unchecked.

   • If it succeeds, the core LMS application is functioning properly, and the issue is strictly isolated to the Rustici Engine sub-system.

2. Rule Out File Size / Timeout Restrictions:

   • Attempt to upload a small, standard test package (e.g., a simple SCORM 1.2 package under 1 MB).

   • If the small test file throws the same error, the issue is environmental rather than a file-size or network timeout limitation.

3. Compare Environments:

   • Attempt the upload in your TEST/Staging environment using the same settings. If it works in TEST, verify whether both environments are running the same LMS software version.

Solution / Remediation

Because this error typically involves server-level permissions or database index states within the Rustici integration:

1. Server Restart & Index Clear:

   • The hosting/operations team will need to clear backend cache/indexes for the Rustici Engine sub-system and restart the site services.

2. Permission Check:

   • Verify read/write database permissions for the Rustici Engine sub-system on the production application server.

Escalation Guidelines

If the diagnostic steps above confirm that the issue persists across all files (including <1MB test files) only when Rustici Engine is enabled, open a Support Ticket and provide the following details:

• Course ID / Error Trace: The exact CourseId provided in the error message (e.g., EKP000188231-0).

• Environment Details: Confirmation of whether the issue affects PROD, TEST, or both.

• Logs:

  • EKP.log: Any ERROR entries generated during the upload timestamp (accessible via System Administration > System Logs).

  • RusticiEngine.log: Server-side logs filtered for the specific CourseId.