Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ...403 error on clean install to server 2003403 error on clean install to server 2003
Previous
 
Next
New Post
8/8/2006 10:59 AM
 
pvickers

Joined: 8/4/2006
Posts: 8

Hi folks,

Have Microsoft Server 2003 r2 installed on a box, Machine name CASPORTAL ,  not part of a domain.

Have DotNET 2.0 installed

IIS 6.0 installed. sql express 2005 installed.

contents of the DotNetNuke_4.3.4_Source.zip extracted to c:\DotNetNuke

Full control of the folder assigned to ASP.NET machine account and NETWORK SERVICE account

Database created in SQL called DotNetNuke

IIS Virtual directory created under the default web site called DotNetNuke.  local path pointing to C:\DotNetNuke\Website

ASP.NET version set to 2.0

 

All I get when I browse to http://localhost/dotnetnuke is a 403 forbidden error!

Any clues  - below is my web.config

<configuration>

<!-- register local configuration handlers -->

<configSections>

<sectionGroup name="dotnetnuke">

<!-- the requirePermission attribute will cause a syntax warning - please ignore - it is required for Medium Trust support-->

<section name="data" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>

<section name="logging" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>

<section name="scheduling" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>

<section name="htmlEditor" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>

<section name="navigationControl" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>

<section name="searchIndex" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>

<section name="searchDataStore" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>

<section name="friendlyUrl" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>

<section name="caching" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke"/>

<section name="authentication" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />

<section name="members" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />

<section name="roles" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />

<section name="profiles" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />

</sectionGroup>

</configSections>

<connectionStrings>

<!-- Connection String for SQL Server 2005 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 2000/2005

<add

name="SiteSqlServer"

connectionString="Server=Localhost;Database=DotNetNuke;uid=sa;pwd=sapassword;"

providerName="System.Data.SqlClient" />

-->

</connectionStrings>

<appSettings>

<!-- Connection String for SQL Server 2005 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 2000/2005 - kept for backwards compatability - legacy modules

<add key="SiteSqlServer" value="Server=Localhost;Database=DotNetNuke;uid=sa;pwd=sapassword;"/>

-->

<add key="InstallTemplate" value="DotNetNuke.install.config" />

<add key="AutoUpgrade" value="true" />

<add key="InstallMemberRole" value="true" />

<add key="ShowMissingKeys" value="false" />

<add key="EnableWebFarmSupport" value="false" />

<add key="EnableCachePersistence" value="false"/>

<add key="HostHeader" value="" /><!-- Host Header to remove from URL so "www.mydomain.com/johndoe/Default.aspx" is treated as "www.mydomain.com/Default.aspx" -->

<add key="RemoveAngleBrackets" value="false" />

<!--optionally strip angle brackets on public login and registration screens-->

</appSettings>
 
New Post
8/8/2006 5:05 PM
 
Shawn Denogeon

Joined: 7/19/2006
Posts: 32
Try it with http://localhost/dotnetnuke/default.aspx

or with
http://localhost/dotnetnuke/install/install.aspx
 
New Post
8/8/2006 10:56 PM
 
Shane Miller

www.callcenters24x7.com
Joined: 4/2/2005
Posts: 520
See whether or not you can download a static file, such as the logo.gif which comes by default with the DNN installation; that will tell you whether or not your problem is specific to the asp.net configuration. 

Shane Miller
Call Centers 24x7
 
New Post
8/9/2006 9:52 AM
 
pvickers

Joined: 8/4/2006
Posts: 8

ok, resolved that issue.

Ok, Resolved that issue.  Had to add default.aspx to the dotnetnuke virtual directory, "enable default content page" list.  This is located within the properties, then documents tab of the donetnuke virtual directory in IIS.

Don't know if there is a knowldege base somewhere for Server 2003 r2 dotnetnuke installs?  Maybe we could add it?

 

Looks like I still haven't got everything right though, now i get the below error.

 

Error Installing DotNetNuke

Current Assembly Version: 04.03.04

ERROR: Could not connect to database specified in connectionString for SqlDataProvider

 

Which I guess must  mean I have my connection string a bit skew wiff.  Can someone point me in the right direction. The connection string is copyied and pasted to the first post.

Am running SQL Server 2005 Express. Have created a database in the database list called dotnetnuke
 
New Post
8/9/2006 11:35 AM
 
Shawn Denogeon

Joined: 7/19/2006
Posts: 32

Try a different connectiong string, like:

<add name="SiteSqlServer" connectionString="Data Source=.\SQLExpress;Integrated Security=True;Database=DotNetNuke;" providerName="System.Data.SqlClient" />

Also, is your database really called Database.mdf?  And, see this link for an explanation of |DataDirectory|.

You could also try it with SQL Authentication, where you put the user and password in the connectionString.

http://msdn2.microsoft.com/en-us/library/ms228037.aspx

------------------------------

<add name="SiteSqlServer" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;" providerName="System.Data.SqlClient" />
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...403 error on clean install to server 2003403 error on clean install to server 2003


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