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 ...New install for local intranetNew install for local intranet
Previous
 
Next
New Post
2/7/2011 1:31 PM
 
Hello,

    I've searched through the net and cannot find the answer that best fits my scenario. I'm attempting to install DNN on my companies local intranet so that it may be viewable to anyone connected to the network. I downloaded and extracted the "source code project" files of version 5.6.1 to my C:/inetpub/(site name) local folder after IIS setup of this site on my machine. I then made a new database on a NETWORK DATABASE SERVER. Made the appropriate changes and modified the release.config file with the correct connection strings for SQLSERVER and renamed to web.config. When I try to navigate to my site to finish the install, I get the following...
Compiler Error Message: BC30451: Name 'Config' is not declared.

Source Error:

Line 61: ''' ----------------------------------------------------------------------------- 
Line 62: Private Sub Application_Start(ByVal Sender As Object, ByVal E As EventArgs)
Line 63: If Config.GetSetting("ServerName") = "" Then
Line 64: ServerName = Server.MachineName
Line 65: Else

Source File: C:\inetpub\port\App_Code\Global.asax.vb    Line: 63 

 

 Here are my web.config connection strings...
<connectionStrings>
    <!-- Connection String for SQL Server 2005/2008 Express
    <add name="SiteSqlServer" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;" providerName="System.Data.SqlClient"/> -->
    <!-- Connection String for SQL Server 2005/2008-->
    <add name="SiteSqlServer" connectionString="Server=(NetworkDbServerName);Database=port;uid=portdbadmin;pwd=portadmin1;" providerName="System.Data.SqlClient" />
   
  </connectionStrings>
  <appSettings>
    <!-- Connection String for SQL Server 2005/2008 Express - kept for backwards compatability - legacy modules 
    <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/> -->
    <!-- Connection String for SQL Server 2005/2008 - kept for backwards compatability - legacy modules    -->
    <add key="SiteSqlServer" value="Server=(NetworkDbServerName);Database=port;uid=portdbadmin;pwd=portadmin1;"/> 

I've setup several DNN sites before but this is the first time I've tried to use my local machine as the app server and a network box as the DB server to be viewed on a local intranet.

Thanks for your help,
~Mike
 
New Post
2/7/2011 2:16 PM
 
I received a recomendation from another forum to replace the app files with just the install package files and modify the new web.config.

It worked!

Not exactly sure what the issue was but I'll be sticking with the install only files from now on.

Thanks,
~Mike
 
New Post
2/7/2011 3:31 PM
 
That's good advice to use the Install package rather than Source package at this point. The Source package intentionally does not include a web.config file  In addition to having to rename the Source package's release.config or development.config file to web.config, it is necessary to first build the DotNetNuke_Community solution in Visual Studio, lacking which is the root cause of the error you received. - not something to attempt when first working with DotNetNuke! Even if you later get involved in developing custom modules and other extensions for DotNetNuke, it is still recommended to use the Install package in your development environment.

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...New install for local intranetNew install for local intranet


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