Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 5 of 5

Thread: Question about attempting to encrypt web.config

  1. 11-20-2009, 08:20 AM #1
    chainsaw is offline Junior Member
    Join Date
    Jul 2009
    Posts
    9

    Default Question about attempting to encrypt web.config

    I'm almost finished with the configuration of this site, and I need to encrypt this file. After clicking on the configuration wizard, and trying to encrypt the file, I get an error below.

    Server Error in '/AspDotNetStorefront' 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>
  2. 11-20-2009, 08:31 AM #2
    John Reasons is offline Senior Member
    Join Date
    Oct 2009
    Posts
    119

    Default

    You will need to temporarily give both ASPNET and NETWORK SERVICES user account Read, Write and Modify access to the entire Web directory in order to encrypt the web.config, once it is encrypted you can set the ASPNET and NETWORK SERVICES user account permissions to their previous setting.
  3. 11-25-2009, 07:53 AM #3
    chainsaw is offline Junior Member
    Join Date
    Jul 2009
    Posts
    9

    Default

    They've done that for me, and yet it still errors out after the perms have been
    modified. Any other ideas on what might be causing this?



    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>
  4. 11-25-2009, 06:52 PM #4
    ASPAlfred is offline Senior Member
    Join Date
    Nov 2007
    Posts
    2,244

    Default

    Ok. We need to view the stack trace to determine what error you're getting. Please open up your web.config file and set customErrors mode to "Off". Try to encrypt it again and send us the error details here to see what's going on. Thanks
  5. 11-30-2009, 09:55 AM #5
    chainsaw is offline Junior Member
    Join Date
    Jul 2009
    Posts
    9

    Default

    I already have it set to off. Did you mean "On"?

    <!-- CUSTOM ERROR MESSAGES: Set customErrors mode="On" or "RemoteOnly" to enable custom error messages, "Off" to disable. -->
    <customErrors mode="Off">