Receiving 404 Error When Trying To View elmah.axd File In IIS 7.0

jonathangill

unread,

Aug 25, 2008, 12:50:57 PM8/25/08

to ELMAH

I am receiving a 404 Error when trying to access the elmah.axd file on
the server. Is there something I need to do to allow the file to
appear. I am using Discount ASP as my web host and my account is also
running IIS 7.0.

The log should appear at domain.com/elmah.axd.

James_2JS

unread,

Aug 25, 2008, 6:02:14 PM8/25/08

to ELMAH

Have you looked at any of these threads which discuss the same
problem???

http://groups.google.com/group/elmah/browse_thread/thread/74b855ca569585df?hl=en
http://groups.google.com/group/elmah/browse_thread/thread/4bbef2f26e0c5fd1?hl=en
http://groups.google.com/group/elmah/browse_thread/thread/c678f3120d37f8a6?hl=en

Cheers,

James

jonathan{GILL}

unread,

Aug 25, 2008, 7:58:06 PM8/25/08

to el...@googlegroups.com

James,

Yes, these have been utilized but I am still receiving a 404 error. It may be because my host has not mapped .axd files.

James_2JS

unread,

Aug 26, 2008, 3:25:03 AM8/26/08

to ELMAH

Hi Jonathan,

I don't think it's because the .axd files haven't been mapped... if
that was the case you would have issues with WebResource.axd, which is
pretty fundamental to the .NET Framework! However, you should be able
to test this by changing elmah.axd for elmah.aspx in the handler
mapping. If you get no joy with this, could you post your web.config
here so we can see what's going on please?!

Thanks,

James

jonathan{GILL}

unread,

Aug 26, 2008, 8:38:18 PM8/26/08

to el...@googlegroups.com

James,

Thanks. It doesn't look like that worked either. Here is the current mix and match web.config, that may have the details needed.

<?xml version="1.0"?>
<configuration>
<configSections>
  
  
  <sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
   <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
    <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication"/>
    <sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
     <section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="Everywhere"/>
     <section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication"/>
     <section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication"/>
    </sectionGroup>
   </sectionGroup>
  </sectionGroup>

  <sectionGroup name="elmah">
   
   <section name="security" requirePermission="false" type="Elmah.SecuritySectionHandler, Elmah"/>
   <section name="errorLog" requirePermission="false" type="Elmah.ErrorLogSectionHandler, Elmah"/>
   <section name="errorMail" requirePermission="false" type="Elmah.ErrorMailSectionHandler, Elmah"/>
   <section name="errorFilter" requirePermission="false" type="Elmah.ErrorFilterSectionHandler, Elmah"/>
  </sectionGroup>
  <section name="NotTheRealDBName.Data" type="NotTheRealDBName.Data.Bases.NetTiersServiceSection, NotTheRealDBName.Data" allowDefinition="MachineToApplication" restartOnExternalChanges="true"/>
  <section name="enterpriseLibrary.ConfigurationSource" type="Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ConfigurationSourceSection, Microsoft.Practices.EnterpriseLibrary.Common, Version=3.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
</configSections>
<connectionStrings>
  <add name="NotTheRealDBName.Data.ConnectionString" connectionString="Data Source=sql2k503.whatwhat.net;Initial Catalog=SQL2005_537304_NotTheRealDBNamedev;Persist Security Info=True;User ID=SQL2005_537304_NotTheRealDBNamedev_user;Password=phones"/>
  <add name="connNotTheRealDBName_PRD" connectionString="Data Source=sql2k503.whatwhat.net;Initial Catalog=SQL2005_537304_NotTheRealDBNamedev;Persist Security Info=True;User ID=SQL2005_537304_NotTheRealDBNamedev_user;Password=phones" providerName="System.Data.SqlClient"/>
  <remove name="LocalSqlServer"/>
  <add name="LocalSqlServer" connectionString="Data Source=sql2k503.whatwhat.net;Initial Catalog=SQL2005_537304_NotTheRealDBNamedev;Persist Security Info=True;User ID=SQL2005_537304_NotTheRealDBNamedev_user;Password=phones" providerName="System.Data.SqlClient"/>
  <add name="Elmah.Sql" connectionString="Data Source=sql2k503.whatwhat.net;Initial Catalog=SQL2005_537304_NotTheRealDBNamedev;Persist Security Info=True;User ID=SQL2005_537304_NotTheRealDBNamedev_user;Password=phones" providerName="System.Data.SqlClient"/>
