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

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

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