The following table lists common error messages that can occur while you are creating scripts and possible explanations.
|
Error |
Possible explanation |
Client browser hangs after requesting
.asp file |
-
Syntax or runtime error in an .asp file. If debugging is enabled for the application to which the .asp file belongs, the server invokes the Script Debugger on the server.
|
|
.asp file source appears in browser. |
-
Wrong protocol used to fetch file (file:// instead of http://). Do not open an .asp file as a file in your browser.
|
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 file that generates no HTML output. The script or scripts in the .asp file have executed successfully. You can avoid this error by adding HTML output to the .asp file, 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 file 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.
|