Posts: 5614 Joined: 3/14/2005 From: Living on the edge Status: offline
Strange ASP error message - 7/14/2006 13:32:13
Okay, so here I am in the ASP lounge - eek! It's a bit posh in here isn't it?
I'm having a few slight (read massive) problems with a couple of ASP pages. Said pages are residing on the server where they should be, but when I try to view them online, I get the following message:
quote:
HTTP 500.100 - Internal Server Error - ASP error Apache/1.3.27 (Unix) (Red-Hat/Linux) Sun-ONE-ASP/4.0.0 mod_ssl/2.8.12 OpenSSL/0.9.6b
Technical Information (for support personnel)
* Error Type: Active Server Pages, ASP 0140 (0x80004005) The @ command must be the first command within the Active Server Page. /~ret26/eca/cust_log_in.asp, line 6
* Browser Type: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
* Page: GET /~ret26/eca/cust_log_in.asp
* Time: 13 July 2006, 21:21:08
* More information: Sun ONE Active Server Pages Support
Logic would seem to suggest that it's meaning that the first line of the script should be "<%@LANGUAGE="VBSCRIPT"%>" - which it is. I even get the same message when I try to use a page's code I know's okay with that same filename (a page that works with a different filename). I'm guessing this is a server/filename problem, but I've no idea really.
My knowledge of ASP is basic to say the least and this has got me totally stumped. Any suggestions?
_____________________________
~~ "A cruel god ain't no god at all" ~~
rdouglass
Posts: 9272 From: Biddeford, ME USA Status: offline
RE: Strange ASP error message - 7/14/2006 13:38:02
Do you have an include file somewhere with the @ command in it?
That one has got me before..
EDIT: and actually IIRC it should be the first line of the page and not just the script.
Posts: 5614 Joined: 3/14/2005 From: Living on the edge Status: offline
RE: Strange ASP error message - 7/14/2006 13:59:48
Yep, it's the first line of the page. There is an include file, but it doesn't have the @ command in it. What's puzzling me is why the same page, with a different filename, is working just fine.