Products

Solutions

Resources

Partners

Community

About

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 ...SQLServer 2016SQLServer 2016
Previous
 
Next
New Post
8/30/2016 7:25 AM
 
did you upfront create the blank database and grant dbowner permission to the login you are using?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/30/2016 8:19 AM
 
PS: I am not aware of any breaking change in SQL Server 2016, which would affect DNN.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/31/2016 10:38 PM
 

The SA, which is the user (on my local machine, not in production), is the owner.  I created the database before I ran the installation wizard.  

I entirely removed SQL Server from my laptop then installed 2016 again.  Same behavior on a new site.  I just finished setting up three copies of the site using backups from the host (they are using 2016 but Enterprise would be my guess) and gave them all three different names and domain names.  Two of them are fine.  The one I named DNNDEV.ME is throwing the same error as the newly installed ones.  The first time I tried to open it, it said there was a primary key error in PortalAlias although there is just one of everything in the table, including DNNDEV.ME.  Now, it is the same error as has been occuring all along, "http://dnndev.me/Default.aspx?tabid=59&error=An%20unexpected%20error%20has%20occurred&content=0."  

I have created a new custom error page and turned on debugging but still can't seem to get anything other than the DNN error page.  How do I go about getting the "yellow screen of death" in this environment?  I especially want to read the stack trace.    

I am going to go ahead and finish what I can without building custom modules and manually handle the situations I need to handle.  If the host will let me set up a couple of jobs, I won't need the custom modules right away, anyway.  It really is amazing what can be done with this out of the box.

Thanks for all the help you have been able to provide.  At least I know I'm not crazy or wasn't before this started.

JoAnn

 
New Post
9/1/2016 12:32 AM
 
What are you trying to do? I don't understand the fact you restored a database backup from your host and then run a fresh DNN installation against it. The database is supposed to be empty. 
This is how I install a fresh DNN install. Create a an empty DNN database and edit the connection string in web.config.  I only enter the password in the install page. DNN picks up everything from the connectionstring in web.config.

If you want to run a local copy against a copy of the host database, you need to have a copy of the DNN files from the host too because there are extra files in the tree structure after the installation and they need to match with entries in the database.  I don't know if this helps your case any.

 

 

 

 

 
New Post
9/1/2016 4:08 PM
 

Tony:
I have a restored copy of the real site.  In addition to that site, I am trying and failing at creating a separate fresh out of the box site for module development.  Using the Christoc templates requires that the work take place in a site called DNNDEV.ME.  I can neither create a clean out of the box site for this, nor can I clone the copy of the real site and rename it and have it work.  In both cases, I get the same errors.  Others have reported this same issue through various versions.  I had no trouble creating a new site until I installed SQL Server Express 2016.  It might be a coincidence. 

JoAnn

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...SQLServer 2016SQLServer 2016


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