I've been given the files for a website built using dotnetnuke.  This website was running on a server that is no longer in service.  I am trying to get it up and running on another server.  The new server already has one website using dotnetnuke running on it.  I've created a new website in IIS and mapped it to the files I've been given.  When I click browse, I'm taken to a wizard that steps me through the dotnetnuke setup.  I can get past the initial permissions page, but when I get to the database configuration page and test the database connection, it fails to connect using the host user name and password I've been given for the website.  I've also tried it using the Integrated Security option, but that fails as well for a NETWORK SERVICE user. 

I'm looking for some guidance on how to proceed.  Can anyone give me some advice?  It would be much appreciated.  Thanks.

John M

Yeah, it doesn't sound like you have the whole installation. When we have people moving to PowerDNN from another server we typically request the entire root DNN directory. Those folders are typically labeled wwwroot, but basically you need everything contained in the httpdocs folder. You will also need an SQL backup. If you have access to get that, a backup in .bak format is the easiest to retore, but you can also make due with an mdf and ldf file. 

You must have all those components to fully restore the site. One thing that you can not do (as far as I know) is combine the DNN site you are moving with an already running installation of DNN. 

@JohnM 

Were you able to find a solution to your site issue? If you need some assistance let me know, I know a thing or two about manual migrations.