Stack overflow at line: 7

Feb 18, 2014

Hello,

I updated my articulate yesterday, and today when publishing I get a "Stack overflow at line: 7" error when attempting to launch index_lms.html. I have made no other adjustments to my machine. I have not been able to find any possible resolutions online.

Any insight is greatly appreciated.

25 Replies
Leslie McKerchie

Hi April and Jen!

Be sure that you are not viewing your content locally, but from your LMS as your user would.

If you view published Articulate Presenter content on your local hard drive or send it to someone else to view on their local hard drive, you'll encounter security restrictions from the computer, web browser, Flash Player, and network that'll cause various features to fail. To test your content and share it with others, you'll need to upload it to the environment for which it was published. Here's how.

You can also check out the blog post here for common LMS issues.

Jacob Berger

Why is this problem all of a sudden occurring?  It is only occurring for content published by new installations of Articulate Presenter.  I say that because we are only experiencing this issue with content published by our newest developer that recently downloaded Articulate Studio '09 Pro from a link provided by Articulate Support.

This is a major issue as we can no longer easily launch content from the SCO pages within our LMS.

Are there any fixes available for this issue?

Thanks!

Christine Hendrickson

Jacob,

I sincerely apologize for the delay - I'm not sure how we missed your message. If you're still having trouble with this, please let us know.

Brian,

Welcome to the community! I'm sorry to hear that you're running into this issue as well.

