Skip to main content
knelarson
Participant
February 23, 2023
Question

Receiving "Bad Request" Error When Client Tries to Upload SCORM Zip

  • February 23, 2023
  • 1 reply
  • 262 views

Hoping to find some clues about what's happening. I made two custom LMS projects for a client - custom meaning I designed stuff in Photoshop then brought it into Captivate. So I'm not using a bunch of Captivate functions, other than buttons and Advanced Actions. I have a few videos throughout.

 

The interesting thing is the larger Module (Module 01) is a larger file size, has more assets, and has reporting at the end. And it isn't giving that error at all. It works fine. So Module 02 is the one we're having issues with - and it's significantly smaller and less complex. So I don't think it's a file size issue.

 

On my end, I can import the ZIP output into a LMS viewer (Review my eLearning) and it works just fine. So I'm just at a loss to figure out why it's working for us, but as soon as they try to import it to their system, it's not working and giving back a generic "Bad Request" error.

 

I'm trying to figure out why system they're using to host/upload these outputs to, but for now, is there anythign on my end or in Captivate that might be causing a "Bad Request" error?

This topic has been closed for replies.

1 reply

Lilybiri
Legend
February 24, 2023

It is not clear to me if you are talking about a SCO or a packaged and zipped output. I will try to explain the difference:

  • SCO: the project is set up to report to the LMS using Quiz Preferences, Reporting with one of the available SCORM or other protocols. In this case the zipping on publishing will be done automatically and almost all LMSs will accept that type of output without issues. Unless of course they do not support the protocol you used.
  • Zipped package: you did not set up Reporting but published to HTML and zipped manually or by activating that option in the Publishing dialog box.  Not all LMSs support upload of such a package. In Blackboard which I used in the past that option is available, and you have to instruct the LMS to unzip the package and to launch from the index.html file.