Cry about...
Internet Explorer Troubleshooting

---

An error has occurred in the script on this page

---

Symptom:

When opening a page within Internet Explorer a dialog box is displayed titled ‘Internet Explorer Script Error’ displaying the message:

An error has occurred in the script on this page.

Line:  line-number
Char:  column-number
Error: xyz
Code:  code
URL:   http://abc...

Do you want to continue running scripts on this page?

What the error means:

Internet Explorer is displaying this message because it has encountered this error when trying to run some JavaScript on the page.

Possible Causes and Remedies:

• The problem may be related not with the site but with the contents of Internet Explorer’s cache.

  Internet Explorer may be using some old files from its cache instead of retrieving newer versions from the site. Try deleting all of Internet Explorers temporary files (Tools > Internet Options ... > Delete Files ) and then refresh the page view. If the error persists then it is a fault with the page.

• The page contains a genuine JavaScript error.

  If the page is yours (i.e. one that your are developing or one for which you are the webmaster responsible) then its up to you to debug the problem. Otherwise ignore the error (select ‘No’ to debug) and see if you can carry on.

  This error can be disabled:

  1. Within Internet Explorer select ‘Tools’, ‘Internet Options’.
  2. Select the ‘Advanced’ tab.
  3. Tick the option ‘Disable script debugging’ (under ‘Browsing’).
  4. For the setting change to take effect close down all Internet Explorer windows and then restart Internet Explorer.

  Note: If you are a JavaScript developer (or webmaster) then it is probably wise to leave script debugging enabled.

• This can be caused by malware on your PC. If the problem seems to affect a large number of sites and not just the occasional site then it may well be caused by malware.

  This tip was kindly provided by Catriona Chaplin: "For anyone getting that Runtime error popup all the time despite changing their Disable script debugging setting and the existing MS tips, my recommendation is: Try a complete scan with SpyBot (or similar) first."

---

These notes have been tested with Windows Vista and Internet Explorer 8.