Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Help with web.configHelp with web.config
Previous
 
Next
New Post
1/24/2006 11:40 AM
 

Don't know if this is the place to ask but I have a problem.

I have created a couple of pages that have nothing to do with DNN and put them in a sub directory on the site.  I have web.config file in the directory with the new files.  My problem is that when you load a page in this new directory it reads the web.config file in that directory wich is good, but it also reads the web.config file in the root directory, the DNN install web config.  When I go to a page in this sub directory I get the following errror:

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: Could not load file or assembly 'DotNetNuke.HttpModules.UrlRewrite' or one of its dependencies. The system cannot find the file specified. (c:\hosting\webhost4life\member\sdwo\web.config line 55)

Source Error:

Line 53:     <httpModules>
Line 54:       <!-- add name="Authentication" type="DotNetNuke.HttpModules.AuthenticationModule, DotNetNuke.HttpModules.Authentication" / -->
Line 55:       <add name="UrlRewrite" type="DotNetNuke.HttpModules.UrlRewriteModule, DotNetNuke.HttpModules.UrlRewrite" />
Line 56:       <add name="Exception" type="DotNetNuke.HttpModules.ExceptionModule, DotNetNuke.HttpModules.Exception" />
Line 57:       <add name="UsersOnline" type="DotNetNuke.HttpModules.UsersOnlineModule, DotNetNuke.HttpModules.UsersOnline" />

 

Is there a way I can tell the files in my directory to ignore the parent directory's web.config file or is there something simple I can do to get this to work.

Thanks,

Scott

 
New Post
1/24/2006 7:18 PM
 

Add <Clear /> to the HTTPHandlers section of the web config of your other virtual directory.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
1/24/2006 10:40 PM
 
It is in the <httpmodules> not <httphandlers> and <clear /> doesn't work in the modules
 
New Post
1/25/2006 2:00 PM
 

sorry, it was late when I made the post. Use <clear /> in the httpmodules section. See this for more details.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
1/25/2006 3:33 PM
 

That cleard up that problem then I got the same thing in <httpHandlers> 

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: Could not load file or assembly 'FreeTextBox' or one of its dependencies. The system cannot find the file specified.

Source Error:

Line 61:     <!-- This is for FTB 3.0 support -->
Line 62:     <httpHandlers>
Line 63:       <add verb="GET" path="FtbWebResource.axd" type="FreeTextBoxControls.AssemblyResourceHandler, FreeTextBox" />
Line 64:     </httpHandlers>
Line 65:     <!-- set code access security trust level - this is generally set in the machine.config   -->


Source File: c:\hosting\webhost4life\member\sdwo\web.config    Line: 63

Assembly Load Trace: The following information can be helpful to determine why the assembly 'FreeTextBox' could not be loaded.

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

 

 if I put <clear/> in the handlers then it doesn't know how to handle GET.  This is a real pain.    I am sure it is a microsoft thing lets blame Bill. 

No http handler was found for request type 'GET'

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: No http handler was found for request type 'GET'

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[HttpException (0x80004005): No http handler was found for request type 'GET']
   System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig) +659
   System.Web.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +120
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155

 

Any other thoughts?

Thanks,
Scott

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Help with web.configHelp with web.config


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out