Common Error Messages

The following table lists common error messages that can occur while you are creating scripts, and possible explanations.

Common Wrrors While Running Scripts

Error Possible explanation

Client browser hangs after requesting
ASP page
  • · Syntax error in an ASP page. If debugging is enabled for the application to which the ASP page belongs, the server invokes the Script Debugger on the server.

Expected end of statement
  • · Misspelled command.

  • · Missing End statement to close If, Function, Sub, etc.

Type mismatch
  • · Call to undefined function (check for misspelled function name, in particular if the error says ôType mismatch: æ<undefined>Æö).

IE cannot open the Internet
site <URL> ... The operation
completed successfully.
  • · Attempt to display an ASP page that generates no HTML output. The script or scripts in the ASP page have executed successfully. You can avoid this error by adding HTML output to the ASP page, or including a Response.Redirect statement to move to a page that does have HTML output.

The HTTP headers are already
written to the client
browser.
  • · Attempt to use Response.Redirect in an ASP page to display a different page after some portion of the current page has already been processed. For example, the server might have already processed and sent the <HTML> tag.