DotNetNuke Permissions issues

Discussion in 'ASP.NET / ASP.NET Core' started by compuaid, Apr 2, 2004.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. I've installed a tested and working version of a DotNetNuke 2.03 portal here and everything seems to be working but there is one strange quirk...the first time I access the portal after a few minutes of inactivity I receive a message from DotNetNuke that reads:

    DotNetNuke Configuration Error
    Access to the path "E:\web\compuaidcom\htdocs\kybar\verify" is denied.

    DotNetNuke has extensive file upload capabilities for content, modules, and skins. These features require custom security settings so that the application is able to create and remove files in your website.

    Using Windows Explorer, browse to the root folder of the website ( C:\DotNetNuke by default ). Right-click the folder and select Sharing and Security from the popup menu ( please note that if you are using Windows XP you may need to Enable Simple File Sharing before these options are displayed ). Select the Security tab. Add the appropriate User Account and set the Permissions.

    If using Windows 2000 - IIS5
    - the {Server}/ASPNET User Account must have Read, Write, and Change Control of the virtual root of your website

    If using Windows 2003 - IIS6
    - the {Server}/NetworkService User Account must have Read, Write, and Change Control of the virtual root of your website

    Any suggestions on what changes I need to make from my Control Panel or is this something that is going to require a modification by tech support in the directory where I've setup the DotNetNuke files?

    Brad Weaver
    ComputerAid International
     
  2. Bruce

    Bruce DiscountASP.NET Staff

    pls create a support ticket, we can verify the permission for you.

    quote:Originally posted by compuaid

    I've installed a tested and working version of a DotNetNuke 2.03 portal here and everything seems to be working but there is one strange quirk...the first time I access the portal after a few minutes of inactivity I receive a message from DotNetNuke that reads:

    DotNetNuke Configuration Error
    Access to the path "E:\web\compuaidcom\htdocs\kybar\verify" is denied.

    DotNetNuke has extensive file upload capabilities for content, modules, and skins. These features require custom security settings so that the application is able to create and remove files in your website.

    Using Windows Explorer, browse to the root folder of the website ( C:\DotNetNuke by default ). Right-click the folder and select Sharing and Security from the popup menu ( please note that if you are using Windows XP you may need to Enable Simple File Sharing before these options are displayed ). Select the Security tab. Add the appropriate User Account and set the Permissions.

    If using Windows 2000 - IIS5
    - the {Server}/ASPNET User Account must have Read, Write, and Change Control of the virtual root of your website

    If using Windows 2003 - IIS6
    - the {Server}/NetworkService User Account must have Read, Write, and Change Control of the virtual root of your website

    Any suggestions on what changes I need to make from my Control Panel or is this something that is going to require a modification by tech support in the directory where I've setup the DotNetNuke files?

    Brad Weaver
    ComputerAid International
    </blockquote id="quote"></font id="quote">
     
  3. I resolved the problem by creating a new directory under my account that was NOT a Frontpage Extensions directory. Apparently the Frontpage server extensions change some of the permissions necessary for DotNetNuke to run properly. DNN 2.03 is working great now. Of course it does happen to be running on the Web108 server so of course the prospective client was not thrilled when they couldn't access it this afternoon due to the server crash. Here's hoping that's a rare occurence! [:I]

    Brad Weaver
    ComputerAid International
     
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page