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 ...Install DotNetnuke 4.0Install DotNetnuke 4.0
Previous
 
Next
New Post
11/27/2006 6:20 PM
 
skips

Joined: 10/12/2006
Posts: 77
Hi all,
I am having difficulties installing dotenetnuke version 4. I am following the instructions from the book (Professional DotnetNuke 4).
I am doing the following:
 
  1. Created a subdirectory and called it website (C:\websites\dotnetuke\website)
  2. Extracted the install package into the website subdirectory that I’ve just created
  3. Configured IIS (version 5.1), created a virtual directory called DotNetNuke and made sure that it points to the appropriate physical file directory
  4. Ensured that virtual DotNetNuke virtual directory is running on ASP.NET 2.0.
I get confused when I have to configure web.config for installation. What do I need to change on the <connectionString> Sections and <machineKey> Section?
I believe I have to create a database on SQL server for dotnetnuke.
 
 
I desperately need to install dotnetuke ASAP so I can start working on my intranet project.
 
Finally is the install package that right package for my project?
 
Any help much appreciated
Skips
 
New Post
11/28/2006 5:46 AM
 
Sebastian Leupold


Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

Sebastian Leupold's Avatar

www.dnnwerk.de
Joined: 3/8/2004
Posts: 46212
  • Using Install you got the right package.
  • Did you set folder permissions for C:\websites\dotnetuke\website, to grand access to the virtual user (local "ASPNet" or "Network Service")?
  • you should find a database.mdf in your app_data subdirectory. DO NOT touch with SQL Management Studio!
  • have you installed MS SQL Express locally as \SQLExpress instance and granted Windows or mixed authentication? In this case you do not need any changes to your web.config and can just start calling your webSite as http://localhost/<virtualdirectory>
Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
11/29/2006 12:46 AM
 
Shawn Mehaffie

Joined: 1/4/2003
Posts: 2313
You can attach to the database in SQL Management Studio, but certain steps have to be followed so you can access the DNN using SQL Managment Studio and the DNN site can still access it.  See my blog at www.dotnetnuke.com/Community/BlogsDotNetNuke/tabid/825/EntryID/1202/Default.aspx  for complete details.
 
New Post
11/29/2006 9:34 AM
 
skips

Joined: 10/12/2006
Posts: 77

By giving acess to ASP.net user, solved the problem, many thanks for that tip. I need to use a database which is already created in MS SQL 2005. How can I  connect dotnetnuke with the database and display staff information/contact details on dotnetnuke? And my second question is: How do I change the url from http://localhost/dotnetnuke to http://intranet and finally I have installed dotenetnuke on client machine(my machine, XP Pro) at work and not windows 2003 server. What do I have to do/change so other client machines can access  the dotnenuke by typing http://intranet (once the url is changed).

Many thanks for all your help.

Skips

 
 
New Post
11/29/2006 6:40 PM
 
Shawn Mehaffie

Joined: 1/4/2003
Posts: 2313
I need to use a database which is already created in MS SQL 2005. How can I  connect dotnetnuke with the database and display staff information/contact details on dotnetnuke?
-- Use the other connection string for SQL2000/SQL2005 that is commented out by default (make sure you comment out the other one).  You connection string should look like this:
"Server={Your Server Name};Database={Your DNN database name};uid={UserID};pwd={Password};".  For more information please check out the installation document.

How do I change the url from http://localhost/dotnetnuke to http://intranet:
--Access the site and login as host.  Go to site settings and at the bottom of the screen there is a section for aliases.  Add an entry for the alias you want to use.  By adding this you can access it using either URL.

What do I have to do/change so other client machines can access  the dotnenuke by typing http://intranet (once the url is changed).
-- You either have to get a DNS entry created so that the URL resolves to the IP address the site is running under.  Or if you do not have a DNS server, you can add an entry into each users hosts file.  The second way is not recommended because it is really hard to maintain and you have to update every machine that will need access to the site.
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Install DotNetnuke 4.0Install DotNetnuke 4.0


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