Module not working properly in IIS web server
Mar 13, 2018
My organization was recently provided some content from a 3rd party vendor produced using Articulate Storyline. It works fine when run from a network share, but doesn't work when deployed to our IIS 7.5 server. I checked with the vendor, and they assures me it was produced using "publish to web".
When viewing the network traffic, I see several request to /html5/data/js/...js which are failing with HTTP 406 (Not Acceptable). Looking deeper, the browser is sending an Accept Header "text" on the XMLHttpRequest which is why the server is rightfully refusing to return content which is of type application/javascript.
Is there some setting our vendor should be checking in order to set the correct HTTP headers?
36 Replies
Hi there, Erin. I'm really sorry you're still running into those 406 errors on the published output after the update.
I saw that you submitted a case with your output and .story file attached for our Support Team to dig into. In the meantime, can you let us know what slide(s) you see this behavior on?
I'll be following your case closely – and will share updates on our findings here, as needed!
Hi! Thanks for getting back to me :)
The course plays with no issues in IE with Flash player installed.
In Chrome, the errors are right from the start (the menu). All pages seem to 'work' until you get to the quiz.
There is an easter egg grey square in the bottom right corner of the menu - click that to get to the last page of the materials, go 'next' to complete and return to the menu and the quiz will unlock.
The problem users are experiencing (which I can only reproduce in Chrome) is that when they 'submit' the first answer to the quiz - nothing happens. EDIT: Wooooah - as of this morning the submit button DOES work! That is... peculiar, sorry. But still plenty of errors (see attached!). I'll keep testing it.
Good morning, Erin – and thank you for the extra detail! Every bit really helps.
I've shared this latest information in your support case. You'll be hearing directly from one of our Support Engineers with some next steps, and I'll also share what we find regarding those errors after our testing here!
Fab - my thanks!
Hi, Erin – and those following this thread! Circling back here to note that Anna published and tested the course in multiple environments, in which it could be an issue with the server that's hosting the project. Thanks again for working through this with us!
Keep us posted on what your IT department suggests, and we'll be standing by if you need anything else!
Hi Articulate staff;
In previous versions of Storyline, videos ran fine in the SucessFactors LMS when we tested them in Stage then moved them to Production for review using Chrome.
Now videos work fine in Stage via Chrome but get stuck at video end with a spinning twirl.
Our Stage is on Apache server, Production is on IIS. I understand there is an IIS patch but the problem persists.
Could you help out with this?
Hi Michael,
What version and update of Storyline are you using? The issue you're describing sounds a bit different than some of the previous ones here, so I think it'd be best to work with our Support team so that they can take a look at your files and do some additional testing around it.
I just wanted to chime in here and say we are publishing via Storyline 360 and are also having this issue. Even with courses published in the last month or so, non-stop 406 errors. It is affecting our licensing customer and our internal service. Any word on a fix?
Hi Jason,
Have you already gone through the steps here? We've seen in many instances that folks needed to have their server admin or IT team add those additional MIME types to allow for proper playback.
If it's still not working after going through those steps or you're not able to work with your server admin, I'd want to have you work one on one with our Support Engineers. They'll take a look at your .story file and test publishing it to a few of our servers to compare. You can connect with them and share your file here.
If you need anything else, let me know!
hi Ashley, i'm just discovering this issue. Do the steps you've provided in your link required all content to be republished? OR will those steps work for existing older Articulate published content as well?
I support a large organization that is going through server upgrades that bring the new version of IIS....and also has Articulate content published in LMS that is older than current version (back to Articulate 2 i believe). Is there a work-around?
Hi Eric,
If your server administrator isn't able to add the MIME type, you'd need to make those changes to the published output for all your courses. That article is only for Studio 360, Storyline 3 and Storyline 360. It shouldn't be impacting older courses from Storyline 2.
If you're running into issues with Storyline 2 course playback, do you know what update you used to publish these courses?
This discussion is closed. You can start a new discussion or contact Articulate Support.