I have done this dozens of time, but this has me stumped. I've done the usual, downloaded an evotiva backup (files and db), restored the db to a sql express installation, created a user and made it the owner of the db, unpacked the files to a local website already registered with IIS, modified web.config with and appropriate connection string, but when I launch the site, I get an error message saying trouble logging in. Here's a screenshot of the error:
And here's a bit from the middle: [Exception: Failed to execute SQL: SELECT Id,ApiId,PortalId,Name,ContextUser,ContextPortal,ContextPage,ContextModule,IsEnabled,(SELECT MIN(NEXT_FIRE_TIME)
My first pass at dbowner username and password was very simple, I thought that might be the problem so I did it again with more complex name and password, but same error.
Help! Not sure where to start. This is my first time doing this since DNN 9, is there anything different with this version?
Thanks for any guidance.
Looks like screenshot didn't work, here's a link:
And here it is without the image tool:
https://www.dropbox.com/s/6pdiun99ag9knfe/Screenshot%202019-07-06%2020.43.49.png?dl=0
Answered my own question. When I installed the SQL Server instance, I neglected to check the option for both Windows security and SQL security (default is windows only), so when I tried to launch the site and login according to web.config, it triggered the error. Changed to both, now working fine.
Sorry for the disruption, problem solved.
Posted By Worth Robbins on 07 Jul 2019 07:35 AM Answered my own question. When I installed the SQL Server instance, I neglected to check the option for both Windows security and SQL security (default is windows only), so when I tried to launch the site and login according to web.config, it triggered the error. Changed to both, now working fine. Sorry for the disruption, problem solved.
Just glad you found the culprit and were able to move forward :-)
Worth,
you don't have to excuse, the community is here to help each other, and it's great that you found a solution yourself.
When IIS and SQL Server are located on the same machine, I would not recommend using a SQL Server login (which you have when you change to "both"). Add a Windows login to the SQL Server (SSMS: Security -> Logins) with the name of "IIS AppPool\ApplicationPoolName" (the name of the application pool the DNN site is assigned to, e.g. "IIS AppPool\.Net v4.5") and assign it to the db_owner role (or use a more secure configuration).
Then change the connection string to use integrated security, this should look like
Data Source=SERVERNAME;Initial Catalog=DATABASENAME;Integrated Security=True
Happy DNNing! Michael
There's nothing to be sorry about... You just added content that will help countless others. So, it's actually a great thing that you posted the problem and solution. :D Thank you!
These Forums are for the discussion of the open source CMS DNN platform and ecosystem.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.