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/28/2016 2:36 PM
 

I have been a real pain to everyone on here since I installed SQL Server 2016 last week.  I had to use it since my hosting company is using it and the backup they provided for my local dev site was in 2016.  While I was able to restore the bak and httpdocs and get everything running well here, I have not yet been able to install an out of the box site.  I thought it was due to a conflict with SQL 2012 so I scripted everything out and removed SQL 2012 completely.  My problems remain, however.  The installs state that they were successful but the minute I try to go to the home page, I get an error in the query string along the lines of:

http://dnndev.me/Default.aspx?tabid=55&error=An%20unexpected%20error%20has%20occurred&content=0

I would look at the event logs and saw an error on page load.  I just now looked farther down the list and see what had to have been errors during the installation

<LogProperties>
<LogProperty>
 <PropertyName>AbsoluteURL
</PropertyName>
<PropertyValue>/Default.aspx
</PropertyValue>
</LogProperty>
<LogProperty>
<PropertyName>DefaultDataProvider
</PropertyName>
<PropertyValue>DotNetNuke.Data.SqlDataProvider, DotNetNuke
</PropertyValue>
</LogProperty>
<LogProperty>
<PropertyName>ExceptionGUID
</PropertyName>
<PropertyValue>e85b6367-f05f-4790-ac18-68bbdc8341b2
</PropertyValue>
</LogProperty>
</LogProperties>

It can't be that it can't connect since it does create the objects in the database. That means it is the right set of credentials and SQL authentication is available and the user can log in remotely.  I also verified these by looking at their settings in the server.   In addition, the copy from our host runs fine, so it connects.  I have tried this with new installs of both 8.0.3 and 7.4.1 with the same results.

What else can I look at?

Thank you for your patience with me.  

JoAnn

 
New Post
8/28/2016 5:14 PM
 
what are properties in your connection string (please don't publish user name or password), database owner and object qualifier?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/28/2016 9:54 PM
 

Thanks.  They are the ones that are blacked out in the screenshots, the database owner is dbo and there are no object qualifiers.  I should note that I found it interesting that running the installation, it would not accept the server name when it was just the local server but the installation would run leaving that blank.  I installed a second, named instance of 2016 and was able to use that server name to run the installation.  

JoAnn

 

 
New Post
8/29/2016 3:30 AM
 
what is compatibility level of the database, you created?
if you want to install on local server default instance, you may just use ".", for any named instance ".\sqlexpress" or appropriate name.
further down, databaseowner should be "dbo" and objectqualifier empty string.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/29/2016 9:38 PM
 

Thanks for looking at this with me.

Compatibility level is 130 and the dbo checkbox is checked.  Do you think changing it to 110 (Sql Server 2012) might get it to work?  I guess I can try it.

I will admit to using the sa locally since it is just me here at home and there is nothing to be gained by hacking my pc.  Obviously, it is different in production.


When I was trying to use the local instance of SQL Server, it wouldn't accept just a period for the server name or the server name itself.  It did accept a blank.  This is running against a named instance.

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