Default runtime error page regardless of customerrors setting

[kristan.mcdonald]

Probably a simple one, but I've found nothing in groups or google so
here goes;
trying to deploy a simple .net asp app to our web server, which has
been hardended as it's public facing. It's only ever run classic asp
apps before. I've tried to upload a basic app with nothing but an empty
web form, and I get the default "Runtime error, The custom error
settings prevent you blah"

I've tried setting customErrors but I get the same page, I've tried
aspnet_regiis -i to reinstall, I've tried doing a -ua then an -i to
remove and install. I'm guessing it's something to do with whatever
security settings were applied to the box, but I've even tried giving
everyone full control to the folder and still nothing!

Please has anyone got any ideas?

ta

 

[Guest]

If this is IIS 6.0, have you "Allowed" the webservice extension for ASP.NET?
They all come locked down by default, except for plain old HTML.
Peter

 

[kristan.mcdonald]

Yeah, but thanks for reminding me to check though - "ASP.NET v1.1.4322
Allowed". Any other ideas?

 

[kristan.mcdonald]

Just to thicken the plot slightly, if I just copy a default app up I
get told
"Server cannot access application directory 'E:\site\atest\'. The
directory does not exist or is not accessible because of security
settings. "

This is true, and interestingly I get the footer giving me the
information about the framework and asp.net versions. If I grant
permissions to the relevant accounts, I get the default runtime error
page, but without the footer. It's like it can't find some part of
asp.net and it giving up.

 

[kristan.mcdonald]

horrah, got it working!

In case anyone else has problems with this, I edited the machine.config
to set customerrors to off, go the actual error (which was due to me
being stupid, as I didn't grant asp.net permissions to the folder of
the website, only the app folder which was underneath) and now it
works. Only taken me 5 hours!!