chapter 15: WSAT error

dany96 · August 12th, 2011, 12:01 PM

when I try to enter the Web Site Administration Tool (Website > ASP.NET Configuration), I get this message:

Quote:

An error was encountered. Please return to the previous page and try again.

how do I solve this problem?

Imar · August 12th, 2011, 03:17 PM

Hi there,

Maybe your database isn't setup correctly? Do other features such as membership work at the frontend? Can you post the code for your web.config?

Imar

dany96 · August 12th, 2011, 03:58 PM

here is a screenshot:
http://img37.imageshack.us/img37/2577/unledldh.png

and here is the web.config:

Code:

<?xml version="1.0"?>
<!-- 
    Note: As an alternative to hand editing this file you can use the 
    web admin tool to configure settings for your application. Use
    the Website->Asp.Net Configuration option in Visual Studio.
    A full list of settings and comments can be found in 
    machine.config.comments usually located in 
    \Windows\Microsoft.Net\Framework\v2.x\Config 
-->
<configuration>
  <appSettings/>
  <connectionStrings>
    <add name="PlanetWroxConnectionString1" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\PlanetWrox.mdf;Integrated Security=True;User Instance=True" providerName="System.Data.SqlClient"/>
  </connectionStrings>
  <system.web>
    <!-- 
            Set compilation debug="true" to insert debugging 
            symbols into the compiled page. Because this 
            affects performance, set this value to true only 
            during development.
        -->
    <compilation debug="true" targetFramework="4.0">
      <assemblies>
        <add assembly="System.Web.DynamicData, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
        <add assembly="System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="System.ComponentModel.DataAnnotations, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
        <add assembly="System.Data.Linq, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="System.Data.Entity, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="System.Drawing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
        <add assembly="System.Web.Entity, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        <add assembly="mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
      </assemblies>
    </compilation>
    <!--
            The <authentication> section enables configuration 
            of the security authentication mode used by 
            ASP.NET to identify an incoming user. 
        -->
      <membership>
          <providers>
              <clear/>
              <add name="AspNetSqlMembershipProvider" 
                   type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" 
                   connectionStringName="LocalSqlServer" 
                   enablePasswordRetrieval="false" 
                   enablePasswordReset="true" 
                   requiresQuestionAndAnswer="false" 
                   applicationName="/" 
                   requiresUniqueEmail="false" 
                   passwordFormat="Hashed" 
                   maxInvalidPasswordAttempts="5" 
                   minRequiredPasswordLength="6" 
                   minRequiredNonalphanumericCharacters="0" 
                   passwordAttemptWindow="10" 
                   passwordStrengthRegularExpression=""/>
          </providers>
      </membership>
      
      <authentication mode="Forms">
          <forms timeout="43200" />
      </authentication>
    <!--
            The <customErrors> section enables configuration 
            of what to do if/when an unhandled error occurs 
            during the execution of a request. Specifically, 
            it enables developers to configure html error pages 
            to be displayed in place of a error stack trace.

        <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
            <error statusCode="403" redirect="NoAccess.htm" />
            <error statusCode="404" redirect="FileNotFound.htm" />
        </customErrors>
        -->
    <pages theme="Monochrome" controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID">
      <controls>
        <add tagPrefix="Wrox" tagName="Banner" src="~/Controls/Banner.ascx"/>
      </controls>
    </pages>
  </system.web>
  <!-- 
  The system.webServer section is required for running ASP.NET AJAX under Internet
  Information Services 7.0.  It is not necessary for previous version of IIS.
  -->
  <system.net>
    <mailSettings>
      <smtp deliveryMethod="Network" from="Planet Wrox System &lt;[email protected]&gt;">
        <network host="smtp.mail.yahoo.com" userName="******" password="**********"/>
      </smtp>
    </mailSettings>
  </system.net>
</configuration>

Imar · August 13th, 2011, 03:38 AM

Hmmm, not sure what's going on. Do you have the aspnetb.mdf file in your App_Data folder? Does Membership work at the frontend?

Imar

dany96 · August 13th, 2011, 03:48 AM

I have ASPNETDB.mdf file in the App_Data, and what frontend? if you mean the WSAT frontend then no, the screenshot i posted is all I get.
I know just that the sign up and login are working...

Imar · August 13th, 2011, 06:36 AM

Quote:

I know just that the sign up and login are working...

Yeah, that's what I meant with frontend. This indicates that Membership works as expected and is configured correctly in the web.config.

You may want to search Google for the exact error message and see if that brings up something useful. The error has been reported by others and one of their solutions may help.

Can you verify your own account has permissions to write to the App_Data folder? To see if it's a security problem, try granting Full Control to the Everyone account temporarily.

Cheers,

Imar

Imar · August 13th, 2011, 06:37 AM

Another thing to check: what's the path to your web site on your disk?

Imar

dany96 · August 13th, 2011, 08:13 AM

C:\Users\VaindrU\Documents\C#WEB\Site

Imar · August 13th, 2011, 08:28 AM

Ah, that's what I thought (not the exact path, but the # in the folder name). Try this:

1. Close Visual Studio
2. Rename the folder by removing the # or rename it to something like C:\Users\VaindrU\Documents\CSharpWEB\Site
3. Open the web site from its new location in VWD.
4. Try the WSAT again.

I think it should work then.

IMO, you're usually better off placing sites in a folder outside your Documents folder such as C:\Websites. Your Documents folder has special permissions applied which may cause security problems. That's not the reason for the current problem, but you may run in to it in the future.

Cheers,

Imar

dany96 · August 13th, 2011, 01:21 PM

Thanks man! it works now.
btw I enjoyed your book, I almost finished it and I already built a simple website for a friend and uploaded it on the internet.
and I wanted to ask you what to learn after this book, is there some advanced things in asp.net that u recomend to learn? I know that u published another one asp.net 4, but I saw that the only new thing there I think is the JQuery..