A little feedback on my own post. The answer was that the asp.dll file was
not accessible by the IUSR and IWAM accounts. (The Filemon utility (from
sysinternals.com) was a big help in discovering this, as it showed what file
was being denied access.) But before I discovered that, I followed the
procedure in the MKB article 271071 (HOW TO: Set Basic NTFS Permissions for
IIS 5.0). I'm pretty sure that an update caused this problem, as I'd never
have reset those permissions myself. After getting asp working again, I
discovered that CDONTS was not working. I have IIS5 installed on the D
drive, not C where it went by the default installation. But CDONTS still
uses the C:\Inetpub\mailroot area, and the IUSR and IWAM accounts had to
have permissions set there again as per MKB 197619 (Runtime Error '800a0046'
Using the Send Method of CDONTS.NewMail). Now, all is working again, but
some of my permissions as set by MKB 271071 are too permissive and I've some
more work to do in that regard...
SomewhatAnonymous
[quoted text, click to view] "SomewhatAnonymous" <Please@NoSpamWanted.yuk> wrote in message
news:sJ8Zb.14860$v31.1655@newssvr29.news.prodigy.com...
> I posted this to the .iis.activeserverpages group but received no
responses
> yet, so I'm posting it here too... time is becoming critical on my
obtaining
> a solution. :(
> ======
> I've been trying to solve this one for weeks! IIS5, W2KP, very latest
> updates, no virus trojans etc, no attacks. Everything with the box works
> fine, including all of IIS except that absolutely no ASP will work. When
try
> to view any ASP page, I get the Enter Network Password dialog and event
log
> shows errors 529 and 681 for IUSR. I think this is supposed to mean that
the
> IUSR account doesn't exist. But it obviously does, and normal HTML works
ok.
> I've checked everything I can think of, and researched and researched and
> checked again. At NTFS level IUSR is everywhere I think it's supposed to
be
> at, and with at least read permissions. I need major some help on this,
and
> I'm afraid it's not going to be easy to track down because I really have
> been at this for weeks. Anyone willing to spend time with me to nail this
> down right here in this forum? I'm suspecting some kind of a COM problem.
>
>
>
> ---
>
> Checked by AVG anti-virus system (
http://www.grisoft.com).
> Version: 6.0.592 / Virus Database: 375 - Release Date: 18-Feb-04
>
>
---
Checked by AVG anti-virus system (
http://www.grisoft.com).
Version: 6.0.592 / Virus Database: 375 - Release Date: 18-Feb-04