Hi guys,
I was wondering if anyone can help me with this question.
We had dotnetnuke 3.1.0 sitting on a server, everything was fine until one day server died.
We have a copy of the dotnetnuke database and I have the original stuff from the virtual directory from that server (we recovered the hard drive).  Now what I've tried to do is to copy that dotnetnuke directory to another machine...but all I can get is "Page cannot be displayed" message when I browse to the default.aspx.
What is the best way to recover everything that we had posted on the dotnetnuke site and to setup a new site on another machine?

Any help will be appreciated.

Olga.

OlgaB:

To expand on what MikeH mentioned about the aliases, in addition to recreating the database, which must include the same security parameters you had before per the Web.config file, and restoring all the content of the DNN directory, including all files specific to the portal(s), you must recreate all the settings for the site in IIS including the default directory, security parameters, host headers, etc. That last point is why is important to backup the IIS metabase.

Hope this helps.

Carlos

OlgaB:

Is the Web site in question visible from the outside world??? Also, check the server system logs for possible IIS errors that may help in the diagnostics. Does the site work if you try to connect to it using localhost on the server console? Do you have ASP.Net 2.0 running on that server? Just in case, make sure that your site is running with ASP.Net 1.1. Did the server TCP/IP address change when you went to the new one, this may cause DNS resolution issues until the change propagates to all devices (including your PC DNS cache).

You can always give us more details about your configuration, server O/S version, whether other sites/applications are running properly on that server, etc.

Sorry for the questions all over the place but your error is not DNN specific, is more basic than that in the interaction of your browser and IIS. See if you can run a simple, plain html page on the DNN virtual directory (make sure that this file has the htm or html extension).

Also, based on what you have said, the old server died for reasons other than hard disk failure correct? I have not considered corruption of the DNN files yet.

Carlos