Hello,

I developed our DNN 4 site on a local development box.  Once I was complete with the development I moved the database and files to the production hosting server.  I made changes to the web.config file for the new database settings and modified the key "" to the new domain name.  When I access the site its trying to call the url to my local secure development server... 

Am I missing another step here?  Is my development server string tucked away in another file or database setting?

 Thanks very much in advance.

As mentioned above you will need to work with the PortalAlias table.  I have a full guide that covers this available on my website, but to get you going you can fix things up with a simple insert into your database, and a modification of your web.config.

First you need to add a new portal alias for the new URL to be used for your site.  Assuming that you have only one portal the following script should be ok to insert the alias, simply put your own values in for the mysite.com portion.

INSERT INTO PortalAlias (PortalId, HTTPAlias)
VALUES(0, 'mysite.com)

After you do this, add a space to a non-critical part of your web.config and save it.  This will trigger a restart of the DotNetNuke application which will update the cache and you should be set to go!

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services