IIS7 - Classic ASP

Re: Problem when using App pool account for Anonymous Authentication

djwUnisys — Wed, 17 Jun 2009 19:10:59 GMT

When I look for the applicationhost.config file, there are multiple copies in inetpub -> history -> CFGHISTORY_0000000020...

Re: Problem when using App pool account for Anonymous Authentication

Bjorn S — Wed, 17 Jun 2009 06:12:22 GMT

Hi!

This is how my section looked like. My virtual directorys name is "Arbetstagare" and it's under the Default Web Site.

<system.webServer>

</asp>

</authentication>

</security>

</system.webServer>

</location>

If your virtual directory doesn't have a location path you will have to add it to the file. Make sure you do a backup before editing the file.

Re: Problem when using App pool account for Anonymous Authentication

djwUnisys — Tue, 16 Jun 2009 17:57:21 GMT

Bjorn S: In what section did you put this key? I am having this issue and putting this line in doesn't make a change

Thx

Re: Problem when using App pool account for Anonymous Authentication

Bjorn S — Thu, 26 Mar 2009 10:59:09 GMT

I have found a solution for this myself. The trick was to set

for the application in applicationhost.config.

Problem when using App pool account for Anonymous Authentication

Bjorn S — Wed, 25 Mar 2009 09:29:25 GMT

I'm porting our application to IIS 7. The application is very big and uses a mixture of Classic ASP and ASP.Net pages. So far there haven't any problems, but now I've encountered one thing that is a bit irritating.

I really like the possibility to use the application pool account as the anonymous account. That way you get a much more manageable situation when it comes to security. The problem is that when I enabled this for my application I encountered an error when Session_End fires;
"Failed to retrieve the Anonymous User Token for ASP Application /LM/W3SVC/1/ROOT/XXXXXXX. Global.ASA OnEnd routines will not be executed.". It occurs when we try to create a com-object by "Server.CreateObject".

I can understand that there is a special situation since this isn't a user-initiated event, rather a trigger that fires on the server. But it works without problems in the older IIS-versions and it works in IIS 7 if I use the IUSR acount as anonymous user. I should add that I have the problem regardless if I use a "classic" or "pipelined" app pool.

Does anyone know of a fix/workaround for this? I'd really like to run it all as the app pool account.