http://thrilla.net/  and it worked great. I recently upgrated my wwwroot website from static html and aspx pages to a dynamic .NET CMS called DotNetNuke. Problems arose, I managed to installed DNN and get it working correctly. But once i attempted to goto YAF using the above link. I recieved the following error message.

Server Error in '/board' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

I get the same message from the server and remote machines as well..

But if I point to a directory such as board/install/ it can browse the directory.

I turned

in the j:\yaf\web.config

http://thrilla.net/board/  to the same error message (which can be customized for remote views)in another directory? Not very helpful.

I am aware of the DNN and YAF bundle, but would like the YAF to remain its own virtual directory....what am i doing wrong? HELP! :evil:

Not sure how your structure in IIS works... but make sure the J:\yaf\ directory is it's own application directory and restart IIS.

Server Error in '/board' Application.

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: The code subdirectory '/board/App_Code/HTML/' does not exist.

Source Error:

Line 109: -->

Line 110:

Line 111:

Line 112:

Line 113:

Source File: :\Inetpub\wwwroot\web.config Line: 111

seems to be referencing web config for website wwwroot/DNN not YAF virtual directory... sincce it reside on a virtual dir why is it not pointing to /YAF/web.config? Confused?

WinDoze:

If not, that's probably why IIS is reading the root's web.config rather than the YAF VD's web.config.

but it does have its own application pool and account.

Let me explain:

"Root" IIS application directory has DNN installed in it with it's web.config -- let's call it ~/

Even if you have a completely separate application in a different directory -- as long as the app directory is a child of that root -- it will pull the full configuration into it.

So... let's say you have ~/forum too...

but that's off from the base root with DNN installed in ~/

~/forum will pull ALL the configuration settings from ~/web.config into it... and then also apply any settings from ~/forum/web.config.

Make sense?

Is it a bitch? Yes. Is it extremely useful in *most* situations? Yes.

I would actually suggest NOT having YAF in a separate application off DNN -- that's just easier. If you must -- you will have to learn a very, very useful function of the web.config -- the "Remove" function.

E.g.:

Line 110:

Line 111:

Line 112:

Line 113:

So true. I've seen it over and over again. Simply taking the time to merge all a client's web.configs usually fixes everything. And then everything is that much simpler going forward.

 

www.bunkerhollow.com  | www.careercomputing.com 

When I post fp:mddubs in a topic, I'm leaving my footprint there so I can track it once I get into coding/supporting. (Yes I stole this off Mek 🙂, who stole this off Ederon 🙂 )