Please go through my previous post, before reading this.
It works with IIS 5.1.
I faced the same issue today with IIS 6.0/Windows 2003 Server. None of the previous solutions did help.
Finally..was able to got through, by changing the Identity of IIS Application Pools, from Network Service to Local System. No machine.config changes are required.
The identity of an application pool is the name of the account under which an application pool's worker process runs. By default, application pools operate under the NetworkService account, which has the least user rights that are required to run Web applications. You can configure application pools to run as LocalSystem, which is an account with more assigned user rights than the NetworkService account; however, running an application pool under an account with more user rights assigned presents a more serious security risk.
You can also get around with this by using impersonation, quite handy when used together with role based security.
ReplyDeleteThanks ..Mahasen
ReplyDelete