Issues with Articulate Presenter '09 'index_lms.html' Launch File

Jul 31, 2014

Hello,

I am having an issue viewing content published for an LMS (AICC standard). When I launch the index_lms.html file on my local machine or from within our LMS, it loads a blank screen and then stalls. I've reviewed content published by my colleagues using the same software, and I am able to successfully launch the content using the same method in their output files.

I've tried narrowing down the causes--I used existing PPTs, and created new ones from scratch. I tried even changing the base PPT file to the 2000-2003 format before publishing, and I still get the same result.

There are two more details to note:

- I am able to view the content successfully if I launch the 'player.html' file instead; the only problem with this, of course, is that our LMS will not be able to track the content if I use this as an alternative.

- If I publish using the same basic settings in Articulate Storyline, I am able to launch the file without issue using the "index_lms.html" file.

Any suggestions would be greatly appreciated!

3 Replies
Justin Grenier

Good Afternoon Adam, and welcome to Heroes!

If you see only a blank window when launching an Articulate course in your learning management system (LMS), the issue may be related to the specific version of Java Runtime Environment installed on your computer. Please review this article for more information.

Good luck on your project!

Adam Yerger

Thank you for your prompt reply!

I will investigate the Java Runtime Environment installed on my computer, however, I doubt that is the cause of the issue since I am able to view other presenter modules launched from within the same LMS system that were published by other people. In addition, the blank window issue occurs on my local drive as well, but again, only for modules published on my computer. I am able to view others' published output locally as well.

V6.3.1402.0316 Pro Update 10

Thanks again!

Justin Grenier

Hello again, Adam.

If you determine with certainty that the problem is unrelated to which machine views the content and is instead firmly linked to which machine publishes the content, it sounds like you are dealing with a publishing problem on your machine.

In this case, you might consider a simple repair. If that doesn't work, you can get a bit more aggressive.

Please let us know if you need anything else, and have a great day!

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