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 ...Worst software seen to date.Worst software seen to date.
Previous
 
Next
New Post
6/4/2007 2:54 PM
 

After trying to install DotetNuke for better than 3 days, I have got to say, that this is the worst piece of software to install.

I have tried several tutorials that say "follow these steps and you will have a working site!"  Don't you believe it!!!

You would think that such a project would have an installation wizard which would insure that all permissions and such are taken care of.

SInce I need to use DotNetNuke, would it be too hard to ask if a real set of installation / configuration instruction, that really works, be provide with the downloads?

So....how do I really install and configure this application??????

 
New Post
6/5/2007 7:40 AM
 

Hello

I have to admit that I felt abit like you do at first, like many open-source projects the start-up instructions generally sucks, since they mainly target people who are allready in the know (is it to much to ask to get a description of what a module actually does and what it provides on the module page? =).

This is how I do atm to get a somewhat easy setup (using 4.5.1):

Preparations:
1. Install the .vsi package for a DNN template in either Visual studio 2005 or the free variest (think its visual web developer from Microsoft.

2. Open MSVS 2005 and select new website --> select the DNN template that should now be there. I usually go for local IIS installation so I can test at localhost. ( for this you need to have IIS on your windowsmachine which will be IIS 5 for win XP and IIS 6 on 2003 server). After a little while the project will be built and you will se the whole file structure in the right-pane of MSVS 2005.

3. Download and install SQL server management studio express 2005 from microsoft. This will give you SQL server like environment free, which makes it easier to make a "real" installation.

4. Create a database (right click on databases in SQL smse 2005).

5. under security create a login account with username and password for sql (remove password policy if you wish).

6. under databases in sql smse 2005 your database should be visible, expand it and go to security-->users. Add the user you created and give that user DB owner schema and db owner role membership.

7. Go back to IIS, rightclick on the website that should be visible (Visual studio creates it in IIS) and run permission wizard (rightclick-->all tasks-->permission wizard) go for public website and replace all directory permissions (it will work for a few seconds). Also in IIS rightclick on the website and pick properties. In the window that shows, go to directory security and pick integrated windows security (spelling? its the little box at the bottom of the page anyhow)

8. go to c\inetpub\wwwroot and rightclick on the folder with your website name. pick properties and go to the security tab. pick Add and in the box that pops up write aspnet and hit the check name button, if its found, add it and give it modify permission. repeat this for Network service (they both need modify I think)

9. Open IIS again and make sure that the IIS-website is running (press the play button)

10. Open Internet explorer and write http://localhost/"write the name of the DNN website here, and without the quotationmarks"

11. With a bit of luck the installationwizard will start. pick typical in the radiobox and your language of choice --> hit next.

12. Test the folder permissions, which should work.

13. Database --> pick sql server 2000/2005 and not sql server express. In the server name write your computername (you can also see this if you open the sql manager, what the server is called). Enter the database name of the database you created. Enter the username and password for the user you created and tick the tickbox with "run as DB owner". Test the connection.

If this works you can hit next and it will install the DB scripts needed to run the DNN site and the wizard will end --> you made it =).

You can now access your site with http://localhost/"name" and you should get to your portal. If you are denied to view the page its probably an IIS error, and the permissions are wrong.

Anyway I hope this will help you get started, it might look like a lot of work , but its actually quite fast once you get the hang of it. Once you get access to the portal and can actually use it, you will hopefully think its worth the trouble.

Good Luck

Torbjörn Bång

 
New Post
6/5/2007 8:23 AM
 

This is no way to get help.   I've been using this software since the first roll out and before that I used IBUYSPY.  I'm not a programer and I've been able to load it with no problems following the instructions.

My suggestion to you is to tone it down, read your instructions again and not bad mouth the software as there are many people here that are happy to give a hand to those who apprieciate it!

 
New Post
6/5/2007 9:06 AM
 

I fully agree to Janettx's words.

I came to DNN with version 4.3.7 and had no clue about portal systems, asp, but knowledge about IIS, MS-SQL and of course some basic things regarding computers....

Since then i made every single upgrade which came up (approx. 6) without any errors. I even managed to customize it a little, with the help of the forum. I don't know how many people are really using it, but hey, more then 440 thousands logged users here will have same real users out there.

Why do some people think that the system is wrong when a single user issue occurs? I've seen this behaviour very often when working in an IT-Department responsible for several hundred people. ONE is having a problem, therefore the whole Infrastructure must be buggy..... well, it is not.

OK, an Installer would be fine, but with the installation document it is pretty easy to build it up. And starting SETUP.EXE, clicking several times on NEXT and then on finish.....everybody could do it. Where is the challange?

 
New Post
6/5/2007 9:29 AM
 

There is an installer for version 4.4.1 if you would like to use it, download it here: http://www.dotnetnuke.com/Projects/UtilityInstaller/tabid/838/Default.aspx

Otherwise, 4.5.x inludes a web based wizard to test permissions and configure your database connection. You pretty much just upzip the install package open it in visual studio and press ctrl+f5 or configure IIS to host the site, and then browse to it. Either way a wizard page should load and walk you through the rest of it.

I would like to say, I agree with the previous responses that your post is no way to ask for help. I am only resonding in hopes of closing this thread so that others do not spend their time on it. I do not mean to be rude, but their are legitiment questions \ issues for the community to deal with. If you "played nice with others" you may have resolved your issues on day 1, mine typically are and I usually find they are related to user error more than the quality of DNN. I have used DNN since version 4 and other than a few minor issues, that again were quickly resolved via these forums and some additional research, I have been more impressed with each release. I encourage you to take a step back re-group and try again, and ask for help before bashing the software.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Worst software seen to date.Worst software seen to date.


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