I have a website based on DNN 7.3.3 running well on a server. All necessary sources and binaries are checked into a SVN repository. In the past, checking out all files and compiling was all I had to do on a new device.
Now I set up a new server, checked out all sources and binaries and compiled without errors. However, on start of my website with IIS Express the DNN installation procedure is started.
Why??
I know that DNN 7.3.3 is outdated but we don't have much time so It would be fine to keep this version.
I used the database backup of the old server to set up the database on the new server. So I think that the DB is ok.
My collegue tells me that she hat to run through the DNN setup rocedure whenever she changed her computer. So I'll try to do the install.
Maybe the problem is that I created a new database instance, restored the DNN database with a backup of the production version on the old server but I did not yet grant access to the current Windows user.
In former situations, I got HTTP error 500 with a stack trace that told me about problems logging in my current user. The current reaction however was new to me and upset me.
The problem was as follows: I am using two different databases: One for the DNN content and one for my program logic. I granted access to the program logic database but not for the DNN database. This was the difference to former situations where I did not grant access to any of those databases.
After changing the access rights for the current user for both databases, the web application is running, at least in debugging mode in IIS Express.
Usually, issues like this are due to a missed step in the migration/copy/restore of the website.
Assuming you have a good setup that can run an ASP.NET application like DNN (e.g., .NET, IIS, SQL all installed and properly configured)...
You need to be sure to have a good and synchronized backup of the files and database. Recreate and reapply the permissions on the new folder.
Once you've restored the database and files, you need to be sure the web(dot)config is updated to reflect the new database location and credentials.
You'll also need to update the database to respond to the correct domain name in the PortalAlias and PortalSettings tables.
PortalAlias
PortalSettings
As an added bonus, you may also want to change the SMTP server setting so that it doesn't send emails to people from the wrong place and for the wrong reason.
In all of these cases, I highly recommend only using copy & paste to update values. Typos are the most common culprit in my experience. 😉
These Forums are dedicated to the discussion of DNN Platform.
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.