</connectionStrings>
<NotTheRealDBName.Data defaultProvider="SqlNetTiersProvider">
  <providers>
   
   <add name="SqlNetTiersProvider" type="NotTheRealDBName.Data.SqlClient.SqlNetTiersProvider, NotTheRealDBName.Data.SqlClient" connectionStringName="NotTheRealDBName.Data.ConnectionString" providerInvariantName="System.Data.SqlClient" entityFactoryType="NotTheRealDBName.Entities.EntityFactory" useEntityFactory="true" enableEntityTracking="true" enableMethodAuthorization="false" useStoredProcedure="false" defaultCommandTimeout="60"/>
   
  </providers>
</NotTheRealDBName.Data>
<appSettings>
  <add key="SiteStatus" value="On"/>
  <add key="UserThreshold" value="1000"/>
  <add key="CSSFriendly-JavaScript-Path" value="~/JavaScript"/>
</appSettings>
<elmah>
  <security allowRemoteAccess="1"/>
  <errorLog type="Elmah.SqlErrorLog, Elmah" connectionStringName="Elmah.Sql"/>
  
  <!--
            Use to log errors into separate XML files that are stored on
            disk at the path specified in the logPath attribute.

<errorLog type="Elmah.XmlFileErrorLog, Elmah" logPath="..." />
        -->
  <!--
            Use to send error reports by e-mail and adjust the attributes
            according to settings desired. Note that only the from and
            to attributes are required. The rest are optional and may
            be removed. If the SMTP server does not require authentication,
            you MUST remove the userName and password attributes or
            set them to empty values (resulting in zero-length strings).
            If you are using ELMAH compiled for .NET Framework 1.x, then
            the to attribute may contain multiple recipient addresses,
            each of which must be delimited by a semi-colon(;). If you are
            using ELMAH compiled for .NET Framework 2.0 or later, then the
            to attribute may contain multiple recipient addresses,
            each of which must be delimited by a comma (,).

<errorMail
            from="el...@example.com"
            to="ad...@example.com"
            subject="..."
            async="true|false"
            smtpPort="25"
            smtpServer="smtp.example.com"
            userName="johndoe"
            password="secret" />
        -->
  <!--
            Use to prevent errors from being mailed or logged based on
            assertions/conditions provided under the <test> element.
            The example below will filter errors of type HttpException
            where the status code is 404 (in other words, where the
            resource was not found).

<add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
    <add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
    <add assembly="System.Management, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
    <add assembly="System.Security, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
    <add assembly="System.Configuration.Install, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
    <add assembly="System.Data.OracleClient, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
    <add assembly="System.Transactions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
    <add assembly="stdole, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
    <add assembly="System.Messaging, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
    
   </assemblies>
  </compilation>
  <!-- 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"/>
  <httpHandlers>
   
  <remove verb="*" path="*.asmx"/>
  <add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
  <add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
  <add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" validate="false"/>

<add verb="POST,GET,HEAD" path="elmah.axd" type="Elmah.ErrorLogPageFactory, Elmah"/>
  
  </httpHandlers>
  <httpModules>
   
      <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

