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 ...Instructions for database creation and securityInstructions for database creation and security
Previous
 
Next
New Post
12/7/2013 5:06 AM
 
Sebastian Leupold wrote:



There are no changes in database setup for DNN between SQL Server 2008, 2008R2 and 2012, file based access (AKA User Instance DB) is available in Express Editions only.

 Thank you, Sebastian. A couple of things...

  • It seems unfortunate to me that the installation page uses terminology that may not be obvious to everyone. I have never heard the term "User Instance" in this context - but immediately understood what you meant by "file-based access". IMHO, the installation instructions should assume the user doesn't know that term.
  • Am I correct in saying that the Attached Database instructions are wrong for SQL Server 2012 on WS 2012 (and may be other combinations)? I followed the instructions to the letter (I think). Nothing worked until I changed the account references in step 14d to "IIS AppPool\dotnetnuke".
  • If the app pool is being created as a consequence of step 9 (Convert to Application), should the instructions not specifically mention that in step 14c? I was using DefaultAppPool until I realized. Obviously I could have figured that out for myself (and did - eventually) but if we are relying on an IIS app that was just created, why not be specific.

Thanks.

Mark

 
New Post
12/7/2013 5:11 AM
 
Richard Howells wrote:



Hi Mark,



Congratulations on solving the problem. 



The page you linked to is a Wiki, and you are the guy who has hit the hole most recently. Why not edit the page yourself to reflect what you discovered?

Because I install DNN VERY rarely (I give up a lot :)) and don't have the confidence that things I discover are correct or don't have side effects I have not yet discovered. Plus, I think the pages should be re-written and I'm not sure I have the time or inclination.

Re "Congratulations on solving the problem" - ah ha! It's all falling into place now. It's a game to see who can work out the ugly world of installing DNN. With that assumption it all makes sense now :)

Mark

 

 
New Post
12/7/2013 5:22 AM
 

Another issue with the installation page...

The link in section 14c goes to a generic page and not the content suggested by the link.

"To read why Windows 7/2008R2 differ click here"

Mark

 

 
New Post
12/7/2013 6:39 AM
 
IIS 7 (Windows 2008/Vista) introduced application pool identities, i.e. virtual users being created automatically for each application pool. You may still use Network Service account, but app pool identities make it much easier for hosters or admins on webservers with sites from different owners to isolate file and database access (for security reasons, each owner should have his dedicated application pool). You need to make sure to grant file system access for the website directory and database access (dbowner role) to the app pool user.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Instructions for database creation and securityInstructions for database creation and security


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