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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...BC30451: Name BC30451: Name 'Config' is not declared.
Previous
 
Next
New Post
5/25/2007 11:47 AM
 

I am getting the common error "BC30451: Name 'Config' is not declared." when trying to install DNN 4.4.1 onto a Win2K3 server box that is hosting live websites.  There seems to be a couple of posts around, especially a link to Charles Nurse's blog on how to solve the issue.  The problem i am having is that no-one seems to have given a solid answer on how to fix the problem.  Any help on this would be greatly appreciated.  The contents of my web.config are the same as on my test server which installed fine.


For all your software needs.....www.softwareknowhow.info
 
New Post
5/26/2007 8:37 AM
 
  • has ASP.Net 2.0 been properly setup
  • did you configure your web site / virtual directory in IIS to point correctly to the DNN root directory, where web.config resides?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
5/29/2007 3:57 AM
 

Hi,

I think that the most likely cause is that ASP 2.0 is not configured correctly.  This was not configured by me so I am not sure what has been done.  I have ran the asp_regiis -i command but that didn't help.

My virtual directory is pointing at the root of the dotnetnuke installation.

Thanks


For all your software needs.....www.softwareknowhow.info
 
New Post
5/29/2007 8:57 AM
 

please also check wether you have a proper web.config file. If you used the source or upgrade version, you need to rename release.config to web.config


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
5/29/2007 12:27 PM
 

The last person that reported this problem turned out to be missing a bunch of DNN files in the bin directory.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...BC30451: Name BC30451: Name 'Config' is not declared.


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