Link to home
Start Free TrialLog in
Avatar of CUTTHEMUSIC
CUTTHEMUSIC

asked on

.NET File Permission Issues

I installed .NET on my Win2k server and was unable to run an aspx file. I then went to my webserver directory and gave the ASPNET user full control of my websites files. What permissions should I give the ASPNET user. Please supply links if possible.
ASKER CERTIFIED SOLUTION
Avatar of naveenkohli
naveenkohli

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of CUTTHEMUSIC
CUTTHEMUSIC

ASKER

It's not a domain contoller. I changed the permissions to read/execute and it still works. Although I must assign the permissions all the way upto the root. Ex.

If I give d:\webserverDirectory\ read / execute permissions then it works.

But if I give d:\webserverDirectory\mydoamain\ read /execute permissions then I get the below error.


Server Error in '/' Application.
--------------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>
 

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>
 
The first link in the list i gave you tells exactly what permissions are required on what folder. So if you look at that, the root web folder requires the read permissions for reading confoguration file. So can't take away all the permissions on it.
Try to follow that table and you will come up with right ACLs on various folders for ASPNET account.
Thanks, This .NET stuff seams to offer alot more features but sometimes I wonder if all of the headaches are worth it?   :~)