web.config error

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • choatdot
    New Member
    • Aug 2006
    • 1

    web.config error

    I ftp my asp.net 2.0 pages using visual studio 2005 to a godaddy.com server, when I try running it I keep getting this error.



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

    Configuration Error
    Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

    Parser Error Message: It is an error to use a section registered as allowDefinition ='MachineToAppl ication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.

    Source Error:


    Line 22: during development.
    Line 23: -->
    Line 24: <roleManager enabled="true"/>
    Line 25: <customErrors mode="Off"/>
    Line 26: <compilation debug="true">


    Source File: E:\ictstudents\ 000524203\dot\w eb.config Line: 24



    Show Additional Configuration Errors:


    It is an error to use a section registered as allowDefinition ='MachineToAppl ication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS. (E:\ictstudents \000524203\dot\ web.config line 40)
    It is an error to use a section registered as allowDefinition ='MachineToAppl ication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS. (E:\ictstudents \000524203\dot\ web.config line 41)




    --------------------------------------------------------------------------------
    Version Information: Microsoft .NET Framework Version:2.0.507 27.42; ASP.NET Version:2.0.507 27.42


    I know something needs to be done to the web.config file. I just don't know what.

    Thanks.
  • Enyi
    New Member
    • Jul 2006
    • 38

    #2
    This error can be caused by a virtual directory not being configured as an application in IIS.
    For this, you would have to go to control panel in Windows, then the IIS configuration module, and setup the virtual directory there.

    But this looks like something you would have to get GoDaddy to do unless you have remote access to your web server.

    Comment

    Working...