Google Chrome Issues

230 views
Skip to first unread message

DJohnson

unread,
Sep 1, 2010, 1:47:02 AM9/1/10
to eLearning Technology and Development
Hey,

I'm using the Pipwerks Interface for AS3 to develop a SCORM-compliant
course, but am noticing some very strange behaviour when running it in
Google Chrome (such as failing to connect but still saving SCORM data
but not reading it).

I've even scaled this back to the bare bones Pipwerks JavaScript
wrapper demo on the website, but when loading it onto Moodle 1.9, it
works fine in IE and FireFox but Google Chrome (5.0) always fails to
connect to SCORM. I always get the generic useless error description:

"SCORM.connection.initialize failed.
Error code: 101
Error info: General exception"

Any ideas? Thanks.

Philip Hutchison

unread,
Sep 1, 2010, 2:10:22 AM9/1/10
to elearning-technolo...@googlegroups.com
Hi David

If you're getting an error code, it means the SCORM connection worked well enough to get a return value from the LMS (the error code itself), but some part of the communication failed.  Unfortunately, a 101 error is a vanilla error code that means "something went wrong but it doesn't fall into any of the other categories". It doesn't really help us diagnose the problem. Try adding a call to getDiagnosticInfo in the pipwerks wrapper... sometimes the LMS provides additional information:

Edit this line:
trace(traceMsgPrefix +"failed. \nError code: " +errorCode +" \nError info: " +debug.getInfo(errorCode));

to read:
trace(traceMsgPrefix +"failed. \nError code: " +errorCode +" \nError info: " +debug.getInfo(errorCode) +"\nDiagnostic info: " +debug.getDiagnosticInfo(errorCode));

LMS vendors have the option of supplying diagnostic info for each error code, but they aren't under any obligation.  Keep your fingers crossed.

- philip




--
You received this message because you are subscribed to the Google Groups "eLearning Technology and Development" group.
To post to this group, send email to elearning-technolo...@googlegroups.com.
To unsubscribe from this group, send email to elearning-technology-and...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/elearning-technology-and-development?hl=en.


DJohnson

unread,
Sep 1, 2010, 2:39:48 AM9/1/10
to eLearning Technology and Development
Thanks for the advice.

I should've mentioned this in my original post but I did try pulling
the LMS Diagnostics and received the extra-useful information of the
error code: "101" again! Which isn't overly helpful.

My continual trial & error debugging has revealed some more
information though, it appears that if I select the option to display
the SCO in the current frame, it connects and works fine, but when I
select the "new window" option so the SCO opens up in another window,
that's when it fails.

I've also tested in Ilias which appears to work fine across all
browsers. However, it fails to even find the API in Moodle 2.0 (in any
browser) - has anyone tested the SCORM Wrapper in Moodle 2.0 before?

Cheers,
Dave
> > elearning-technology-and...@googlegroups.com<elearning -technology-and-development%2Bunsu...@googlegroups.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/elearning-technology-and-development?h....

amy groshek

unread,
Sep 1, 2010, 9:31:09 AM9/1/10
to elearning-technolo...@googlegroups.com
Moodle 2.0 is itself still in development.
"This development version is nearly feature-complete now but UNSTABLE
and should not be used for production sites."
http://download.moodle.org/

You shouldn't be using 2.0 to test content you're just developing
yourself. Use the latest stable build of 1.9. If you find a legitimate
bug in Moodle 2.0, however, it's helpful if you log it at
tracker.moodle.org so we can replicate and fix.

Regards,
Amy

> To unsubscribe from this group, send email to elearning-technology-and...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/elearning-technology-and-development?hl=en.
>
>

Reply all
Reply to author
Forward
0 new messages