I published a Storyline course and all works well. I selected "Include HTML5 output" to try that out, but when I attempt to view the output, my browser (Chrome) throws the following error: "The page at file://localhost/ says: Error loading story_content/data.xml: error".
Has anyone encountered this? If so, what could be causing this and are there any known workarounds or solutions?
Thanks,
Eric Rohrer
Helix Knowledge | a digital learning design agency
Hi Will! Sorry for the inconvenience. Looks like the site is back up now.
It doesn't always give an error - sometimes the content just gets displayed incorrectly. Sounds like you share my sentiments about IE - and it's why I prefer Chrome :)
Sorry about the website black out - but you should be able to get there now.
If a user is trying to access content that was published from Storyline (including the HTML5 output) and they're viewing it in IE (any version) they'll want to have Flash enabled. If not, it'll default to showing the HTML5 output which is either going to provide the error message or provide a experience with the content that doesn't always work as expected.
Hi All! After the recent discussion here, I just wanted to pop in with an update in case you didn't see the news yesterday :)
In Storyline 360, you can choose which formats are included in your published output—HTML5, Flash, and/or Articulate Mobile Player.
Click the Formats property on the Publish window to open this Publish Formats dialog.
Use the Publish As slider to choose one of these options:
HTML5: This publishes your course as HTML5 output only.
HTML5/Flash: This publishes your course as HTML5 first with Flash fallback. Learners will see HTML5 output if they’re using a supported HTML5 browser. If not, they’ll see Flash output.
Flash/HTML5: This publishes your course as Flash first with HTML5 fallback. Learners will see Flash output if they’re using a Flash-enabled browser. If not, they’ll see HTML5 output.
Flash: This publishes your course as Flash output only.
Some users are having trouble loading the course in LMS Cornerstone. (see image error)
Some slides are not loading their elements correctly either. They're out of place and proposition, some are not loading at all, and some are loading on the wrong slide, it seems. (see image loading).
Story file is 54 MB. Output is Flash. We tested the course in IE 11, Chrome and Firefox in Windows 7. We are unable to replicate these bugs that are happening to our users and need to solve this urgently.
Hi Daniela! You mention being unable to replicate and how you tested the content, but do you know the browsers/environment that the users were utilizing?
The first error looks like an error when the content is being uploaded, is that correct? Are the users with an issue the same ones uploading? Perhaps they are not viewing the content in the intended environment and still viewing locally? Just brainstorming.
I'd advise to upload the content to SCORM Cloud to see if the user experiences the same issue.
The course is on our LMS - Cornerstone. Our learners have restricted internet access (for security reasons). They are unable to test the course in Scorm Cloud. We have tested the course in our LMS and never had trouble loading or viewing the course. Our learners are accessing the course in IE10.
Do you have the .story file so that I could take a look perhaps? If you cannot share here in the forums, you are welcome to share here with our support engineers privately.
Has anyone found a solution to this? My course is 7MB and has some animations (fly in, appear) but no video. Most slides are a click and reveal showing a different state of a button or image. It is very basic. Some users are getting the error while some are not.
I have republished and had a co-worker publish. Users have tried in Chrome and IE.
Sorry to hear that you've run into an issue with your course. You're getting the same error the original author got in their course?
Do you experience the same error if you test the content in SCORM Cloud or is this limited to your LMS? Any consistency in replicating that we could follow if you were to share your .story file?
I'm one of Donna's coworkers. I have been tinkering with the Storyline file and I found something interesting.
This is a 5 scene course. If I only publish scenes 1, 2 and 3, it works fine. if I publish scenes 4 and 5 together, it works fine. When I publish all 5 scenes together, I get the error.
After a lot of researching and testing this was the solution needed:
From our IT guy: "The file was being blocked by the anti-malware in our proxy server.
It gave this reason: BehavesLike.JS.ExploitBlacole.dv
This is a generic description for detection of malicious javascript that looks similar to malicious javascript that was commonly seen being served from compromised web servers over 5 years ago. I grabbed a copy of this data.js file from the LMS website and analyzed it against a battery of anti-malwares at VirusTotal and it came back clean.
This is likely a false positive in the proxy’s anti-malware engine. However, I can’t say that I’m 100% certain that the LMS server is not serving up potentially malicious javascript."
He whitelisted that from the proxy and it resolved the issue!
66 Replies
Hi Will! Sorry for the inconvenience. Looks like the site is back up now.
It doesn't always give an error - sometimes the content just gets displayed incorrectly. Sounds like you share my sentiments about IE - and it's why I prefer Chrome :)
Hey Will,
Sorry about the website black out - but you should be able to get there now.
If a user is trying to access content that was published from Storyline (including the HTML5 output) and they're viewing it in IE (any version) they'll want to have Flash enabled. If not, it'll default to showing the HTML5 output which is either going to provide the error message or provide a experience with the content that doesn't always work as expected.
Hi All! After the recent discussion here, I just wanted to pop in with an update in case you didn't see the news yesterday :)
In Storyline 360, you can choose which formats are included in your published output—HTML5, Flash, and/or Articulate Mobile Player.
Check out this link for the full tutorial.
We have the same issue.
Some users are having trouble loading the course in LMS Cornerstone. (see image error)
Some slides are not loading their elements correctly either. They're out of place and proposition, some are not loading at all, and some are loading on the wrong slide, it seems. (see image loading).
Story file is 54 MB. Output is Flash. We tested the course in IE 11, Chrome and Firefox in Windows 7. We are unable to replicate these bugs that are happening to our users and need to solve this urgently.
Hi Daniela! You mention being unable to replicate and how you tested the content, but do you know the browsers/environment that the users were utilizing?
The first error looks like an error when the content is being uploaded, is that correct? Are the users with an issue the same ones uploading? Perhaps they are not viewing the content in the intended environment and still viewing locally? Just brainstorming.
I'd advise to upload the content to SCORM Cloud to see if the user experiences the same issue.
Dear Leslie,
The course is on our LMS - Cornerstone. Our learners have restricted internet access (for security reasons). They are unable to test the course in Scorm Cloud. We have tested the course in our LMS and never had trouble loading or viewing the course. Our learners are accessing the course in IE10.
Do you have the .story file so that I could take a look perhaps? If you cannot share here in the forums, you are welcome to share here with our support engineers privately.
This post was removed by the author
Hi Donna,
It looks like maybe all of your response didn't come through? If you need help, just let us know with what!
Has anyone found a solution to this? My course is 7MB and has some animations (fly in, appear) but no video. Most slides are a click and reveal showing a different state of a button or image. It is very basic. Some users are getting the error while some are not.
I have republished and had a co-worker publish. Users have tried in Chrome and IE.
Hey Donna,
Sorry to hear that you've run into an issue with your course. You're getting the same error the original author got in their course?
Do you experience the same error if you test the content in SCORM Cloud or is this limited to your LMS? Any consistency in replicating that we could follow if you were to share your .story file?
I am going to attempt to access an earlier version to see if that will resolve anything as all other resolutions have failed.
Sounds great Donna.
If you need the help of our support team, you can reach out here.
I'm one of Donna's coworkers. I have been tinkering with the Storyline file and I found something interesting.
This is a 5 scene course. If I only publish scenes 1, 2 and 3, it works fine. if I publish scenes 4 and 5 together, it works fine. When I publish all 5 scenes together, I get the error.
Hi Lisa,
Thanks for chiming in with an update.
Curious if the issue happens in any course you are working on or just this particular one?
If you cannot re-create the issue in a new course, I would advise to import the file into a new one and proceed.
If it's happening in any/all files, you should certainly conduct a repair of your software.
After a lot of researching and testing this was the solution needed:
From our IT guy:
"The file was being blocked by the anti-malware in our proxy server.
It gave this reason: BehavesLike.JS.ExploitBlacole.dv
This is a generic description for detection of malicious javascript that looks similar to malicious javascript that was commonly seen being served from compromised web servers over 5 years ago. I grabbed a copy of this data.js file from the LMS website and analyzed it against a battery of anti-malwares at VirusTotal and it came back clean.
This is likely a false positive in the proxy’s anti-malware engine. However, I can’t say that I’m 100% certain that the LMS server is not serving up potentially malicious javascript."
He whitelisted that from the proxy and it resolved the issue!
My goodness.
Thanks so much for chiming back in with an update Donna. Glad you were able to track it down.
This discussion is closed. You can start a new discussion or contact Articulate Support.