Sub Web won't run

[JonO]

Main site is:
http://www.e-cattery.com which is a version of DotNetNuke (similar to Microsoft's 'Communities' web app

sub Web is:
http://www.e-cattery.com/LaChat

I can get to the subweb okay via the browser - by hitting an html page, but when I try to run the app by hitting aspx page, I end up parsing the web.config file of the root web, it crashes on "add name="HTTPHandler" type="DotNetNuke.HTTPHandler, DotNetNuke" /" which is in the main web.

I have configured the subweb as an application, and I've given it read-write.

I suspect this is a blind spot on my part, but I would love to say "doh" if someone can tell me what I'm missing.

Jon
(Information doesn't want to be free, it wants to be sixty-nine cents @ pound)

[bruce]

Ya... that's what i was going to recommend. but i thought i'll give you a technical answer rather than workaround.

Enjoy.
quote:Originally posted by JonO

Yes it does! Of course it does. And it's a much simpler solution than what I came up with, which was move the entire DNN app off into a subweb, thusly removing its config from the hierarchal consideration when I call up the other web app.

Most importantly, I now know what to do [b]next time

Thanks!!!

[b]quote:Originally posted by bruce

Jon,

I am fairly familiar w/ DNN.

DNN uses a httphandler to intercept most HTTP request. This setting will inherits into your subweb (or sub application). You'll need to explicitly remove the HTTP Handler in your subapplication's web.config.

Let me if if that helps.</blockquote id="quote"></font id="quote">

Jon
(Information doesn't want to be free, it wants to be sixty-nine cents @ pound)
</blockquote id="quote"></font id="quote">

[bruce]

Jon,

I am fairly familiar w/ DNN.

DNN uses a httphandler to intercept most HTTP request. This setting will inherits into your subweb (or sub application). You'll need to explicitly remove the HTTP Handler in your subapplication's web.config.

Let me if if that helps.

[b]quote:Originally posted by JonO

Main site is:
http://www.e-cattery.com which is a version of DotNetNuke (similar to Microsoft's 'Communities' web app

sub Web is:
http://www.e-cattery.com/LaChat

I can get to the subweb okay via the browser - by hitting an html page, but when I try to run the app by hitting aspx page, I end up parsing the web.config file of the root web, it crashes on "add name="HTTPHandler" type="DotNetNuke.HTTPHandler, DotNetNuke" /" which is in the main web.

I have configured the subweb as an application, and I've given it read-write.

I suspect this is a blind spot on my part, but I would love to say "doh" if someone can tell me what I'm missing.

Jon
(Information doesn't want to be free, it wants to be sixty-nine cents @ pound)
</blockquote id="quote"></font id="quote">

[JonO]

Yes it does! Of course it does. And it's a much simpler solution than what I came up with, which was move the entire DNN app off into a subweb, thusly removing its config from the hierarchal consideration when I call up the other web app.

Most importantly, I now know what to do next time

Thanks!!!

[b]quote:Originally posted by bruce

Jon,

I am fairly familiar w/ DNN.

DNN uses a httphandler to intercept most HTTP request. This setting will inherits into your subweb (or sub application). You'll need to explicitly remove the HTTP Handler in your subapplication's web.config.

Let me if if that helps.</blockquote id="quote"></font id="quote">

Jon
(Information doesn't want to be free, it wants to be sixty-nine cents @ pound)