<add name="EntityTransactionModule" type="NotTheRealDBName.Web.Data.EntityTransactionModule"/>
   <add name="ErrorLog" type="Elmah.ErrorLogModule, Elmah"/>
   
   
   
  </httpModules>
  <!-- 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 name=".NotTheRealDBName" loginUrl="Login.aspx" protection="All" timeout="120" path="/" requireSSL="false" slidingExpiration="true" defaultUrl="Login.aspx" cookieless="UseDeviceProfile" enableCrossAppRedirects="false"/>
  </authentication>
  <sessionState timeout="120"/>
  <membership userIsOnlineTimeWindow="120">
   <providers>
    <add name="AspNetSqlProvider" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" connectionStringName="connNotTheRealDBName_PRD" enablePasswordRetrieval="true" enablePasswordReset="true" requiresQuestionAndAnswer="false" applicationName="NotTheRealDBName" requiresUniqueEmail="true" passwordFormat="Encrypted" minRequiredPasswordLength="6" minRequiredNonalphanumericCharacters="1"/>
    
    
   </providers>
  </membership>
  <roleManager defaultProvider="AspNetSqlProvider" enabled="true">
   <providers>
    
    <add name="AspNetSqlProvider" connectionStringName="connNotTheRealDBName_PRD" applicationName="NotTheRealDBName" type="System.Web.Security.SqlRoleProvider"/>
   </providers>
  </roleManager>
  
  <profile defaultProvider="AspNetSqlProvider" enabled="true">
   <providers>
    
    <add name="AspNetSqlProvider" connectionStringName="connNotTheRealDBName_PRD" applicationName="NotTheRealDBName" type="System.Web.Profile.SqlProfileProvider"/>
   </providers>
   
  </profile>
  
  <globalization requestEncoding="utf-8" responseEncoding="utf-8" culture="auto" uiCulture="auto"/>
  
  <authorization>
   <allow users="*"/>
   
   
  </authorization>
  
  <trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true"/>
  
  
  <machineKey validationKey="30CC1E773F7D12E53A3C9F2346D682C33593DE77788CB7CF0154A9885D9F63A59219D5507D1C5C6AEAAA3EDC1D632C5EA86F2BB5BA476652F60F74A4394E2182" decryptionKey="1CC156C7B41308C8B09AF7FB8C08E7B548C722A3131547CAAB3189A268680B7D" validation="SHA1" decryption="AES"/>
  <xhtmlConformance mode="Legacy"/>
</system.web>

<enterpriseLibrary.ConfigurationSource selectedSource="File Configuration Source">
  <sources>
   <add name="File Configuration Source" type="Microsoft.Practices.EnterpriseLibrary.Common.Configuration.FileConfigurationSource, Microsoft.Practices.EnterpriseLibrary.Common, Version=3.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" filePath="entlib.config"/>
  </sources>
</enterpriseLibrary.ConfigurationSource>

<system.net>
  <mailSettings>
   <smtp from="no-r...@whatwhatyupyep.info">
    <network host="smtp.whatwhatyupyep.info" port="25" userName="no-r...@whatwhatyupyep.info" password="crazy!fet43tegfet3t3ef1"/>
   </smtp>
  </mailSettings>
</system.net>
<system.web.extensions>
  <scripting>
   <webServices>
    
    
    
    
    
    
   </webServices>
   
  </scripting>
</system.web.extensions>


<system.webServer>
  <validation validateIntegratedModeConfiguration="false"/>
  <modules>
   <add name="ScriptModule" preCondition="integratedMode" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

        <add name="Elmah.ErrorLog" type="Elmah.ErrorLogModule, Elmah"
preCondition="managedHandler" />

  </modules>
  <handlers>
   <remove name="WebServiceHandlerFactory-Integrated"/>
   <add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
   <add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
   <add name="ScriptResource" preCondition="integratedMode" verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
  </handlers>
</system.webServer>
</configuration>

James_2JS

unread,

Aug 27, 2008, 3:37:44 AM8/27/08

to ELMAH

Hi Jonathan,

Looks like you've made a simple omission in the <system.webServer>
(aka IIS7) part of web.config:

<configuration>
<system.webServer>
<handlers>
<add name="Elmah" path="elmah.axd" verb="POST,GET,HEAD"
type="Elmah.ErrorLogPageFactory, Elmah" preCondition="integratedMode" /
>
</handlers>
</system.webServer>
</configuration>

You have put the right bits into the <modules> section, but you
haven't put the handler in there... hence the 404 errors!!

Give that a whirl and let us know how you get on!

Cheers,

James

Reply all

Reply to author

Forward