Wrox Programmer Forums
|
Visual Web Developer 2005 Discuss creating ASP.NET 2.0 sites with Microsoft's Visual Web Developer 2005. If your question is more specific to a piece of code than the Visual tool, see the ASP.NEt 2.0 forums instead.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Visual Web Developer 2005 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old November 24th, 2008, 04:05 AM
Registered User
 
Join Date: Oct 2008
Posts: 7
Thanks: 0
Thanked 0 Times in 0 Posts
Default Problem when login website

Hi all. I'm having a problem to login the website after upload to the server. After i enter the user ID and password then press [Enter], it gives me an error. Runtime Error! An application error occurred on the server. I had set the customErrors mode = "Off". but i can't see the detailed error message. Below is my web.config file. Is there anything goes wrong with my web.config file? Anyone can help?


<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">

      <connectionStrings>
        <add name="AccessFileName" connectionString="~\App_Data\ASPNetDB.mdb" providerName="System.Data.OleDb" />
    </connectionStrings>

  <appSettings>

    <add key="ConnectionString" value="Provider=Microsoft.Jet.OLEDB.4.0;Data Source=d:\hosting\hardypos\Project\Hardsoft.mdb;"/>
  </appSettings>

  <location path="Admin">
    <system.web>
        <authorization>
   <allow roles="Administrators" />
    <deny users="*" />

  </authorization>



  <!-- AUTHENTICATION
          This section sets the authentication policies of the application. Possible modes are "Windows",
          "Forms", "Passport" and "None"

          "None" No authentication is performed.
          "Windows" IIS performs authentication (Basic, Digest, or Integrated Windows) according to
           its settings for the application. Anonymous access must be disabled in IIS.
          "Forms" You provide a custom form (Web page) for users to enter their credentials, and then
           you authenticate them in your application. A user credential token is stored in a cookie.
          "Passport" Authentication is performed via a centralized authentication service provided
           by Microsoft that offers a single logon and core profile services for member sites.
    -->


  <authentication mode="forms " >

   <forms loginUrl="Login.aspx" defaultUrl="Customers.aspx" />
  </authentication>

        <membership defaultProvider="AccessMembershipProvider">
            <providers>
                <clear/>
                <add name="AccessMembershipProvider"
     type="Samples.AccessProviders.AccessMembershipProv ider, SampleAccessProviders"
     connectionStringName="AccessFileName"
     enablePasswordRetrieval="false"
     enablePasswordReset="false"
     requiresUniqueEmail="false"
     requiresQuestionAndAnswer="false"
     minRequiredPasswordLength="1"
     minRequiredNonalphanumericCharacters="0"
     applicationName="SampleSite"
     hashAlgorithmType="SHA1"
     passwordFormat="Hashed"/>
            </providers>
        </membership>
        <roleManager enabled="true" defaultProvider="AccessRoleProvider" cacheRolesInCookie="true" cookieName=".ASPXROLES" cookieTimeout="30" cookiePath="/" cookieRequireSSL="false" cookieSlidingExpiration="true" cookieProtection="All">
            <providers>

                <add name="AccessRoleProvider"
     type="Samples.AccessProviders.AccessRoleProvider, SampleAccessProviders"
     connectionStringName="AccessFileName"
     applicationName="SampleSite"/>
            </providers>
        </roleManager>
        <profile enabled="true" defaultProvider="AccessProfileProvider">
            <providers>
                <add name="AccessProfileProvider"
     type="Samples.AccessProviders.AccessProfileProvide r, SampleAccessProviders"
     connectionStringName="AccessFileName"
     applicationName="SampleSite"
     description="Stores and retrieves profile data from an SampleAccessProviders database."/>
            </providers>
            <properties>
                <add name="FriendlyName" type="string" allowAnonymous="true" serializeAs="String"/>
                <add name="Height" type="int" allowAnonymous="true" serializeAs="String"/>
                <add name="Weight" type="int" allowAnonymous="true" serializeAs="Xml"/>
            </properties>
        </profile>
        <anonymousIdentification enabled="true" cookieName=".ASPXANONYMOUS" cookieTimeout="100000" cookiePath="/" cookieRequireSSL="false" cookieSlidingExpiration="true" cookieProtection="None" domain=""/>
        <webParts>
            <personalization defaultProvider="AccessPersonalizationProvider">
                <providers>
                    <add name="AccessPersonalizationProvider"
      type="Samples.AccessProviders.AccessPersonalizatio nProvider, SampleAccessProviders"
      connectionStringName="AccessFileName"
      applicationName="SampleSite"/>
                </providers>
            </personalization>
        </webParts>


    <identity impersonate="true" />


    <!-- DYNAMIC DEBUG COMPILATION
          Set compilation debug="true" to insert debugging symbols (.pdb information)
          into the compiled page. Because this creates a larger file that executes
          more slowly, you should set this value to true only when debugging and to
          false at all other times. For more information, refer to the documentation about
          debugging ASP.NET files.
    -->
    <compilation debug="true" defaultLanguage="vb" />



    <!-- CUSTOM ERROR MESSAGES
          Set customErrors mode="On" or "RemoteOnly" to enable custom error messages, "Off" to disable.
          Add <error> tags for each of the errors you want to handle.

          "On" Always display custom (friendly) messages.
          "Off" Always display detailed ASP.NET error information.
          "RemoteOnly" Display custom (friendly) messages only to users not running
           on the local Web server. This setting is recommended for security purposes, so
           that you do not display application detail information to remote clients.
    -->
    <customErrors mode ="Off" />



    <!-- APPLICATION-LEVEL TRACE LOGGING
          Application-level tracing enables trace log output for every page within an application.
          Set trace enabled="true" to enable application trace logging. If pageOutput="true", the
          trace information will be displayed at the bottom of each page. Otherwise, you can view the
          application trace log by browsing the "trace.axd" page from your web application
          root.
    -->
    <trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true" />



    <!-- GLOBALIZATION
          This section sets the globalization settings of the application.
    -->
    <globalization requestEncoding="utf-8" responseEncoding="utf-8" />


    </system.web>
    </location>
</configuration>







Similar Threads
Thread Thread Starter Forum Replies Last Post
login control problem (asp.net2.0 website progr..) rookie07 ASP.NET 2.0 Basics 1 June 22nd, 2006 09:25 AM
website query with login Leveland Excel VBA 0 March 15th, 2006 12:56 PM
Problem with IIS and website boksi ASP.NET 2.0 Basics 2 July 18th, 2005 08:10 PM
making a login on a website Apocolypse2005 JSP Basics 0 June 14th, 2005 08:35 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.