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
Ryan Somma

We are experiencing the same issue. When running a StoryLine course in Chrome or Firefox on our IIS server, the developer's console is filling with 406 errors on each slide transition as it appears the app.min.js is defaulting the .js requests to a content-type of text/html instead of application/javascript as the IIS server is returning. This is happening only with *.js files in the html5/data/js/ folder. We are not having any issues with our other js files. We appreciate any help you can provide on this matter.

Crystal Horn

Hi Philip and Ryan!  I see that Emily worked with you, Philip, to confirm that we're addressing an issue on our end regarding that output.  We've prioritized this issue and hope to be able to release a fix soon.

Ryan, I suspect that the fix will also help you, but you are welcome to submit your file to our support team here for confirmation of this issue.  I'm so sorry for the hangup, but I hope to bring good news soon!

Tony Choo

Hi, im a developer trying to help my client on troubleshooting Storyline Scorm issue. I think we are having the same issue as Philips and Ryan.

We did a trace using chrome developer tools and notice that there are 3 js located in html5/data/js/ folder receiving http 406 response error.

When requesting the file directly, we notice the accept header is set to text. 

Is there any workaround for this while we awhile the proper solution? 


Stuart Jones

We've just had this issue raised today to us too. It is a serious issue that needs to be resolved immediately. We've traced the requests and it is exactly the same as the points above.

When will the updated release be available and are there any patches available in the short term? Please set expectations as we are seeing thousands of users affected.

Ashley Terwilliger-Pollard

Hi all, 

I'm sorry for the issues you ran into where in some cases, HTML5 courses could get stuck or stop advancing. It's been fixed in today's update of Articulate 360 - we also included a few important fixes and new features that you'll see in the release notes here.

Just launch the Articulate 360 desktop app on your computer and click the Update button for each application. Details here.

You'll want to publish and re-upload any content to take advantage of the fixes! 

Tony Choo

Great to hear that it have been fixed. We are reaching out to inform our user.

Meanwhile, would also like to explore alternate solution. We have some articulate SCORM which is running for sometime, in such case there are implication for us to republish and re-upload the SCORM package.

Could you advise us if we can change the package manually to fix this issue?

Katie Riggio

Hello, all! 

I wanted to share that we released a new update for Storyline 3 – you can check out the new features and fixes in the release notes here!

One of the fixes addresses an issue where some slides after the first one would not load/advance in the HTML5 output.

You can download the latest update of Storyline 3 here! Let us know if you run into any trouble – either here or by reaching out to our Support Engineers directly!

This discussion is closed. You can start a new discussion or contact Articulate Support.