Hi, I am having issues with my course as it just does not load? 
It would be helpful if you provide more information. What version of Moodle? What did you use to author the package? How is your site hosted?
hi rob, sorry am new to this.
PHP Version 5.4.9
Moodle 2.4
Ispring pro
Ive loaded a test course and that worked however since then i am able to view the outline of the slides but no actual prsentation it doesnt go pass the load state
Hey Michael,
I'm experiencing a similar problem. Running a LAMP server. Moodle 2.4. Packaging SCO's with 'Reload Editor'. I need to upload the SCORM package.zip file twice (overwrite the first upload) before my SCORM packages will play.
Once the student runs throught the course and the LMS gets the 'completed' status for the module it fails to load if launched again, just get that blank grey screen with the course structure to the left.
Anyone experiencing similar issues?
Seems like these threads are talking about very similar issues
https://moodle.org/mod/forum/discuss.php?d=219032
https://moodle.org/mod/forum/discuss.php?d=219964
https://moodle.org/mod/forum/discuss.php?d=219687
https://moodle.org/mod/forum/discuss.php?d=219617
Checking if MDL-37424 is a fix, not sure as my build is 2.4+ 20121208
https://tracker.moodle.org/browse/MDL-37424
If your SCORM player components (TOC, SCORM container, etc) are generated in the page, then the likely culprit is either zlib compression or the new filtering settings in M23 which allow filters to be applied to uploaded content. For those cases, try disabling zlib compression and turning off filtering for uploaded files.
If your SCORM player components are not generated in the page, and you have a JS error regarding setData (Chrome) or thisselect (Firefox) (attaching screenshot), then check out MDL-37397.
If your SCORM player components are not generated in the page, and you have a JS error regarding setData (Chrome) or thisselect (Firefox) (attaching screenshot), then check out MDL-37397.
Thanks for your help Amy,
However my problem doesn't seem to be related to the above tracker ticket. It seems frivolous, but it appears I needed to select the check box 'Start new attempt' before entering the SCORM package the second time round
Is it necessary to keep that check box? Shouldn't entering/re-entering the SCORM package be enough for a student to commit to a new attempt?
Anyway, thanks again
Hi Jarred,
Take a minute to congratulate yourself on having such a simple problem.
You can set the Moodle SCORM activity to only allow a single attempt or set the number of (multiple) attempts allowed. But in order for there to be multiple attempts, rather than editing the settings of the existing attempt during SCO launch, the end-user does have to indicate that a new attempt is desired. That lets Moodle know to serve up a blank set of SCORM API data to the active SCO, so that, for example, rather than lesson_status of "completed," the SCO again gets a lesson_status of "not started".
Another option is to configure your SCORM package so that users can still access the content even after lesson_status is set to completed. It really depends on what your goal is for your end-users.
Regards,
A
Take a minute to congratulate yourself on having such a simple problem.
You can set the Moodle SCORM activity to only allow a single attempt or set the number of (multiple) attempts allowed. But in order for there to be multiple attempts, rather than editing the settings of the existing attempt during SCO launch, the end-user does have to indicate that a new attempt is desired. That lets Moodle know to serve up a blank set of SCORM API data to the active SCO, so that, for example, rather than lesson_status of "completed," the SCO again gets a lesson_status of "not started".
Another option is to configure your SCORM package so that users can still access the content even after lesson_status is set to completed. It really depends on what your goal is for your end-users.
Regards,
A
https://tracker.moodle.org/browse/MDL-37424
Was a fix for us. It does look like this was more properly fixed in:
https://tracker.moodle.org/browse/MDL-37397
With the fix applied to 2.3.4+ already. So we'll have to reverse this fix before upgrading to 2.3.5 when it is released.