IIS 6.0 ASP error 0201

I'm getting an error 0201 from an ASP script. This *used* to work until
recently.

I've done the obvious things:

- checked the permissions on ASP.DLL and VBScript.dll
- re-registered the DLLs
- set failure audit on the DLLs for the IUSR_ account
- re-installed the Scripting package

Nothing seems to work. I don't get a failure audit entry, but it still
tells me that my default scripting language is invalid.

Short of tearing down the machine and doing a complete rebuild, I'm stuck
for ideas. Any thoughts?

Bob
Mon Nov 13 05:37:23 CST 2006

Marc Wilson wrote:
> I'm getting an error 0201 from an ASP script. This *used* to work
> until recently.
>
> I've done the obvious things:
>
> - checked the permissions on ASP.DLL and VBScript.dll
> - re-registered the DLLs
> - set failure audit on the DLLs for the IUSR_ account
> - re-installed the Scripting package
>
> Nothing seems to work. I don't get a failure audit entry, but it
> still tells me that my default scripting language is invalid.
>
> Short of tearing down the machine and doing a complete rebuild, I'm
> stuck for ideas. Any thoughts?

What is the text of the error message?
What would we need to do to attempt to recreate the problem on our machines?
Does this help?
http://www.aspfaq.com/show.asp?id=2371
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

MarcWilson
Mon Nov 13 07:31:02 CST 2006



"Bob Barrows [MVP]" wrote:

> Marc Wilson wrote:
> > I'm getting an error 0201 from an ASP script. This *used* to work
> > until recently.
> >
> > I've done the obvious things:
> >
> > - checked the permissions on ASP.DLL and VBScript.dll
> > - re-registered the DLLs
> > - set failure audit on the DLLs for the IUSR_ account
> > - re-installed the Scripting package
> >
> > Nothing seems to work. I don't get a failure audit entry, but it
> > still tells me that my default scripting language is invalid.
> >
> > Short of tearing down the machine and doing a complete rebuild, I'm
> > stuck for ideas. Any thoughts?
>
> What is the text of the error message?

Active Server Pages error 'ASP 0201'

Invalid Default Script Language

The default script language specified for this application is invalid.

> What would we need to do to attempt to recreate the problem on our machines?

Try to open an ASP page. If you open it in the browser, you either get
nothing or the above error message. If you open it from Windows Explorer,
the page renders the static content, but the scripted stuff is not expanded;
if you mouseover the links on e.g. localstart.asp, you see unexpanded
variable substiutions.

> Does this help?
> http://www.aspfaq.com/show.asp?id=2371

I'll take a look.

MarcWilson
Mon Nov 13 07:43:02 CST 2006



"Bob Barrows [MVP]" wrote:

> Marc Wilson wrote:
> > I'm getting an error 0201 from an ASP script. This *used* to work
> > until recently.
> >
> > I've done the obvious things:
> >
> > - checked the permissions on ASP.DLL and VBScript.dll
> > - re-registered the DLLs
> > - set failure audit on the DLLs for the IUSR_ account
> > - re-installed the Scripting package
> >
> > Nothing seems to work. I don't get a failure audit entry, but it
> > still tells me that my default scripting language is invalid.
> >
> > Short of tearing down the machine and doing a complete rebuild, I'm
> > stuck for ideas. Any thoughts?
>
> What is the text of the error message?
> What would we need to do to attempt to recreate the problem on our machines?
> Does this help?
> http://www.aspfaq.com/show.asp?id=2371

Yes it does. Weird. It now renders ASP pages successfully again.

I *hate* things like this, when no-one knows why it works- if only because
it could happen on the production server.

If you (or anyone else) ever get to the bottom of this, please post a
follow-up here!

Cheers,

Bob
Mon Nov 13 08:20:36 CST 2006

Marc Wilson wrote:
>
> Try to open an ASP page.

That covers a wide range doesn't it? I see your follow-up so you have
been helped. Your future help requests can be facilitated by providing a
repro script. In this case, the repro script would have been:

<%
Response.Write "Hello, World"
%>

But without seeing your follow-up, I would not have known this. My
initial reply was basically a guess. With the repro script (and the text
of the error message) it would have been a certainty.

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

Bob
Mon Nov 13 08:32:20 CST 2006

Marc Wilson wrote:
> "Bob Barrows [MVP]" wrote:
>> Does this help?
>> http://www.aspfaq.com/show.asp?id=2371
>
> Yes it does. Weird. It now renders ASP pages successfully again.
>
> I *hate* things like this, when no-one knows why it works- if only
> because it could happen on the production server.
>
> If you (or anyone else) ever get to the bottom of this, please post a
> follow-up here!
>
That article has been the standard reply for several years. Given MS
dropping development of ASP, you will need to resign yourself to this
question never being answered. Sorry.

--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

MarcWilson
Tue Nov 14 13:08:01 CST 2006



"Bob Barrows [MVP]" wrote:

> Marc Wilson wrote:
> > "Bob Barrows [MVP]" wrote:
> >> Does this help?
> >> http://www.aspfaq.com/show.asp?id=2371
> >
> > Yes it does. Weird. It now renders ASP pages successfully again.
> >
> > I *hate* things like this, when no-one knows why it works- if only
> > because it could happen on the production server.
> >
> > If you (or anyone else) ever get to the bottom of this, please post a
> > follow-up here!
> >
> That article has been the standard reply for several years. Given MS
> dropping development of ASP, you will need to resign yourself to this
> question never being answered. Sorry.

Dropping it in favour of ASP.NET, presumably?

MarcWilson
Tue Nov 14 13:08:02 CST 2006



"Bob Barrows [MVP]" wrote:

> Marc Wilson wrote:
> >
> > Try to open an ASP page.
>
> That covers a wide range doesn't it? I see your follow-up so you have
> been helped. Your future help requests can be facilitated by providing a
> repro script. In this case, the repro script would have been:
>
> <%
> Response.Write "Hello, World"
> %>
>
> But without seeing your follow-up, I would not have known this. My
> initial reply was basically a guess. With the repro script (and the text
> of the error message) it would have been a certainty.
>

Ah, OK. I see what you mean. In fairness, any ASP page using VBScript
failed the same way.

Bob
Tue Nov 14 13:16:29 CST 2006

Marc Wilson wrote:
>> That article has been the standard reply for several years. Given MS
>> dropping development of ASP, you will need to resign yourself to this
>> question never being answered. Sorry.
>
> Dropping it in favour of ASP.NET, presumably?

Exactly
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.