I was able to find your support case (#00396468 for my reference) and I see that Gren is currently working with you on this issue. It looks like she recently requested your file and should be getting back to you with her testing results. 

Thank you!

Brian Singleton

Thanks for the reply Christine,

We're hearing from many of our clients of this error message.   Strange thing is the problem in not occurring with many users and we're unable to duplicate the error message from our testing sites.   We've worked with some of our users having this problem hoping it was a cache problem....didn't fix the problem.

We've uploaded a sample to your team and all tests ran and tracked to the test LMS ok?

This is a major problem for us as we're quickly loosing our customers confidence.   Any ideas on what might be going on?

Thanks!

Brian

Jacob Berger

Christine Hendrickson said:

Jacob,

 I sincerely apologize for the delay - I'm not sure how we missed your message. If you're still having trouble with this, please let us know.

Christine, I am still having this problem.  It appears the problem may have crept in with the update-10 version of Articulate Studio '09.  Courses that co-workers publish with the update-9 version do not seem to have this problem.

Christine Hendrickson

Hi Brian,

I was able to find the most recent support case (#00396468 for my reference) and I see that Gren was working with you on this. Looks like she was able to publish and upload multiple versions for testing and they worked properly. She did provide some additional suggestions in her last message and I'm curious about whether you've had the opportunity to try them:

"You can ask the users to test the above links to the courses, and also download the published outputs and upload them to your LMS. Test if the same issue occurs as well when the users view these courses. Lastly, please try following the instructions on how to publish properly to AICC (make sure that the Filename(URL) field is properly setup), then republish and test your output, or try publishing to Scorm if your LMS also supports this."

If so, could you share the outcome here, or in a message to Gren, so we can continue working with you?

Thank you!

______________________________________________________________________________________________

Hi Jacob,

Is there any chance you could have one of your colleagues running update 9 publish this module? I realize that might be a lot to ask, but if it works properly after publishing from that specific version, we could see about some additional testing and see if we can get the earlier installation for you. 

It's a little difficult to test on our end, mainly because from the reports here it seems to be happening only for specific users and in specific environments. If you could share some additional information about the machines and browsers used to access the course that experienced this issue, it would also help. 

Thanks!

Christine Hendrickson

Hi Jacob,

Thanks for that information and confirming.

Are you able to test in either a different version of Internet Explorer, or a different browser such as Google Chrome, Firefox or Safari? 

I don't have Internet Explorer 8 on this machine to use for testing, but I can certainly look into using an environment with that specific build, if you'd like me to test this on my end. Are you able to share a link to the module that's available through your LMS?

Jacob Berger

Currently, I am unable to test with a different version of IE and don't have access to Chrome or Safari at work.

When testing in Firefox 24.5, both the modules published with update 9 and those published with update 10 produce the following error message:

An error has occured:

ERROR - LMS returned an error -    DisplayError(strErrorMessage); -    if (strLine.toLowerCase().indexOf("error_text") > -1){

Press 'OK' to view debug information to send to technical support.

Unfortunately, you'd be unable to access a link to the module because of our firewall.

Christine Hendrickson

Hi Jacob,

Which LMS are you using? It sounds like you may be using an in-house LMS, is that correct?

Does your LMS, or your project, use a launch page? 

I understand if the firewall prevents me from accessing the module on your servers. Are you able to share an Articulate Package for the project so we can test the file? If you can, you're welcome to attach the file here. If not, you can share it privately through this form.

Please add ::christine:: in the description and/or title of your support case. This will ensure the case is assigned specifically to me, so I can take a look. If you'd rather have our support engineers test your file, please share the case number so I can follow the progress.

Thank you!

Jacob Berger

Christine,

We use the TEDS LMS.  However, this error occurs when launching the course with the index_lms.html file from anywhere (including my hard drive) except when actually launching it as a student through the normal course enrollment process in our LMS.

Though I don't see where it indicates that I did so, I attached a zip file with the course files (just a dummy course for illustrative purposes) and a screenshot of the error that we receive...  Please confirm that you received the files.

Thanks!

Christine Hendrickson

Hi Jacob,

Thanks for the additional information and the file!

Correct - you can, however, insert screenshots into your response by using the "insert image" option. Only one file attachment is allowed per post at the moment.

However, it looks like you shared the published output of the project and not the Articulate Package. Any chance you could share this?

Also, could you please let me know if you're publishing for AICC, as well?

I'll take a look as soon as possible.

Thanks, Jacob!

Art Allen

Hello,

I'm experiencing this same issue, under the following scenarios:

1) created a new course in Update 10, viewed it on a PC running WIN 7.0.2 with IE 8 = Stack Overflow line 7

2) opened a course (created in Update 7) in Update 10, saved it, published it, viewed it on a PC running WIN 7.0.2 with IE 8 = Stack Overflow line 7

I published both courses to our Towers Watson LMS ("Talent | Reward") using the AICC parameter.

When viewing both courses in IE10 (still on a PC running WIN 7.0.2) there are no problems.

Our company has 50,000+ employees and the IE10 rollout onto the existing WIN 7.0.2 PC build will obviously take a few weeks. (We are not going to WIN 8 at this time). If the above scenario persists, users who have not yet migrated to IE10 will be unable to view courses updated via Articulate Update 10. 

We're anxiously awaiting some direction / fix for this problem.

Christine Hendrickson

Hi Art,

Welcome to the community!

Sorry to hear that you're running into this issue.

I'm a little confused by some of the statements you posted, so I just want to see if I can clarify a few things. 

You mentioned that after uploading both of the course to the LMS with AICC and running in Internet Explorer 10, you saw no problems. Can you please confirm that you tested the version that was uploaded to the LMS fails in Internet Explorer 8, as well? It looks like you viewed both versions locally using IE 8 - I just want to make sure these were tested on a server and not just locally. 

If they were both uploaded to your LMS and display the error in Internet Explorer 8, it might be best if we could take a look at the files. You're welcome to share the Articulate Packages here on the forums, but keep in mind that there's a limit of one attachment and the max file size is 20MB. 

If you'd like to share your packages privately, or if they're too large for the forums, you can share them through a support case. The support case will be submitted to our support engineers. However, if you'd like me to personally take a look, just add ::christine:: to your case description. If you decide not to share the file with me, please share the support case number so we can keep an eye on the progress and share updates here on the forums for others experiencing this issue. 

Best,

Christine

Art Allen

Yes, Christine, the courses were uploaded to the LMS and failed when viewed in Internet Explorer 8. Sorry that wasn't clear.

One of my colleagues did some additional research this morning and learned that the stack overflow relates to a javascript (Ajax) issue where a course is published to a non-secure (http) server and then presented by the LMS, which is on a secure (https) server. Publishing to a non-secure server results in the javascript mis-match and the Stack Overflow error.

His team's course updates worked fine and did not present the error because they publish to a secure server. That is because some of their viewers are outside the firewall, whereas many of us publish to a non-secure server because our audience is entirely internal. 

I'll share the files via a support case to your attention. 

Art

Christine Hendrickson

Hi Art,

Thank you very much for the additional information and for sharing the files. The support case number, for my reference, is 00405330.

My concern is access to a non-secure server. The Articulate site servers have recently been changed to secure and SCORM Cloud (where we do most of our SCORM testing) is also a secure server, I believe. 

However, this information is certainly helpful! I'm curious to see if Alan and Jacob can respond and let us know if they're also uploading to a non-secure server with their content. 

Are you using a public, non-secure server, or is it internal only?

Thanks again,

Christine

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