dman
Perch
I have some clients and sites that still run Classic ASP and I'm seeing an issue with the runtime errors on several sites. The runtime error is returning an incorrect line number. This is happening on more than one site running Classic ASP. In the past these sites have returned runtime errors with the correct line number of the error. When I test this locally IIS returns the correct line number.
Any idea why this is occurring? Is there a problem with the vbscript engine or IIS at Jodohost?
For example:
I purposely created a test page with a runtime error to test this issue. When I go to that page it returns the error below but the actual error is on line 9 not line 17. See the bold text below...
ERROR RETURNED
"Microsoft VBScript runtime error '800a000d'
Type mismatch: 'test2'
/test-error.asp, line 17"
PAGE CODE - see comment for correct lin number.
Line 1: <%@LANGUAGE="VBSCRIPT" CODEPAGE="65001"%>
Line 2: <html>
Line 3: <head>
Line 4: <meta charset="UTF-8">
Line 5: <title>Untitled Document</title>
Line 6: </head>
Line 7: <body>
Line 8: <%
Line 9: test2 "<--- THIS is line 9 not line 17 as shown in the error above"
Line 10: %>
Line 11: </body>
Line 12: </html>
Any idea why this is occurring? Is there a problem with the vbscript engine or IIS at Jodohost?
For example:
I purposely created a test page with a runtime error to test this issue. When I go to that page it returns the error below but the actual error is on line 9 not line 17. See the bold text below...
ERROR RETURNED
"Microsoft VBScript runtime error '800a000d'
Type mismatch: 'test2'
/test-error.asp, line 17"
PAGE CODE - see comment for correct lin number.
Line 1: <%@LANGUAGE="VBSCRIPT" CODEPAGE="65001"%>
Line 2: <html>
Line 3: <head>
Line 4: <meta charset="UTF-8">
Line 5: <title>Untitled Document</title>
Line 6: </head>
Line 7: <body>
Line 8: <%
Line 9: test2 "<--- THIS is line 9 not line 17 as shown in the error above"
Line 10: %>
Line 11: </body>
Line 12: </html>