We have a site that is on one server - it needs to be moved to another for maintience reasons.... the database server is staying in place and does not need to be moved... when I copy the site over... and then update the A record - then set the bindings in IIS7.... browse to the site and I get a:

 

Any ideas what might be causing this? The only thing that I can think of is that this site requires an SSL Cert... but this has been copied over and ever other DNN Instance that I have copied over before works fine. Is there anything in the web.config file that can cause this to happen?

 

I too have seen many 403 errors. One gotcha that really got me was to open up the ASP.NET tab in IIS 6, only to find it was pointing to a different database than what was listed in the web.config. When I updated the ASP.NET tab then I could install dnn. There are somethings in the database that need to be, before default.aspx will load.

---

Bill Swanson

I checked and made sure that this document type was in the list... and it is. Still no luck... Not that I think this should matter, but here is some more details:

• The site is still on the old server and is a live site (www.domain.com)
• The site was copied to a new server that has other DNN instances on it... and all the other sites work...
• The site that is a copy has a subdomain pointing to it for testing purposes to make sure it works (test.domain.com)
• Once I can get this to work I will just switch the A record and bindings to make the site live
• This is the only site that is suppose to have SSL, but whether I have it turned on or off - I get the same 403 error
• Both sites access the same database... that database is held on a third server. Every other site I have hosted works fine as mentioned...
• When I moved this site... literally all I did was copied the whole DNN instance directory to the new server and created a new site in IIS7
• I have done the above with another site just to test if copying files and creating a new site in IIS would work... it did just fine.