I have a DNN site and upgraded to DNN 7 now. originally it was 5. (ex: www.website.com)

I need to do changes to the site. But need to keep the live site as it is until I go for the new site.

So I just copied the source to a new site as a sub domain. (demo.website.com)
Then created a database and duplicate the database as the live site. Changed the connection to the new database.
Changed the "PortalAlias" table "HTTPAlias" record to "demo.website.com"

But still I am getting an error page called as

This site is currently Unavailable

Please check back later

 

The connection string is correct and just needed to change only the database name as the live site.

What could be the issue? Where else should I change the database? Anything else have I missed? Please advise.

There can be a number of reasons that a cloned site brings up this error message. Most often it is due to a failure to connect to the database. Please check the following:

• Does site's application pool meet the minimum requirements for DNN 7.x - Windows Server 2008 or Windows 7, IIS 7.0, MS SQL Server 2008, ASP.Net 4.0 application pool running in Integrated Pipeline mode (not classic) only.
• Have you granted full file system permissions to the ASP.Net Worker Process account (IIS Identity Account) for the cloned site's root folder and allowed those permissions to propagate to all child folders. Note that any file system permissions applied to the "old" site would not have transferred when you cloned the site and must be reset.
• You indicated that you created a new database, duplicated the old site's database and changed the database connection string. Is the new database on the same SQL Server instance as the old? If not you may be running into the issue of an "orphaned" database user. Even if you created a new database user having the same username as the old, internally this user account is not the same account as that in on the old database server. Please see the following for more information: http://mcpmag.com/articles/2011/02/17.... Since you will be transferring the cloned database back to the live site at some point, it may be best to create a new database server login of a different name, add this new login to the cloned database and apply db_owner role.

My bet is on the "orphaned" database user being the issue.

 

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner